Open System Services Shell and Utilities Reference Manual (G06.25+, H06.03+)

Miscellaneous Files and Commands portmap(8)
• Each TCP/IP server is associated with a host name and an IP address (called a Host ID in
Subsystem Control Facility [SCF] displays). The corresponding portmapper process
returns information for that IP address.
• The IP address for each TCP/IP server process (and, if naming conventions were followed,
for its corresponding portmapper process) can be determined by entering the following
SCF command:
INFO PROCESS $ZTC*, DETAIL
For parallel library TCP/IP, only one portmapper process can be started for the entire TCP/IP sub-
system, regardless of how many TCPSAM processes are running.
• By convention, each portmapper process name contains the fourth and fifth characters of
the TCPSAM process name.
• Even though only one portmapper process can be started, it serves all the IP addresses
associated with the parallel library TCP/IP subsystem.
When starting a copy of the portmapper process, the digit to use in its process name can be deter-
mined by the same method:
• Use an SCF command to determine the IP address for each TCP/IP server process and the
digit from the correct corresponding TCP/IP process name.
DIAGNOSTICS
In addition to the following messages, the portmapper program generates EMS error messages for
problems encountered during socket or file input or output.
portmap: backup CPU nn is not valid
The specified backup processor does not exist, or it is the same as the processor
used for the primary portmapper process.
portmap: name is not a valid tcpip process
The process specified by name is the wrong process type to function as a valid
TCP/IP server process. Specify a valid process name for a process of device type
48, device subtype 0.
portmap: name is not a valid collector process
The process specified by name is not an existing EMS collector process.
portmap: process must be named
The portmapper program was started as an unnamed process. The portmapper pro-
gram must run as a named process.
portmap: process name does not exist
The process name specified by name for the EMS collector or TCP/IP server pro-
cess does not identify a running process.
RELATED INFORMATION
Commands: inetd(8), rpcinfo(8).
STANDARDS CONFORMANCE
This command is an HP extension to the XPG4 Version 2 specification.
The HP implementation of the portmapper program depends upon an RPC implementation that
conforms to the Defense Data Network (DDN) Request for Comments (RFC) 1057.
527188-003 Hewlett-Packard Company 12−25