IBM eServer Cluster 1600 Managed by PSSP 3.5: What's New

188 IBM ^ Cluster 1600 Managed by PSSP 3.5: What’s New

򐂰 The lppsource has to be at least at the level of the SPOT and the machines it

supports.

򐂰 Have the newest version of the xlC.rte and vacpp.* in your lppsource and your

SPOT. Otherwise, you might encounter migration problems.

Investigating PTFs

Usually, it is recommended to always apply the latest PTFs obtained by IBM.

Sometimes in a stable production environment, only a few PTFs are applied after

testing. In this case, it can be necessary to not only read the information obtained

by the

instfix command, but also to take a look at the package itself, as shown

in Example C-4.

Example: C-4 Listing the contents of a PTF

sp3cws:/spdata/sys1/install/pssplpp/PSSP-3.5/PTFs

root $ cat PTF001.ssp.vsdgui.bff | restore -Tq -f -

./

./lpp_name

./usr

./usr/lpp

./usr/lpp/ssp.vsdgui/ssp.vsdgui/3.5.0.1

./usr/lpp/ssp.vsdgui/ssp.vsdgui/3.5.0.1/liblpp.a

./usr/lpp/ssp/perspectives/bin/spvsd

Rebuilding the SPOT

When making changes to the lppsource directory, such as adding PTFs, the

Shared Product Object Tree (SPOT) must be updated. In order to update SPOT,

perform the following steps on the control workstation and all of the boot/install

servers:

1. Deallocate the SPOT from all clients using the

unallnimres -l <Node>

command.

2. On the control workstation only, copy all the install images for the PTFs to the

lppsource directory that corresponds to the appropriate SPOT.

3. For boot/install server (BIS) nodes, it is necessary to add the BIS host name

to the /.rhost file on the control workstation.

4. Issue

inutoc in the lppsource directory.

5. Issue

nim -o check -F <lppsourcename>.

6. Issue

smit nim_res_op.

7. Select the appropriate SPOT.