TCP/IP (Parallel Library) Configuration and Management Manual

Managing the Parallel Library TCP/IP Subsystem
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006
4-3
Managing Persistence
Managing Persistence
You can add a generic process to the system configuration database and define that
generic process in such a way that the persistence manager ($ZPM) will restart the
generic process whenever the generic process abends, is stopped through TACL, or
the system is reloaded. To define the generic process, set the STARTMODE to SYSTEM.
If you add the TCPMAN process as a generic process configured in this way, TCPMAN
starts automatically upon system reload and subsequently restores its stored,
subordinate objects. Alternatively, when you add the TCPMAN process as a generic
process to the system configuration database, you can choose to configure it using
STARTMODE MANUAL; this method requires that you start $ZZKRN.#ZZTCP manually
by using an SCF START command to the NonStop Kernel subsystem.
Note that the persistence manager restarts persistent generic processes whenever
they are stopped (if the generic process is configured with STARTMODE SYSTEM) in
addition to starting those generic processes when the system is reloaded. Hence, if
TCPMAN is a generic, persistent process (AUTORESTART > 0), any time you try to stop
TCPMAN, it gets restarted by the persistence manager. To avoid this behavior and
stop a persistent, generic, TCPMAN process, issue the ABORT command to the
NonStop Kernel subsystem as in the following example:
->ABORT PROCESS $ZZKRN.#ZZTCP
See also How to Stop the Generic Process for TCPMAN on page 4-5.
For more information about generic processes and the persistence manager, see the
SCF Reference Manual for the Kernel Subsystem.
Managing the TCPSAM Process
Remember that the TCPSAM process cannot be added as a generic process because
processes that require PARAMs or DEFINEs cannot be configured as generic
processes or added to the system configuration database. Therefore, even if you add
$ZZTCP as a generic process, your Parallel Library TCP/IP environment is not
completely persistent because you still must create any required TCPSAM processes
as well as any applications that depend on TCPSAM. (See How to Manage TCPSAM-
Dependent Applications on page 4-4.)
The following procedures show how to create TCPSAM processes.
TACL Commands for Starting a TCPSAM Process
To create a TCPSAM process, perform the following steps:
1. Determine the location of the system image file (OSIMAGE) by entering the
following TACL command:
>FILEINFO $SYSTEM.SYS*.OSIMAGE
Select one of the system subvolumes returned by this FILEINFO command for the
next step.