Open System Services NFS Management and Operations Guide

• A domain name resolver process can be specified using the DEFINE
=TCPIP^RESOLVER^NAME. For example:
ADD DEFINE =TCPIP^RESOLVER^NAME, FILE resfile
This DEFINE cannot be used if the DEFINE =TCPIP^HOST^FILE is specified. For other restrictions
on this DEFINE, see the portmap(1) reference page either online or in the Open System
Services Shell and Utilities Reference Manual.
• Because the port mapper uses the sockets library provided by NonStop TCP/IP, if a domain
name resolver is not being used, the DEFINE =TCPIP^HOST^FILE must be specified. For
example:
ADD DEFINE =TCPIP^HOST^FILE, CLASS MAP, &
FILE $SYSTEM.ZTCPIP.HOSTS
• For the RPCINFO program to function correctly, the RPC file must be specified to configure
well-known RPC programs. If the RPC file is not located in $SYSTEM.ZRPC.RPC, you can use
the following DEFINE to indicate its location:
ADD DEFINE =ZRPC^RPC^FILE, CLASS MAP, &
FILE $DATA.ZRPC.RPC
For detailed information on NonStop TCP/IP configuration files, see the TCP/IP configuration
and management manual appropriate to your system.
• The port mapper must be run by a user in the super group.
• The HOSTID attribute in NonStop TCP/IP must be set to the host IP address.
• A permanent device name must be supplied for IN, OUT, and TERM. If you use the name of
a Telserv dynamic window instead, the port mapper will fail during a backup takeover.
Error Messages
The port mapper process can return these error messages. In addition to these error messages,
invoking the port mapper might result in I/O error messages or NonStop TCP/IP socket library
error messages.
portmap: backup cpu nnn is not valid
The specified backup processor either does not exist or is the same as the primary processor.
portmap: collect-name is not a valid collector process
The specified EMS collector is not an existing collector process.
portmap: process must be named
The port mapper process was run as an unnamed process. Run it again, but with the NAME
parameter specified.
portmap: process name does not exist
The specified EMS collector or NonStop TCP/IP process does not exist.
portmap: tcpip-process-name is not a valid tcpip process
The specified process has the wrong process type; it must be a NonStop TCP/IP process (device
type 48, subtype 0).
Configuring OSS NFS Objects
Table 1 lists the relationships among OSS NFS objects and processes. The “Means of Adding”
column indicates whether the object is configured using SCF or the TACL RUN command. The
“Configuration Requirement” column indicates whether the object is required or optional.
Configuring OSS NFS Objects 41