IBM RS/6000 SP, Problem Determination Manual

Page: 42 / 316

This soft copy for use by IBM employees only.
2.2.16 Determining Software Service Level
It is important to find out what software service level you have because you may,
for example, need it to report a problem to the IBM Support Center. The support
staff needs this information to check various databases to ascertain if such a
problem is already known on the software service level in question.
Specifying the current software service level while ordering PTFs dramatically
reduces the PTF package size and installation time. There are at least two ways
to find out your software service level:
•
lslpp
command
The
lslpp
command has various flags to provide service level information, as
the following example shows:
# lslpp -l

grep ssp
ssp.authent 2.1.0.2 COMMITTED SP Authentication Server
ssp.basic 2.1.0.10 COMMITTED SP System Support Package
ssp.clients 2.1.0.5 COMMITTED SP Authenticated Client
ssp.css 2.1.0.8 COMMITTED SP Communication Subsystem
ssp.docs 2.1.0.4 COMMITTED SP man and info files
ssp.gui 2.1.0.6 COMMITTED SP System Monitor Graphical
ssp.jm 2.1.0.2 COMMITTED SP Job Manager Package
ssp.public 2.1.0.2 COMMITTED Public Code Compressed
ssp.sysctl 2.1.0.2 COMMITTED SP Sysctl Package
ssp.sysman 2.1.0.7 COMMITTED Optional System Management
ssp.top 2.1.0.2 COMMITTED SP Communication Subsystem
ssp.authent 2.1.0.0 COMMITTED SP Authentication Server
ssp.basic 2.1.0.10 COMMITTED SP System Support Package
ssp.clients 2.1.0.0 COMMITTED SP Authenticated Client
ssp.css 2.1.0.8 COMMITTED SP Communication Subsystem
ssp.jm 2.1.0.0 COMMITTED SP Job Manager Package
ssp.sysctl 2.1.0.0 COMMITTED SP Sysctl Package
ssp.sysman 2.1.0.7 COMMITTED Optional System Management
ssp.top 2.1.0.0 COMMITTED SP Communication Subsystem
• Using PSSP Program Directory
The structure is /usr/lpp/ssp/ < p r o d u c t > /< l e v e l > , where product is an SSP
product such as ssp.basic, and level is the level of service such as 2.1.0.10.
You may traverse through the PSSP program directory for individual PSSP
components and get to the
fixdata file, as shown in the following example:
22
SP PD Guide