Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-36
Starting a Server
•
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.
Starting a Server
How and when you start a server depends on the type of server:
•
Starting an OSS Name Server on page 4-36
•
Starting the OSS Message-Queue Server on page 4-37
•
Starting the OSS Sockets Local Server on page 4-37
•
Starting an OSS Transport Agent Server on page 4-38
•
Starting a Network Services Server on page 4-38
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-7 for more information
about that alternative)
•
Manually using the following procedure
1. Make sure that you are a member of the super group (255,nnn).
2. If the OSS name server you want to start is not the OSS name server for the root
fileset:
a. Use the OSS Monitor SCF INFO FILESET $ZPMON.*, DETAIL command to
select the fileset the OSS name server manages that has a mount point closest
in the file system directory hierarchy to the / directory. See the INFO FILESET
Command on page 12-48 for a description of the output.
b. Use the OSS shell ls -l command to make sure that the mount point is
defined as a directory in the OSS file system. If it is not, use the OSS shell
mkdir command to define it.