TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

Manage the NonStop TCP/IPv6 Subsystem
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
6-15
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 this way, set the STARTMODE to
SYSTEM.
If you add the TCP6MAN process as a generic process configured in this way,
TCP6MAN starts automatically upon system reload and subsequently restores its
stored and subordinate objects. Alternatively, when you add the TCP6MAN 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 by the TACL STOP command (if the generic process is configured
with STARTMODE SYSTEM) in addition to starting those generic processes when the
system is reloaded. Hence, if TCP6MAN is a generic, persistent process
(AUTORESTART > 0), any time you issue a TACL STOP command to the NonStop
TCP/IPv6 subsystem, TCP6MAN gets restarted by the persistence manager. To avoid
this behavior and stop a persistent, generic, TCP6MAN process, issue the ABORT
command to the NonStop Kernel subsystem as in this example:
->ABORT PROCESS $ZZKRN.#ZZTCP
See also How to Stop the Generic Process for TCP6MAN on page 6-17.
For more information about generic processes and the persistence manager, see the
SCF Reference Manual for the Kernel Subsystem.
Managing the TCP6SAM Process
Remember that the TCP6SAM 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, although you add
$ZZTCP as a generic process, your NonStop TCP/IPv6 environment is not completely
persistent because you still must create any required TCP6SAM processes and any
applications that depend on TCP6SAM. (See How to Manage TCP6SAM-Dependent
Applications on page 6-16.)
These procedures show how to create TCP6SAM processes.
TACL Commands for Starting a TCP6SAM Process
Start a TCP6SAM process by entering this TACL command (substitute a name of your
choice for the process name -- shown here as ZTC2):
>TCP6SAM /NAME $ZSAM3, TERM $ZHOME, IN $ZHOME, OUT $ZHOME,
NOWAIT, CPU 0/1