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

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.
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 stopping the OSS
SEEP. For details of OSS SEEP, see “Using an OSS Security Event-Exit Process (SEEP)” (page 231).
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” (page 47).
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 an OSS Sockets Local Server
To stop an OSS local server, all AF_UNIX sockets using that server must be closed or the STOP
SERVER command will fail:
1. Make sure that you are a member of the super group (255,nnn).
2. Warn your users. You can use a method similar to the one described under “Manually Stopping
the OSS File System and the OSS Environment” (page 47).
3. If the system is running AF_UNIX Release 1 software, issue the following OSS Monitor SCF
command:
STOP SERVER $ZPMON.#ZPLS
4. If the system is running AF_UNIX Release 2 software, issue the following OSS Monitor SCF
command:
STOP SERVER $ZPMON.#ZLSnn
where nn is the processor number.
Stopping an OSS Transport Agent Server
If you need to shut down the QIO subsystem, you must first stop the OSS transport-agent server.
For more information about the QIO subsystem, see the QIO Configuration and Management
Manual.
To stop an OSS transport-agent server:
1. Make sure you are a member of the super group (255, nnn).
2. Warn your users. You can use a method similar to the one described under “Manually Stopping
the OSS File System and the OSS Environment” (page 47).
134 Managing Servers