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

fileset are started. See the “STATUS FILESET Command” (page 314) for a description of
the output.
d. Issue the OSS Monitor SCF START FILESET command for any unstarted filesets identified
in the previous step.
3. Issue the OSS Monitor SCF START FILESET command for the OSS name server’s fileset and
for any unstarted filesets that are mounted on it.
The OSS name server starts automatically when the first of its filesets starts.
Beginning with the J06.15 and H06.26 RVUs, an OSS Security Event-Exit Process (SEEP) is supported
and provides additional file-access authorization. The OSS name server controls starting the OSS
SEEP. For details of OSS SEEP, see “Using an OSS Security Event-Exit Process (SEEP)” (page 231).
Starting the OSS Message-Queue Server
You can start the OSS message-queue server:
• As part of bringing up the OSS environment by using the STARTOSS Utility
• Automatically using the automatic startup service (see the “ALTER SERVER Command” (page 278)
for more information about that alternative)
• Manually using the following procedure
To start this server manually when the system is brought up or to restart this server if it fails:
1. Make sure that you are a member of the super group (255,nnn).
2. Enter the OSS Monitor SCF command:
START SERVER $ZPMON.#ZMSGQ
Starting the OSS Sockets Local Server
If the system is running AF_UNIX Release 2 software, the OSS sockets local server for each processor
is started automatically when the processor starts.
To restart an OSS sockets local server 2 server manually:
1. Make sure that you are a member of the super group (255,nnn)
2. Enter the OSS Monitor SCF command:
START SERVER $ZPMON.#ZLSnn
where nn is the processor number.
For systems running AF_UNIX Release 1 software, you can start an OSS sockets local server:
• As part of bringing up the OSS environment by using the STARTOSS Utility
• Automatically using the automatic startup service (see the “ALTER SERVER Command” (page 278)
for more information about that alternative)
• Manually using the following procedure
To start this server manually when the system is brought up or to restart this server if it fails:
1. Make sure that you are a member of the super group (255,nnn)
2. Enter the OSS Monitor SCF command:
START SERVER $ZPMON.#ZPLS
Starting an OSS Transport Agent Server
An OSS transport agent is started automatically when its processor starts. You do not need to start
an OSS transport-agent server to use an OSS AF_UNIX, OSS AF_INET, or OSS AF_INET6
sockets application in a given processor.
To restart a stopped OSS transport-agent server:
1. Make sure that you are a member of the super group (255,nnn).
128 Managing Servers