OSM Service Connection or TSM Service Application: CRUs or FRUs Are Missing

4.6 Click Skip Logon and then click Yes to dismiss the warning
dialog.
4.7 Delete and re-add the IP address of the console exhibiting
the problem and click OK or Apply.
4.8 Exit the TSM Configuration Application.
4.9 Log back on to the TSM Service Application.
If the CRU or FRU still does not appear, proceed to the next step.
5 Is there a problem with the TSM server software?
To recover from a possible problem with the TSM server, copy the
contents of the ZSERVICE subvolume to tape or diskette and send it
to the GCSC along with a description of which CRU is missing. Then
stop and restart $ZTSM.
5.1 Log on to the server as the super ID (255,255) and use TACL
to stop the $ZTSM process. The Persistence Monitor ($ZPM)
will automatically restart $ZTSM, which initiates a system
discovery. Allow the discovery process to finish, which might
take several minutes.
5.2 Log off of the TSM Service Application.
5.3 Log back on to the TSM Service Application.
Note: The ZSERVICE information will be forwarded to TSM
Development for diagnosis.