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

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-002
2-4
Manually Stopping the OSS File System and the
OSS Environment
however, the most commonly used signal can be sent by entering the OSS
shell command:
kill PID1 PID2 PID3 ...
where PID1, PID2, and PID3 are OSS process IDs displayed by the ps
command.
To avoid specifying the individual PIDs, which can make command entry a
lengthy and potentially error-prone step, write an OSS shell script to extract
the PID numbers from the ps command output and pipe those numbers
into the kill command.
•
When an application process ignores normal shutdown signals, you can
use force shutdown by entering:
kill -s KILL PID1 PID2 PID3 ...
where PID1, PID2, and PID3 are OSS process IDs displayed by the ps
command.
For more information about the ps and kill commands, see the ps(1) and
kill(1) reference pages either online or in the Open System Services Shell and
Utilities Reference Manual.
3. Stop all servers managed by the OSS Monitor by entering the following Subsystem
Control Facility (SCF) commands:
ASSUME PROCESS $ZPMON
STOP SERVER *
4. Stop (unmount) all filesets mounted on the root fileset and the root fileset itself by
entering the following SCF commands:
ASSUME PROCESS $ZPMON
STOP FILESET *
The wildcard form of the STOP FILESET command stops all filesets in the reverse
of the order that they were started (mounted).
5. After the last fileset stops, stop the OSS Monitor process:
•
If the OSS Monitor is running as a standard process, enter the following at a
TACL prompt:
STOP $ZPMON
•
If the OSS Monitor is running as a persistent process, enter the following at an
SCF prompt:
ABORT PROCESS $ZZKRN.#ZPMON
Note. The process device identifier #ZPMON is the convention used throughout this guide;
your site might use another naming convention such as #OSMON or #OSSMN. The process
name $ZPMON is required by the OSS Monitor process itself; however, the process device
identifier used within the Kernel subsystem is not required to be #ZPMON.