TCP/IP (Parallel Library) Migration Guide

Migration Considerations
HP NonStop TCP/IP (Parallel Library) Migration Guide—522272-003
3-10
Persistence Manager
6. Start LISTNER and TELSERV.
7. Specify Define in $SYSTEM.SYSTEM.TACLLOCL (If not using DNS).
Persistence Manager
Parallel Library TCP/IP, unlike conventional TCP/IP, participates in the system
configuration database; that is, changes to the SCF objects for Parallel Library TCP/IP
are stored in the system configuration database so that the subsystem can be restored
by the persistence manger $ZPM after a system load. You must add the TCPMAN
process as a generic process to the NonStop Kernel subsystem to activate this feature.
Configuration Database Changes for G06.10
The Parallel Library TCP/IP configuration database record structure changed in the
G06.10 RVU (SPR T0470AAB) and is not compatible with the previous configuration
database record structure. When migrating Parallel Library TCP/IP from G06.08 or
G06.09 to G06.10 or later RVUs, repopulate the configuration database by running the
startup script. (The equivalent SPR migration is from T0470AAA to T0470AAB or later.)
Startup scripts generally start the TCPMON processes, add and start the SUBNETs,
add and starts the ROUTEs, and add the ENTRYs. These PROCESS, SUBNET,
ROUTE, and ENTRY records are added to (repopulate) the configuration database.
The configuration database record structure has not changed since G06.10, so you do
not need to start Parallel Library TCP/IP by running the startup script. (The existing
PROCESS, SUBNET, ROUTE, and ENTRY records in the configuration database are
used to configure your Parallel Library TCP/IP subsystem.) Similarly, if migrating from
Parallel Library TCP/IP Conventional TCP/IP
ADD DEFINE =TCPIP^PROCESS^NAME,
class & map, file $ZTC1
ADD DEFINE =TCPIP^PROCESS^NAME,
class & map, file $ZTC0
PARAM TCPIP^PROCESS^NAME $ZTC1 PARAM TCPIP^PROCESS^NAME $ZTC0
LISTNER/TERM $ZHOME, OUT $ZHOME, &
NAME $LSN0,CPU 0,NOWAIT,&
PRI 160/$SYSTEM.ZTCPIP.PORTCONF
LISTNER/TERM $ZHOME, OUT $ZHOME, &
NAME $LSN0,CPU 0,NOWAIT,&
PRI 160/$SYSTEM.ZTCPIP.PORTCONF
TELSERV/TERM $ZHOME, OUT $ZHOME,&
NAME $ZTN0,CPU 0,NOWAIT,&
PRI 170/ -BACKUPCPU 1
TELSERV/TERM $ZHOME, OUT $ZHOME,&
NAME $ZTN0,CPU 0,NOWAIT,&
PRI 170/ -BACKUPCPU 1
Parallel Library TCP/IP Conventional TCP/IP
ADD DEFINE =TCPIP^HOST^FILE,CLASS
& MAP,FILE $SYSTEM.ZTCPIP.HOSTS
ADD DEFINE =TCPIP^HOST^FILE,CLASS
& MAP,FILE $SYSTEM.ZTCPIP.HOSTS
Note. TCPSAM cannot be added as a generic process. Even if TCPMAN is automatically
restarted by the persistence manager, you must still start the TCPSAM processes using
interactive SCF or command files if you have applications that are using TCPSAM as the
transport-service provider.