Open System Services NFS SCF Reference Manual

Introduction

Open System Services NFS SCF Reference Manual—522582-001

1-3

Object Types

Using SCF you can manipulate the OSS NFS subsystem by entering commands that act

on one or more objects. Each OSS NFS subsystem object belongs to a particular object

type. An object name uniquely identifies a specific object within the subsystem.

Figure 1-2

shows the object types supported by OSS NFS and their hierarchical order.

The SUBSYS (subsystem) object is at the highest point in the hierarchy. The PROCESS

object is subordinate to the SUBSYS object, and all other objects are peers and are

subordinate to the PROCESS object. The hierarchy is important when issuing

commands to the OSS NFS subsystem for processing. For example, because the LAN

and SERVER objects are subordinate to the PROCESS object, any commands pertaining

to a LAN or SERVER can be issued only when the PROCESS object is in the

STARTED summary state. (See Summary States

on page 1-7.)

The description of each object type is as follows:

SUBSYS Identifies the OSS NFS subsystem as a whole. There is only one

SUBSYS object for each OSS NFS subsystem. The name of the

SUBSYS object is the manager process name. Remote mounts

requested by NFS clients are considered to be opens of the SUBSYS

object.

PROCESS Identifies the OSS NFS manager process. There is only one PROCESS

object for each OSS NFS subsystem. The manager process is

responsible for handling SPI requests, and starting, controlling, and

stopping all other subsystem processes.

The name of a PROCESS object is the manager process name. The

recommended name for the manager process is $ZNFS.

Figure 1-2. NFS Object Hierarchy

EXPORT GROUP LAN NETGROUP SERVER USER

SUBSYS

PROCESS

003