NonStop S-Series Operations Guide (G06.29+)

Processes: Monitoring and Recovery

HP NonStop S-Series Operations Guide—522459-009

5-6

Recovery Operations for Processes

The asterisks (*) indicate files that do not appear if only OSM (and not TSM) is

installed.

OSM renames some TSM-related files for use by both applications. For example,

$TSMM0 and $TSMM1 become $OSMM0 and $OSMM1 after OSM is installed. You

can still run TSM even though $TSMM0 and $TSMM1 no longer appear by those

names. $ZLOG is another file that is used by both OSM and TSM. (The symbolic

name no longer contains TSM.)

Some OSM and TSM processes stop after executing a macro that runs during system

load or during the reload of processor 0 or 1. Those processes include $TSMRD,

TSMM0, and $TSMM1 (if OSM is not installed), and $ZOLHI, $OSMM0, and $OSMM1

(if OSM is installed).

Optionally, you can also configure other processes such as the Expand subsystem

manager process, $ZEXP, and the Safeguard monitor process, $ZSMP, as generic

processes.

Recovery Operations for Processes

For recovery operations on generic processes, use the SCF interface to the Kernel

subsystem and specify the PROCESS object. These SCF commands are available for

controlling generic processes:

Generic processes that are configured to be persistent usually do not require operator

intervention for recovery. In most circumstances, persistent generic processes restart

automatically.

For recovery operations on IOPs, refer to the manuals listed in Section 6,

Communications Subsystems: Monitoring and Recovery.

For recovery operations on system processes, refer to the Guardian User’s Guide.