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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-41
Stopping the OSS Message-Queue Server
If the OSS name server becomes unstoppable, do one of the following:
•
Repair all filesets involved using the OSS Monitor SCF DIAGNOSE FILESET
Command, restart them, then stop them again.
•
Add a new fileset to be managed by the unstoppable OSS name server (see the
ADD FILESET Command on page 12-8 for command syntax). Start and stop that
fileset; for example, if the new fileset is named DUMMY, enter:
START FILESET $ZPMON.DUMMY
STOP FILESET $ZPMON.DUMMY
The fileset can be deleted as soon as it stops.
•
Reassign an existing fileset to the unstoppable OSS name server; use the OSS
Monitor SCF ALTER FILESET Command on the fileset to change the
NAMESERVER attribute for the fileset. Stop that fileset; for example, if you decide
to use the TEMP fileset to fix this problem, enter:
STOP FILESET $ZPMON.TEMP
Remember to reassign the fileset to its proper OSS name server and restart it
again.
The unstoppable OSS name server should stop as soon as the last of its filesets stops.
Stopping the OSS Message-Queue Server
1. Make sure that you are a member of the super group (255, nnn).
2. Enter the OSS shell ipcs command to determine whether any message queues
are in use. If any message queues are in use, notify OSS users of the pending
shutdown of the OSS message-queue server. You can use a method similar to the
one described under Manually Stopping the OSS File System and the OSS
Environment on page 2-3.
See the ipcs(1)reference page either online or in the Open System Services
Shell and Utilities Reference Manual for more information about this utility.
3. Issue the following OSS Monitor SCF command:
STOP SERVER $ZPMON.#ZMSGQ
As soon as the server stops, any OSS application that was still using an OSS
message queue should halt itself. All stale message queues are automatically
removed.
Stopping the OSS Sockets Local Server
When you stop the OSS sockets local server, the server notifies all applications using
AF_UNIX sockets by closing their open sockets. Depending on how an application has
been coded, this action might cause the application to fail.
1. Make sure that you are a member of the super group (255,nnn).