OSM Migration Guide (G06.25+)

TSM Coexistence and Fallback

OSM Migration Guide—527273-008

6-2

Fallback Issues

This section describes fallback steps to be performed if you need to revert to TSM

instead of OSM for managing your NonStop S-series servers.

1. If you uninstalled TSM components (not necessary for migrating to OSM), reinstall

those TSM components. TSM server components continue to be delivered on the

SUT, and TSM client components are delivered on the NonStop System Console

Installer CD.

2. Revert to the TSM client applications. Reconfigure the TSM Notification Director for

dial-outs if you disabled that feature when you migrated to OSM and be sure to

disable dial-outs in the OSM Notification Director to avoid duplicate dial-outs.

3. Re-enable TSM functionality that was disabled by OSM (as described in

Coexistence Issues).

•

To reenable processor incident analysis and automatic power scrubbing, either

purge the TSMINI file ($SYSTEM.ZSERVICE.TSMINI) or delete the following

text string that OSM inserted into the file:

ExecutePowerTest = no

nocpuia = 0

nocpuia = 1

nocpuia = 15

These changes take effect once you restart $ZTSM as part of step 4.

•

To reenable the automatic line-handler process used by TSM:

1. Go to $SYSTEM.ZOSMLH and perform:

RUN DISABLE

2. Go to $SYSTEM.ZAUTOLH and perform:

RUN ENABLE*

* This assumes you had previously enabled the automatic line-handler

process using TSM. If you do not see the ENABLE macro in this location,

run the TSM guided configuration tool “Configure ServerNet Node” to

enable the automatic line-handler process. For more information, see the

Configure ServerNet Node online help.

4. Restart TSM processes.

Note. TSM does not support certain functionality in the G06.22 RVU and later.