Open System Services NFS Management and Operations Guide

OSS NFS Object Types
The OSS NFS subsystem consists of these object types:
Identifies the OSS NFS subsystem as a whole.SUBSYS
Identifies the OSS NFS manager process. There is only one PROCESS object in an OSS NFS
subsystem.
PROCESS
Identifies a server-controlled fileset that is available to remote NFS clients. Attributes of an EXPORT
object specify which clients can access the fileset.
EXPORT
Identifies a group of OSS NFS users who have common access authority. It provides mapping
between OSS NFS group numbers and group names.
GROUP
Identifies a local area network (LAN) interface process that acts as a front end to other objects for
OSS NFS requests received from the NonStop TCP/IP communications process.
LAN
Identifies by a single name a group of host machines and their users. This one name can be used
in Export objects to grant fileset access to the entire netgroup.
NETGROUP
Identifies a server process that provides access to a single OSS fileset. The root of this fileset is the
mount point of the server.
SERVER
Identifies a person registered to use OSS NFS. It defines the OSS NFS user ID and links that user
ID to an operating system user ID. The OS user ID must exist before the OSS NFS user can be linked
to it.
USER
OSS NFS Object Names
OSS NFS object naming conventions are clearly spelled out in the Open System Services NFS SCF
Reference Manual, which should be consulted for constructing names. This summary lists the basic
OSS NFS object naming conventions:
[\system.][$mgr.]objname
where each of the object-name components are defined as:
• \system
is the name of the system on which the manager process resides. System names follow the
standard NonStop operating system naming conventions and cannot contain wildcard
characters.
• $mgr
is the name of the NFS manager process (usually $ZNFS). Names of OSS NFS objects other
than SUBSYS or PROCESS that are the target of an SCF command must be prefixed by $mgr,
which determines which manager process receives the command. An object name must contain
this prefix unless the currently assumed object name (from a previously entered ASSUME
command) is the manager process name.
• objname
is the actual name of the specific object. The syntax and format of this portion of the object
name varies based on the object type. Names of objects are treated by SCF as subdevice
names. OSS NFS object names differ from typical SCF subdevice names in two respects:
◦ Names of devices and filesets start with a pound sign (#), but others might not.
◦ The names of some OSS NFS objects are case-sensitive.
When an SCF command, such as VERSION or NAMES, addresses the OSS NFS manager process
itself, the object name (following the dot) is simply left blank, or null.
Object names specified as attributes, such as the SERVER attribute of the TRACE LAN command,
need not include the manager process name.
26 Management Environment for OSS NFS