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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-33
Starting a Server
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.
Changing the Transport-Provider Process
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.
Starting a Server
How and when you start a server depends on the type of server:
•
Starting an OSS Name Server on page 4-33
•
Starting the OSS Message-Queue Server on page 4-34
•
Starting the OSS Sockets Local Server on page 4-34
•
Starting an OSS Transport Agent Server on page 4-35
•
Starting a Network Services Server on page 4-35
Other servers used by OSS applications require separate procedures. For more
information, see the manual appropriate for a specific server.
Starting an OSS Name Server
You do not start an OSS name server directly. Instead, you start at least one of the
filesets that it services.
You can start an OSS name server:
•
As part of bringing up the OSS environment by using the STARTOSS Utility
•
Automatically by having one of its filesets started using the automatic startup
service (see the ADD FILESET Command on page 12-8 for more information
about that alternative)
•
Manually using the following procedure