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

Stopping a Server
How and when you stop a server depends on the type of server.
• “Stopping a Specific OSS Name Server” (page 133)
• “Stopping the OSS Message-Queue Server” (page 134)
• “Stopping an OSS Sockets Local Server” (page 134)
• “Stopping an OSS Transport Agent Server” (page 134)
• “Stopping an OSS Resource Agent Server” (page 135)
• “Stopping a Network Services Server” (page 135)
Other servers used by OSS applications require separate procedures. For more information, see
the manual appropriate for a specific server.
If your site uses the STOPOSS utility, it stops all OSS name servers but does not affect other servers
listed here; those servers need not be stopped to shut down a node. See “STOPOSS Utility”
(page 406) for more information about that alternative.
Stopping a Specific OSS Name Server
1. To identify all filesets managed by the OSS name server you intend to stop, enter the OSS
Monitor SCF command:
INFO FILESET $ZPMON.*, DETAIL
See the “INFO FILESET Command” (page 296) for a description of the command output.
2. Make sure that you are a member of the super group (255,nnn).
3. Warn your users to make sure that all their files in affected filesets are closed and all OSS
shell sessions using those filesets are terminated. You can use a method similar to the one
described under “Manually Stopping the OSS File System and the OSS Environment” (page 47).
4. Do one of the following:
• If the OSS name server is the server for the root fileset, stop all filesets by entering the
following OSS Monitor SCF command:
STOP FILESET $ZPMON.*
• If the OSS name server is not the server for the root fileset, reassign all filesets it manages
to another running OSS name server. Use the OSS Monitor SCF ALTER FILESET command
on each fileset to change the NAMESERVER attribute for the fileset.
The OSS name server should stop as soon as the last of its filesets stops.
When an OSS name server first starts, it might become “unstoppable” if one of the following is
true:
• The OSS name server manages only one fileset and that fileset cannot be started.
• The OSS name server manages multiple filesets and none of them can be started.
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” (page 256) 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
Configuration Files 133