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

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-45
Stopping an OSS Transport Agent Server
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 on page 2-3.
3. Issue the following OSS Monitor SCF command:
STOP SERVER $ZPMON.#ZPLS
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 on page 2-3.
Identify and stop all OSS applications that use OSS AF_UNIX or OSS AF_INET
sockets in the processor served by the OSS transport agent that you want to stop. An
OSS transport agent server will not shut down if it is servicing an open socket.
Use an OSS Monitor SCF STOP SERVER Command to stop the OSS transport agent
server. For example:
STOP SERVER $ZPMON.#ZTA15
Stopping a Network Services Server
Network services servers do not shut down if they are in use. You must:
1. Warn your users. 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.
2. Stop each process separately by identifying its OSS process ID (PID) using the ps
command from an OSS shell prompt and then issuing a kill command.
For example, to stop the inetd process, enter commands similar to the following:
ps
.
.
.
kill -s KILL 4291
where 4291 is the OSS process ID of the inetd process. This form of the kill
command sends the nondefault KILL signal to the inetd process.