Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-32
Configuring Network Services Servers, Tools, and
Applications
•
You must keep track of the process names or OSS process IDs (PIDs) that OSS
sockets applications use so that those processes running in a specific processor
(and possibly all processes used by the same application) can be stopped before
you stop an OSS transport agent server.
•
You might want to run multiple TCP/IP processes for scalability or load-leveling.
Then you can assign OSS AF_INET or AF_INET6 sockets applications to a
specific transport-provider process so that the default transport-provider process
for your node is not overloaded.
Setting Up an Alternative to $ZTC0
If your node does not run a $ZTC0 process, determine the name of the TCP/IP
process that is used instead and create a NonStop operating system DEFINE for it. For
example:
DEFINE =TCPIP^PROCESS^NAME, FILE $B018
Add this DEFINE to the TACLLOCL file that is executed whenever a TACL session is
started. If your users do not always login through TACL, follow the equivalent
procedure for the /etc/profile file (under Changing the Transport-Provider
Process) to add the DEFINE to all OSS shells when they are started.
Configuring Network Services
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. If your users do not always login
through TACL, follow the equivalent procedure for the /etc/profile file (under
Changing the Transport-Provider Process) to add the DEFINE to all OSS shells when
they are started:
DEFINE =TCPIP^HOST^FILE, FILE $SYSTEM.ZTCPIP.IPNODES
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