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

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-37
Starting the OSS Message-Queue Server
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 fileset selected in Step 2a are started. See the STATUS
FILESET Command on page 12-67 for a description of the output.
d. Issue the OSS Monitor SCF START FILESET Command for any unstarted
filesets identified in Step 2c.
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.
Starting the OSS Message-Queue Server
You can start an 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 on page 12-28 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
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 on page 12-28 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