Open System Services NFS SCF Reference Manual

SCF Commands for OSS NFS
Open System Services NFS SCF Reference Manual—522582-001
2-70
Considerations
Considerations
Consider the following points when using the START SUBSYS command:
•
START SUBSYS is a sensitive command requiring super-group access.
•
When you start the SUBSYS object, the SUBSYS object must be in the STOPPED
summary state.
•
The SUBSYS object is considered to be in the STARTED summary state upon the
successful completion of a START SUBSYS command or upon the successful
starting of any LAN interface or server process. Once started, the SUBSYS object
can only be stopped by issuing a STOP or ABORT SUBSYS command or by
externally stopping the manager process; explicitly stopping all LAN interface and
server processes does not stop the SUBSYS object.
•
Starting a server has the effect of performing a local mount using the server’s mount
point. You must start SERVER objects in the correct order; that is, start at the root
of the local file hierarchy so that each server’s mount point is defined at the time it is
started.
If you use the START SUBSYS command to start multiple SERVER objects, the
SERVER objects are started in the same sequence that they were originally started.
•
When used with a SUBSYS object, the SUB and SEL options operate just as they do
with any other objects. However, when you specify SUB ALL for a SUBSYS
object and specify a state with the SEL option, the set of objects selected is affected
by changes in the states of PROCESS, LAN, and SERVER objects caused by the
operation. For further details, see the following examples.
Examples
Assume LAN0 and SRV1 are restartable processes, and SRV2 and SRV3 are not
restartable.
The following command starts the OSS NFS subsystem associated with the manager
process $ZNFS, and any restartable LAN and SERVER objects:
->START SUBSYS $ZNFS
This command would start LAN 1 and SRV1, but not SRV2 or SRV3.
The next command starts the OSS NFS subsystem, any restartable LAN and SERVER
objects, and all LAN and SERVER objects in the STOPPED summary state:
->START SUBSYS, SUB ALL, SEL STOPPED
Again, the LAN0 and SRV1 objects are started as part of starting the subsystem because
they are restartable processes. The SRV2 and SRV3 objects, although not restartable,
are started because they are subordinate objects in the STOPPED summary state (that is,
when the SUB option is applied to a START SUBSYS command, you are actually
applying the START command to a different set of objects and the command then
executes according to the rules for that particular object. In this case, the SUB ALL
option, results in the generation of a START SERVER command.)