TCP/IP (Parallel Library) Configuration and Management Manual

Configuration Quick Start
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006
1-21
Tasks: Stopping Parallel Library TCP/IP and
Preserving the Database
The following sample display results from the LISTOPENS PROCESS
command and shows all the processes depending on $ZTCO:
In the Openers column, $ZTNP1 (the name of the TELSERV process
identified in Step 2b on page 1-20) is an opener of the $ZTC0 process. Be
sure that you do not stop this process while executing this shutdown
procedure. This is the process that is running your home terminal.
Comparing the process that you have just identified as running your home
terminal to the output from the LISTDEV commands in Steps 1 on
page 1-19 and 2ba on page 1-20, ensure that this process is not a
TCPSAM process. If the process running your home terminal is a TCPSAM
process, you must use TELNET to connect to a conventional TCP/IP
process and subnet on your system, then execute these procedures from
that process.
3. Determine if any applications are using the TCPMONs and make a note of the
application names for Step 6. Enter the following command at the SCF prompt (a
sample display follows this command):
TCPIP Listopens PROCESS \HOME.$ZTC0
Openers PPID BPID PLFN BLFN Protocol Lport
$ZPRP1 1,304 4 0 TCP echo
$ZPRP1 1,304 5 0 TCP finger
$ZPRP1 1,304 6 0 TCP ftp
$ZTNP1 1,305 3 0 TCP telnet
$ZTSM 0,307 22 0 TCP 980
$ZCVP1 0,324 1 0 UDP 548
$ZPMP1 1,266 2 0 UDP 111
$ZPMP1 1,266 3 0 TCP 111
$ZTNP1 1,305 4 0 TCP telnet
$ZNET 0,21 2 0 #ZSPI *
->LISTOPENS MON $ZZTCP.*
Note. Socket applications can be bound to the SRL without having an open socket. Hence,
their file names would be in use but they would not show up in the LISTOPENS MON
command. These applications could cause an error when you start the Parallel Library TCP/IP
subsystem. If you receive an error (“NLD fatal error, cannot open ZTCPSRL” or “file already
exists”) when running your startup files, repeat the procedure for shutting down and clearing
out the database, then add the names of the processes listed in the error message to the
STOP PROCESS commands in the command file. (See ==Stop the Opener Processes== in
Example 1-3
on page 1-23.)