Open System Services Management and Operations Guide (G06.27+, H06.04+)

Managing Servers
Open System Services Management and Operations Guide—527191-003
4-35
Configuring Network Services Servers, Tools, and
Applications
•
You must configure network services that such applications might use.
You configure the necessary network services by making AF_INET or AF_INET6
sockets configuration files available in the OSS file system. To prevent confusion
and conflicts between servers, use and maintain the Guardian version of the
AF_INET or AF_INET6 sockets configuration files for both environments. Set up
the Guardian files for use from the OSS environment by creating symbolic links
between the Guardian files and the /etc directory. Check that the files or links do
not already exist in the /etc directory, then create them if necessary:
cd /etc
ls -al
...
ln -s /G/system/ztcpip/networks networks
ln -s /G/system/ztcpip/protocol protocols
ln -s /G/system/ztcpip/services services
ln -s /G/system/ztcpip/hosts hosts
To use the full NonStop TCP/IPv6 addressing capabilities instead of the
/etc/hosts file, add the following NonStop operating system DEFINE to the
TACLLOCL file that is executed whenever a TACL session is started:
DEFINE =TCPIP^HOST^FILE, FILE $SYSTEM.ZTCPIP.IPNODES
If your users do not always login through TACL, follow the equivalent procedure for
the /etc/profile file to add the DEFINE to all OSS shells when they are
started.
Note that OSS AF_INET or AF_INET6 sockets and the inetd process use almost
the same set of configuration files. NonStop TCP/IPv6 searches for host
information can be controlled by the environment variable
TCPIP_RESOLVER_ORDER, as described in the environ(5) reference page,
either online or in the Open System Services System Calls Reference Manual.
This environment variable can be set in the .profile file on a user-by-user basis
or in /etc/profile for all shell processes that launch OSS sockets programs.
•
You can change the transport-provider process used for OSS AF_INET or
AF_INET6 sockets by specifying a NonStop operating system DEFINE. This ability
is useful when your node runs several copies of its TCP/IP processes or when you
run more than one NonStop TCP/IP product at the same time and want to
distribute workload between them.
For example, the following DEFINE allows the $ZTC1 process to be used as an
OSS AF_INET transport-provider process:
add_define =TCPIP^PROCESS^NAME, FILE \$ZTC1
If the DEFINE is declared in the /etc/profile file, then all OSS AF_INET or
AF_INET6 sockets applications that are started from an OSS shell prompt use the
specified transport provider process. If the DEFINE is declared in the .profile
file of a specific user, you can control workload distribution on the basis of user.