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-16
How to Manage TCP6SAM-Dependent Applications
Command File for Starting a TCP6SAM Process
Because you have to start TCP6SAM processes yourself without the aid of the
persistence manager, HP recommends that you create a command file for this
purpose. However, before issuing the OBEY command on the file, ensure that your
session is still in the subvolume of the SRL file by using the FILEINFO command
shown in TACL Commands for Starting a TCP6SAM Process on page 6-15.
1. Create the SAMUP file. (Substitute real values for the variables indicated in italics.)
2. Issue this command at the TACL prompt:
How to Manage TCP6SAM-Dependent Applications
Although you can have NonStop TCP/IPv6 started automatically by the persistence
manager, the TCP6SAM processes cannot be managed by the persistence manager.
As applications that depend on NonStop TCP/IPv6 use TCP6SAM, you should not
configure those applications as generic processes to be started automatically by the
persistence manager.
How to Add TCP6MAN as a Generic Process to the System
Configuration Database
Although you should not need to add $ZZTCP as a generic process more than once,
HP recommends that you create a command file for the procedure as a safeguard to
allow you to resume the exact configuration of $ZZTCP as a generic process.
To add a generic process to the system configuration database for $ZZTCP, create a
command file containing commands like the one shown in Example 6-3
(substitute
your own values for those parameters indicated in italics). For complete information
Example 6-2. SAMUP
TCP6SAM /NAME $ZSAM3, TERM $ZHOME, IN $ZHOME, OUT $ZHOME,
NOWAIT, CPU 0/1
>OBEY SAMUP
Note. You can start the TCP6MAN process from a RUN command rather than through the
persistence manager and TCP6MAN will restore the configuration of the subordinate objects
from the system configuration database. Remember, that TCP6MAN does not start any
TCP6SAM processes; you must start TCP6SAM processes manually whether you are using
the persistence manager or the RUN TCP6MAN command.