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

5. Locate and stop all OSS applications that use AF_UNIX sockets.
When you stop the OSS sockets local server to restart it using the new configuration, 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.
6. Use the following OSS Monitor SCF command to stop the server:
STOP SERVER $ZPMON.#ZPLS
7. Use the following OSS Monitor SCF command to restart the reconfigured server:
START SERVER $ZPMON.#ZPLS
8. If feasible, restart all applications using OSS AF_UNIX sockets.
Reconfiguring a Network Services Server
Most network services servers ignore changes to configuration files while they are running. The
BIND 9 domain name server named can be reconfigured using the rndc or nsupdate utility, as
described in the DNS Configuration and Management Manual and the nsupdate(8) and
rndc(8) reference pages online.
Configuration files such as /etc/inetd.conf can be edited while the servers are running.
However, to make such configuration changes take effect, 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” (page 47).
2. Stop or interrupt 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 interrupt the inetd process, enter commands similar to the following:
ps
.
.
.
kill -s SIGHUP 4291
where 4291 is the OSS process ID of the inetd process. This form of the kill command
sends the SIGHUP signal to the inetd process; inetd rereads its current configuration file
in response to this signal and continues to run using the new configuration.
Removing a Server
How and when you remove a server depends on the type of server. You cannot remove the OSS
sockets local server, the OSS message-queue server, or an OSS transport-agent server.
• “Removing an OSS Name Server” (page 138)
• “Removing a Network Services Server” (page 139)
Other servers used by OSS applications require separate procedures. For more information, see
the manual appropriate for a specific server.
Removing an OSS Name Server
You remove an OSS name server by removing its entry in the Enscribe database ZOSSSERV file.
NOTE: You cannot remove the OSS name server for the root fileset, $ZPNS.
1. Make sure that you are a member of the super group (255,nnn).
2. Use the following OSS Monitor SCF command to determine which filesets are managed by
the OSS name server that you want to remove:
INFO FILESET $ZPMON.*, DETAIL
See the “INFO FILESET Command” (page 296) for a description of the output.
138 Managing Servers