Open System Services NFS Management and Operations Guide

OSS Object Name Examples
SUBSYS objects are specified by the process name of the manager process, namely $ZNFS.SUBSYS
The manager PROCESS object is specified by the conventional name, $ZNFS.PROCESS
The object name is the OSS pathname that identifies the directory being exported.EXPORT
A GROUP object name is formed by specifying this OSS NFS group name as a subdevice of the
manager process; for example, $ZNFS.SOFTWARE.
GROUP
A LAN object name is formed by specifying this LAN name as a subdevice of the manager process;
for example, $ZNFS.#LAN0.
LAN
A NETGROUP object name is formed by specifying this OSS NFS netgroup name as a subdevice
of the manager process; for example, $ZNFS.REGHOSTS.
NETGROUP
A SERVER object name is formed by specifying this server process name as a subdevice of the
manager process; for example, $ZNFS.#ROOT.
SERVER
A USER object name is formed by specifying this OSS NFS user name as a subdevice of the
manager process; for example, $ZNFS.RICHARD.
USER
SCF allows you to specify multiple objects in a single command by using either object-name lists
or templates, as described in the Open System Services NFS SCF Reference Manual.
Names of Entities Outside of OSS NFS
In addition to OSS NFS object types, which are defined and controlled by the OSS NFS subsystem,
OSS NFS sometimes requires information about host and domain entities defined by the NonStop
TCP/IP environment. These are case-sensitive, externally defined names that can contain up to 254
characters. OSS NFS imposes no restrictions on the characters that appear in these names. However,
other network software (such as e-mail) might not work with names that contain certain nonalphabetic
or nonnumeric characters.
Object Attributes
An object attribute is a characteristic of an object that takes on specified values. Many attributes
have default values that you can modify by commands. The INFO command displays the current
attribute values for an object. The required syntax for and meaning of each attribute are described
under the individual commands in the Open System Services NFS SCF Reference Manual.
Object States
objects assume operational states, some which determine how certain commands affect the objects.
The SUBSYS, PROCESS, SERVER, and LAN objects have object states; the EXPORT, GROUP,
NETGROUP, and USER objects do not. The object states are:
An object in the STOPPED state is defined but not available for service requests. An object is
placed in the STOPPED state when the OSS NFS subsystem first comes up, when an object is
STOPPED
added with the ADD command but has not been started, or when the object has been stopped
by a STOP command.
An object in the STARTING state is in the process of being initialized. Once the initialization is
finished, the object is placed in the STARTED state.
STARTING
An object in the STARTED state has been initialized and is either in the process of handling user
traffic or ready to accept user input.
STARTED
An object in the STOPPING state is being brought to the STOPPED state in a orderly manner,
and no new service requests are accepted. No corruption of data or disruption of any in-progress
STOPPING
operation occurs. Once all deactivating operations are finished, the object is placed in the
STOPPED state.
Using SCF to Manage OSS NFS 27