DSM/Tape Catalog User's Guide

Storage Server Interface (SSI) to the Tape Library
Control Path
DSM/Tape Catalog User’s Guide 520233-008
8 - 5
Running the Portmapper
must be an existing CPU, different from the primary CPU. If not supplied, the
portmapper cannot run as a process pair.
TCPIP pname
specifies the name of a TCP/IP process that provides a TCP/IP interface to an
Ethernet LAN. If not specified and a parameter exists for
TCPIP^PROCESS^NAME, that parameter is used. Otherwise, $ZTC0 is
assumed.
COLLECTOR pname
specifies the name of the EMS collector to be used for EMS events. If not
specified, the primary collector $0 is used.
Examples
This example uses an implicit RUN command to invoke the portmapper process.
The process runs with CPU 1 as the primary CPU and CPU 0 as the backup.
PORTMAP / NAME $ZRPC, PRI 148, NOWAIT,&
CPU 1, OUT $ZHOME, IN $ZHOME / BACKUPCPU 0, TCPIP $ZTC0
This example shows an explicit RUN command:
RUN $SYSTEM.SYSnn.PORTMAP / NAME $ZRPC, PRI 148, NOWAIT,&
CPU 1, OUT $ZHOME, IN $ZHOME /BACKUPCPU 0, TCPIP $ZTC0
where $SYSTEM.SYSnn is the name of the system subvolume the portmapper
program resides on.
Considerations
Only one portmapper can be started for the entire Parallel Library TCP/IP
subsystem irrespective of the number of TCPSAM processes.
Error messages received on startup are displayed on the OUT file if possible. If an
error occurs when the process is writing to the OUT file, the home terminal is used.
If the home terminal is specified, it cannot be a transient process or window.
Operating system ASSIGN commands are ignored.
Because the portmapper uses the sockets library provided by the NonStop Kernel
TCP/IP, a PARAM for TCPIP^HOST^FILE must be specified if the Domain Name
Resolver is not being used. For example:
PARAM TCPIP^HOST^FILE $SYSTEM.ZTCPIP.HOSTS
For more information on TCP/IP configuration files, see the TCP/IP Configuration and
Management Manual.