Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

To create sockets in compatibility mode, choose $ZPLS. To create sockets in portability mode,
choose $ZAFN2.
NOTE: Neither $ZPLS nor $ZAFN2 is a process that runs on the system.
The DEFINE determines the initial value of the AF_UNIX socket transport provider. If the DEFINE
is not present, then sockets are created in compatibility mode (transport provider $ZPLS).
If the DEFINE is declared in the /etc/profile file, then all OSS AF_UNIX 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, sockets created by
AF_UNIX sockets applications run by that user are created in the mode specified by the DEFINE
(unless the application overrides the transport-provider name).
An application can override the transport provider name, and thus the mode of sockets it
creates, by using either the DEFINE or by calling the socket_transport_name_set()
function.
For more information about AF_UNIX Release 2, compatibility mode, and portability mode,
see the Open System Services Programmer's Guide.
Starting a Server
How and when you start a server depends on the type of server:
• “Starting an OSS Name Server” (page 127)
• “Starting the OSS Message-Queue Server” (page 128)
• “Starting the OSS Sockets Local Server” (page 128)
• “Starting an OSS Transport Agent Server” (page 128)
• “Starting an OSS Resource Agent Server” (page 129)
• “Starting a Network Services Server” (page 129)
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” (page 256) 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” (page 296) 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.
c. Use the OSS Monitor SCF STATUS FILESET $ZPMON.*, DETAIL command to make sure
that all filesets with mount points between / and the mount point directory for the selected
Configuration Files 127