Open System Services NFS SCF Reference Manual Abstract This manual describes the use of the Subsystem Control Facility (SCF) to configure and maintain the Compaq NonStop™ Kernel Open System Services (OSS) Network File System (NFS). It is written for system managers and operators. Product Version OSS NFS G00 Supported Releases This manual supports function added to the D41.
Document History Part Number Product Version Published 114423 OSS NFS D40 May 1996 420036-001 OSS NFS G00 December 1998 522582-001 OSS NFS G00 February 2002 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
Open System Services NFS SCF Reference Manual Glossary Index Figures Tables What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi xi Intended Audience How to Use this Manual xi Where to Go for More Information xi xii Your Comments Invited Notation Conventions xiii 1.
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) ABORT LAN Command 2-5 Considerations 2-6 Example 2-6 ABORT SERVER Command 2-7 Considerations 2-7 Example 2-8 ABORT SUBSYS Command 2-8 Considerations 2-8 Example 2-9 ADD EXPORT Command 2-9 Considerations 2-10 Examples 2-10 ADD GROUP Command 2-11 Considerations 2-11 Examples 2-12 ADD LAN Command 2-12 Considerations 2-14 Examples 2-15 ADD NETGROUP Command 2-15 Considerations 2-16 Example 2-16 ADD SERVER Command 2-16
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) ALTER EXPORT Command 2-23 Considerations 2-23 Example 2-24 ALTER GROUP Command 2-24 Considerations 2-24 Example 2-25 ALTER LAN Command 2-25 Considerations 2-28 Example 2-28 ALTER NETGROUP Command 2-28 Considerations 2-29 Example 2-29 ALTER PROCESS Command 2-30 Considerations 2-31 Example 2-31 ALTER SERVER Command 2-32 Considerations 2-34 Example 2-35 ALTER SUBSYS Command 2-35 Considerations 2-35 Example 2-36 ALTER USER Comm
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) DELETE LAN Command 2-39 Considerations 2-39 Example 2-39 DELETE NETGROUP Command 2-39 Considerations 2-39 Example 2-40 DELETE SERVER Command 2-40 Considerations 2-40 Example 2-40 DELETE USER Command 2-41 Considerations 2-41 Example 2-41 INFO EXPORT Command 2-41 Considerations 2-42 Examples 2-42 INFO GROUP Command 2-43 Considerations 2-43 Examples 2-44 INFO LAN Command 2-44 Considerations 2-45 Examples 2-45 INFO NETG
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) LISTOPENS PROCESS Command 2-56 Considerations 2-56 Example 2-56 LISTOPENS SUBSYS Command 2-57 Considerations 2-57 Examples 2-57 NAMES EXPORT Command 2-58 Considerations 2-59 Example 2-59 NAMES GROUP Command 2-59 Considerations 2-59 Example 2-60 NAMES LAN Command 2-60 Considerations 2-60 Example 2-60 NAMES NETGROUP Command 2-61 Considerations 2-61 Example 2-61 NAMES PROCESS Command 2-62 Considerations 2-62 Exampl
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) PRIMARY PROCESS Command 2-66 Considerations 2-66 Example 2-66 START LAN Command 2-66 Considerations 2-67 Example 2-68 START SERVER Command 2-68 Considerations 2-68 Example 2-69 START SUBSYS Command 2-69 Considerations 2-70 Examples 2-70 STATS LAN Command 2-71 Considerations 2-71 Example 2-72 STATS PROCESS Command 2-73 Considerations 2-74 Example 2-74 STATS SERVER Command 2-76 Considerations 2-76 Example 2-77 STA
SCF Commands for OSS NFS (continued) Contents SCF Commands for OSS NFS (continued) STATUS SUBSYS Command 2-85 Considerations 2-85 Examples 2-86 STOP LAN Command 2-87 Considerations 2-87 Example 2-88 STOP SERVER Command 2-89 Considerations 2-89 Example 2-90 STOP SUBSYS Command 2-90 Considerations 2-91 Example 2-92 STOPOPENS SUBSYS Command 2-92 Considerations 2-93 Example 2-93 TRACE LAN Command 2-93 Considerations 2-96 Examples 2-97 VERSION LAN Command 2-97 Considerations 2-98 Example 2-98 VERSION
A. SCF Command Summary for OSS NFS Contents A. SCF Command Summary for OSS NFS B. Summary of All SCF Commands Glossary Index Figures Figure 1-1. SCF and the OSS NFS Subsystem Figure 1-2. NFS Object Hierarchy 1-2 1-3 Tables Table 1-1. Naming Conventions for OSS NFS Objects 1-5 Table 2-1. SCF Commands and Objects for OSS NFS 2-2 Table 2-2. NULL-ALIAS-OK Interactions With the “Nobody” Alias Table B-1.
What’s New in This Manual Manual Information Open System Services NFS SCF Reference Manual Abstract This manual describes the use of the Subsystem Control Facility (SCF) to configure and maintain the Compaq NonStop™ Kernel Open System Services (OSS) Network File System (NFS). It is written for system managers and operators. Product Version OSS NFS G00 Supported Releases This manual supports function added to the D41.
What’s New in This Manual New and Changed Information Open System Services NFS SCF Reference Manual—522582-001 x
About This Manual This manual describes the Subsystem Control Facility (SCF) interactive interface that allows you to configure, control, and monitor the Open System Services (OSS) implementation of the Network File System (NFS). OSS NFS is a network file server compatible with the Sun Microsystems NFS, version 2, protocol. NFS clients on remote hosts can use OSS NFS servers to store and access files on the Compaq NonStop range of servers.
Your Comments Invited About This Manual • Open System Services Programmer’s Guide The following diagram shows the manuals used to install, configure, manage, and operate OSS NFS. The diagram is organized symmetrically, with programmatic interface manuals on the left and the interactive interface manuals on the right. Note that this manual is highlighted.
Notation Conventions About This Manual Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown.
Change Bar Notation About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %Hþnotation precedes a hexadecimal number. For example: %005400 P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition.
1 Introduction This section contains the following information: • • • • • A general description of the Subsystem Control Facility (SCF), which is an operator interface to the Network File System (NFS) subsystem. Descriptions of the OSS NFS object types supported by SCF. Descriptions of the OSS NFS object-specs and naming rules for each object. A general description of the attribute specifiers you use to define objects. Descriptions of the summary states supported by OSS NFS.
Overview Introduction • The Remote Procedure Call (RPC) port mapper process $ZPMx[x], where x[x] indicates a TCP/IP stack number, registers services using the RPC protocol. For example, $ZPFM0 runs over $ZTC0. Figure 1-1.
Object Types Introduction 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.
Object-Name Syntax Introduction EXPORT Identifies a server mount point, and all the files managed by that server that are to be exported. Note that although you can define EXPORT objects for non-existent directories or directories that are not server mount points these EXPORT objects are ignored. Export permissions are only checked by the NFS manager process for the mount point of the server responsible for the directory being remotely mounted. GROUP Identifies a group of NFS users.
Object-Name Syntax Introduction OSS NFS object names are of the form: [\system.][$mgr.]objname where each of the object-name components are defined as follows: \system is the name of the system on which the manager process resides. System names follow the standard Compaq NonStop Kernel operating system naming conventions and cannot contain wild-card characters. $mgr is the name of the NFS manager process (usually $ZNFS).
Object-Name Templates Introduction Object-Name Templates Object-name templates allow you to specify multiple objects by entering either a single wild-card character, or text and one or more wild-card characters. With an object-name template, you can use one object name to specify multiple objects of a given object type. Wild-Card Characters You can use wild-card characters to specify object-name templates for all OSS NFS object names except the PROCESS name.
Attribute Specifiers Introduction The left square bracket and right square bracket are reserved for future use as wild-card characters. You can also use the backslash escape character to specify the octal code for an ASCII character; for example, \033. In addition, if these names include any of the following characters, you must enclose the name in quotes: space comma ( , ) semicolon ( ; ) ampersand (&) Attribute Specifiers Each OSS NFS object has an associated set of attributes.
Summary States Introduction Open System Services NFS SCF Reference Manual—522582-001 1 -8
2 SCF Commands for OSS NFS This section contains the following information: • • • A table describing the Subsystem Control Facility (SCF) commands supported by the OSS NFS subsystem and the object types applicable to each command Instructions for entering SCF commands The following detailed information about each SCF command that you can use to configure and control the OSS NFS subsystem: ° ° ° ° ° ° A description of the command function The command syntax The object-spec, which shows the object type
Entering SCF Commands SCF Commands for OSS NFS Table 2-1.
SCF Commands for OSS NFS Entering SCF Commands SCF indicates it is ready to process commands by displaying its prompt: the hyphen and greater-than sign (->). Additional information can be added in front of this prompt by using the SETPROMPT command, as described in the Subsystem Control Facility (SCF) Reference Manual (for D-series releases) or the SCF Reference Manual for G-Series Releases. SCF waits for a command, followed by a carriage return.
SCF Commands for OSS NFS Command Descriptions Command Descriptions The remainder of this section describes, in alphabetic order by their command-object pairings, the SCF commands supported by OSS NFS. Each command description includes the command’s syntax, the format of the object specifier, and considerations for using the command. For commands that have attribute specifiers, a description of the attribute specifiers is given. Examples are provided for each command.
SCF Commands for OSS NFS LIKE, SUB, and SEL Options LIKE, SUB, and SEL Options The LIKE option is not supported by OSS NFS for any SCF commands. The SUB or SEL option is supported in a command only if shown in that command’s syntax description in this section. The SUB option allows you to restrict the operation of a command to specified subordinate objects (subtypes). You can specify SUB ALL, SUB NONE, SUB ONLY, or SUB subtype, where subtype is a subordinate object type.
SCF Commands for OSS NFS Considerations LAN lan-name specifies the name of the LAN object whose operation is to be terminated. SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you want to abort only LAN objects in the STARTED summary state. Considerations Consider the following points when using the ABORT LAN command: • • • • • • • • • • ABORT LAN is a sensitive command requiring super-group access.
SCF Commands for OSS NFS ABORT SERVER Command ABORT SERVER Command The ABORT SERVER command terminates the operation of the specified server processes as quickly as possible, regardless of whether files are open or requests are pending. Only enough processing to ensure the integrity of the subsystem is done. The SERVER objects are left in the STOPPED summary state.
SCF Commands for OSS NFS Example Example The following command aborts all servers under the assumed manager process that are in the STARTED summary state: ->ABORT SERVER $ZNFS.*, SEL STARTED ABORT SUBSYS Command The ABORT SUBSYS command terminates the operation of the OSS NFS subsystem as quickly as possible, regardless of whether client operations are in progress or remote mounts against the subsystem exist. Only enough processing to ensure the integrity of the subsystem is done.
SCF Commands for OSS NFS Example Use the STOP SUBSYS command if you want to stop the operation of OSS NFS objects in a more controlled manner. The STOP SUBSYS command does not abruptly terminate in-progress activities. • • • • The ABORT SUBSYS command does not clear the RESTART attribute. The RESTART attribute determines whether or not a subsequent START SUBSYS command initiates an attempt to restart the stopped LAN and SERVER objects.
SCF Commands for OSS NFS Considerations The ADD EXPORT command has the following syntax: ADD EXPORT export-name [ [ , attribute-spec ]... ] For an EXPORT object, attribute-spec can be: [ ACCESS { name } { ( name [ , name ]... ) } ] EXPORT export-name specifies the name of the EXPORT object to be added. EXPORT objects are identified by a case-sensitive NFS path name that can include up to 1024 characters, excluding ASCII NUL. ACCESS { name } { ( name [ , name ]...
SCF Commands for OSS NFS ADD GROUP Command ADD GROUP Command The ADD GROUP command adds a GROUP object to the OSS NFS subsystem. GROUP objects are used to classify groups of NFS users to define NETGROUP objects and to translate group IDs to group names. A group has a name and a numeric ID and is composed of one or more users with unique names. The ADD GROUP command has the following syntax: ADD GROUP group-name [ [ , attribute-spec ]...
SCF Commands for OSS NFS Examples Examples The following command adds a group named sales with three members and group ID 25: ->ADD GROUP $ZNFS.sales, MEMBER (susie, phil, alan)& ->, GROUPID 25 The following command adds a group named software with group ID 50: ->ADD GROUP $ZNFS.software, GROUPID 50 The members are added later by using the ALTER GROUP command. ADD LAN Command The ADD LAN command adds a LAN object to the OSS NFS subsystem.
SCF Commands for OSS NFS ADD LAN Command PROCESS process-name specifies the name of the LAN interface process. PROGRAM file-name specifies the NonStop Kernel file name of the LAN interface program. Use the file name that was used to install the NFSLAN file. See the Open System Services NFS Management and Operations Guide for more information about installation. ADDR-CHECK { ON | OFF } specifies whether the host name is checked when a mount or unmount request is received.
SCF Commands for OSS NFS Considerations numbers have higher priority.) If you specify a priority of -1 or omit this attribute, the priority of the NFS manager process at the time the LAN object is started is used as the priority of the LAN interface process. SWAP file-name specifies a file used to hold the LAN interface process’s virtual data. This attribute allows you to specify a permanent file for swapping the data stack and to specify a different volume for the swap file.
SCF Commands for OSS NFS Examples Examples The following command adds a LAN object named LAN0 that runs on primary processor 2 with an execution priority of 170. If the primary processor fails and the LAN interface process is restarted, the LAN interface process will run on processor 3. The LAN interface process name is $LAN0 and the program name is $SYSTEM.ZOSSNFS.NFSLAN.
SCF Commands for OSS NFS Considerations ( [ host-name ] , [ user-name ] , [ domain-name ] ) is a list that adds a specific host machine to the netgroup you are defining. The user-name and domain-name attributes are accepted; however, they are reserved for future use. If you specify any name that does not start with a letter, digit, or underscore (_), all objects of that type are excluded from the netgroup. You can specify multiple netgroupx-names and lists as attributes of the same NETGROUP object.
SCF Commands for OSS NFS ADD SERVER Command For a SERVER object, attribute-spec can be any of: CPU cpu-number MNTPOINT path-name PROGRAM file-name PROCESS process-name STYPE OSS [ BACKUP backup-cpu-number ] [ FILE-OPT-OK { TRUE | FALSE } ] [ MAX-FILE-SIZE integer ] [ NULL-ALIAS-OK { TRUE | FALSE } ] [ PRI cpu-priority ] [ READ-ONLY { TRUE | FALSE } ] [ ROOT-USER-OK { TRUE | FALSE } ] [ SWAP file-name ] [ UPSHIFT { TRUE | FALSE } ] [ WRITE-THRU { TRUE | FALSE } ] SERVER server-name specifies the name of t
SCF Commands for OSS NFS ADD SERVER Command BACKUP backup-cpu-number specifies the number of the backup processor on which the server process runs. You can specify from -1 through 15. The backup processor must be a different processor than the primary processor. A value of -1 indicates that no backup processor is designated. If you do not specify a backup processor, the server process does not run in persistent mode.
SCF Commands for OSS NFS Considerations allowed during access checking because anyone who can become the root user on their workstation can gain access to any remote file. If TRUE, remote root users are allowed access to the server’s files with super-ID privileges. If FALSE, requests from remote root users are treated as requests from the NFS nobody user (user ID 65534). Note that the FALSE value is contingent on the definition of user ID 65534 as the nobody user ID.
Example SCF Commands for OSS NFS Table 2-2. NULL-ALIAS-OK Interactions With the “Nobody” Alias NULL-ALIAS-OK = TRUE NULL-ALIAS-OK = FALSE "nobody" alias defined The "nobody" NFS user ID is mapped to the "nobody" alias user ID NFS returns status condition NFSERR_PERM to the client indicating a permission violation. "nobody" alias not defined The "nobody" NFS user ID is not mapped. NFS returns status condition NFSERR_PERM to the client indicating a permission violation.
SCF Commands for OSS NFS Considerations GROUPID group-id specifies the user’s group number, which can be a value from 0 through 4294967295. An NFS user can, but need not, be a member of a group; that is, although this attribute must be specified, a corresponding predefined group is not required. USERID user-id specifies the user number, which can be a value from 0 through 4294967295.
SCF Commands for OSS NFS Examples Examples The following command adds a user named susie whose user ID is 118 and whose group ID is 25: ->ADD USER $ZNFS.susie, USERID 118, GROUPID 25 & -> , COMMENT “Susie Shaw” The next command adds a user named phil whose user ID is 35, whose group ID is 25, and whose mapped user name is SALES.PHIL: ->ADD USER $ZNFS.phil, USERID 35, GROUPID 25 & -> , COMMENT “Phil Chomsky”, ALIAS OSS SALES.
SCF Commands for OSS NFS ALTER EXPORT Command ALTER EXPORT Command The ALTER EXPORT command changes the remote client access of the specified EXPORT object. The ALTER EXPORT command has the following syntax: ALTER EXPORT export-name [ [ , attribute-spec] ... ] For an EXPORT object, attribute-spec can be any of: [ ADD-ACCESS [ name ] [ ( name [ , name ] ... ) ] ] [ DEL-ACCESS [ name ] [ ( name [ , name ] ...
Example SCF Commands for OSS NFS the EXPORT object itself should be deleted by using the DELETE EXPORT command. Example The following command alters the EXPORT access list for the server mounted at /usr as follows: • • Allows a netgroup named labs and a host machine named warehs to issue remote mounts against directories maintained by that server. Disallows remote mounts of that server by the host machine named dist. ->ALTER EXPORT $ZNFS.
SCF Commands for OSS NFS • • • Example The ALTER GROUP command processes all ADD-MEMBER specifications before all DEL-MEMBER specifications. Duplicate ADD-MEMBER or DEL-MEMBER specifications cause a warning to be returned. Use the INFO GROUP command to determine the current attribute values of a GROUP object. If you specify multiple parameters in any ALTER command and an error occurs, some of the processing might be complete even though the processing was interrupted.
SCF Commands for OSS NFS ALTER LAN Command LAN lan-name specifies the name of the LAN object whose attributes are to be altered. SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you want to alter only LAN objects in the STOPPED summary state. ADDR-CHECK { ON | OFF } specifies whether the host name is checked when a mount or unmount request is received.
SCF Commands for OSS NFS ALTER LAN Command If you omit this attribute, the default values are 128, 256, 512, 1024, 2048, and 4096 bytes. Seven buffers are used. (See STATS LAN Command on page 2-71 for an example.) PRI cpu-priority specifies the execution priority for the LAN interface process. You can specify a priority of -1 or a priority in the range 1 through 199. (Processes with higher numbers have higher priority.
SCF Commands for OSS NFS Considerations Considerations Consider the following points when using the ALTER LAN command: • • • • • • ALTER LAN is a sensitive command requiring super-group access. When you alter a LAN object, it must be in the STOPPED summary state. If you specify any of the SWAP, TCPIP-PROCESS-NAME, TCPIP-RESOLVERNAME, and TCPIP-HOST-FILE attributes without an argument, any existing specification for that attribute is deleted.
SCF Commands for OSS NFS Considerations ADD netgroupx-name adds another netgroup to the specified netgroup. Recursive definitions are not allowed. DEL netgroupx-name deletes a netgroup from the specified netgroup. ADD ( [ host-name ] , [ user-name ] , [ domain-name ] ) adds a specific host to the netgroup. The user-name and domain-name attributes are accepted; however, they are reserved for future use. See “ADD NETGROUP Command,” earlier in this section, for more information about specifying this list.
SCF Commands for OSS NFS ALTER PROCESS Command ALTER PROCESS Command The ALTER PROCESS command changes attribute values associated with the specified PROCESS object. The ALTER PROCESS command has the following syntax: ALTER PROCESS process-name [ [ , attribute-spec ]...
SCF Commands for OSS NFS Considerations DEBUGONERR { ON | OFF } specifies what happens when a fatal error occurs. If ON, the process goes into debug mode. If OFF, the process aborts ( the ABEND routine is called). Caution. Use DEBUGONERR carefully, because turning it on inhibits takeover and prevents normal fault tolerant operation. LOGFILE [file-name] specifies the name of the log file used to used by the manager process.
SCF Commands for OSS NFS ALTER SERVER Command ALTER SERVER Command The ALTER SERVER command changes attribute values associated with the specified SERVER object. The ALTER SERVER command has the following syntax: ALTER SERVER server-name [ [ , attribute-spec ]...
SCF Commands for OSS NFS ALTER SERVER Command NULL-ALIAS-OK { TRUE | FALSE } specifies whether remote NFS users who do not have an alias are allowed access to files managed by the server. If TRUE, these users are mapped to the "nobody" user ID (-2). The "nobody" user ID must be defined in the list of OSS NFS user IDs. If FALSE, a user must have an alias to gain access through pass-through servers. The default value is FALSE. PRI cpu-priority specifies the execution priority for the server process.
SCF Commands for OSS NFS Considerations STYPE OSS specifies that the type of server is an OSS NFS file server. NFS file servers store and provide access to NFS files, which are typically in formats compatible with PCs or workstations: that is, files compatible with DOS or UNIX. SWAP [ file-name ] specifies a file used to hold the server process’s virtual data. This attribute allows you to specify a permanent file for swapping the data stack and to specify a different volume for the swap file.
SCF Commands for OSS NFS Example Example The following command alters the local mount for a server named LIB to be the /usr/lib directory and specifies a backup processor for the server process: ->ALTER SERVER $ZNFS.LIB, MNTPOINT /usr/lib, BACKUP 3 ALTER SUBSYS Command The ALTER SUBSYS command changes attribute values associated with the specified SUBSYS object. The SUBSYS object is used to define the OSS NFS subsystem as a whole. There is only one SUBSYS object per OSS NFS subsystem.
SCF Commands for OSS NFS • Example Use the STATUS SUBSYS command to determine the current subsystem attribute values. • If you specify multiple parameters in any ALTER command and an error occurs, some of the processing might be complete even though the processing was interrupted. For the SUBSYS object, use the STATUS SUBSYS command to determine which of the requested changes were made before the error occurred.
SCF Commands for OSS NFS Considerations ALIAS OSS { user-name } { user-number } specifies a NonStop Kernel user ID, referred to as the mapped user ID, to be used by this NFS user when requesting file access. The NonStop Kernel user ID must already be defined in the USERID file on the system on which the OSS NFS manager process is running. user-name must be a NonStop Kernel user name. If you omit the ALIAS OSS attribute, the user has no mapped user ID.
SCF Commands for OSS NFS Considerations The DELETE EXPORT command has the following syntax: DELETE EXPORT export-name EXPORT export-name specifies the name of the EXPORT object to be deleted. Considerations Consider the following points when using the DELETE EXPORT command: • DELETE EXPORT is a sensitive command requiring super-ID access. Example The following command deletes an EXPORT object named labs: ->DELETE EXPORT $ZNFS.
SCF Commands for OSS NFS DELETE LAN Command DELETE LAN Command The DELETE LAN command removes specified LAN objects from the OSS NFS subsystem. The DELETE LAN command has the following syntax: DELETE LAN lan-name [ , SEL [ NOT ] state ] LAN lan-name specifies the name of the LAN object to be deleted. SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you want to delete only LAN objects in the STOPPED summary state.
SCF Commands for OSS NFS • Example The DELETE NETGROUP command does not delete the NETGROUP or USER objects that are members of the netgroup. Each NETGROUP object must be specifically deleted. You delete USER objects by using the DELETE USER command. Example The following command deletes a netgroup named labtech: ->DELETE NETGROUP $ZNFS.labtech DELETE SERVER Command The DELETE SERVER command removes specified SERVER objects from the OSS NFS subsystem.
SCF Commands for OSS NFS DELETE USER Command DELETE USER Command The DELETE USER command removes specified USER objects from the OSS NFS subsystem. The DELETE USER command has the following syntax: DELETE USER user-name USER user-name specifies the name of the USER object to be deleted. Considerations Consider the following points when using the DELETE USER command: • • • DELETE USER is a sensitive command requiring super-ID access.
Considerations SCF Commands for OSS NFS DETAIL specifies that detailed EXPORT attribute information is requested. Considerations Consider the following points when using the INFO EXPORT command. • • INFO EXPORT is a nonsensitive command. The wildcard character for INFO EXPORT is **, not *. Examples Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command.
SCF Commands for OSS NFS Access INFO GROUP Command is a list of hosts or netgroups that may access files in or below the exported directory. If no names appear, the directory and all files below it in the hierarchy can be accessed by all hosts. INFO GROUP Command The INFO GROUP command displays the current attribute values for the specified GROUP objects. You can display attribute information about GROUP objects with or without detail.
Examples SCF Commands for OSS NFS Examples Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command. The following command displays information (without detail) about all currently defined GROUP objects: ->INFO GROUP $ZNFS.* The resulting display has the following format: NFS Info GROUP \SYS1.$ZNFS.
SCF Commands for OSS NFS Considerations The information contained in the displays produced by INFO LAN is described in detail under Examples on page 2-45. Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command. The INFO LAN command has the following syntax: INFO LAN lan-name [ , DETAIL ] [ , SEL [ NOT ] state ] LAN lan-name specifies the name of the LAN object for which attribute information is requested.
Examples SCF Commands for OSS NFS The display contains the following information: Objname is the LAN object name. Process is the name of the LAN interface process. Primary is the number of the primary processor. Backup is the number of the backup processor. A value of -1 indicates no backup processor is defined and the LAN interface process will not be restarted in case of failure. Priority is the execution priority for the LAN interface process.
INFO NETGROUP Command SCF Commands for OSS NFS HOSTS file, nor a resolver file is specified, NonStop TCP/IP uses the file $SYSTEM.ZTCPIP.RESCONF. Primary is the number of the primary processor. Backup is the number of the backup processor. A value of -1 indicates no backup processor is defined and the LAN interface process will not be restarted in case of failure. Priority is the execution priority for the LAN interface process.
Example SCF Commands for OSS NFS • The DETAIL option is not allowed with the INFO NETGROUP command. Example Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command. The following command displays information (without detail) about a netgroup named medaccts: ->INFO NETGROUP $ZNFS.medaccts The resulting display has the following format: NFS Info NETGROUP \SYS1.$ZNFS.medaccts *Member.......... (sunsys, marilyn, techco) *Member....
Considerations SCF Commands for OSS NFS PROCESS process-name specifies the name of the PROCESS object for which attribute information is requested. DETAIL specifies that detailed attribute information is requested. SUB [ ALL | NONE | ONLY | subtype ] specifies the subordinate object select option.
Considerations SCF Commands for OSS NFS The display contains the following information: Objname is the PROCESS object name. Primary is the number of the primary CPU. Backup is the number of the backup processor. A value of -1 indicates no backup processor is defined and the NFS manager process is not being run as a process pair. Backup Debug indicates whether the backup process should (ON) or should not (OFF) be initiated in debug mode.
INFO SERVER Command SCF Commands for OSS NFS Ext Mem Swap Vol is the swap volume used for the process extended memory segment (as specified in the SWAPVOL parameter of the PARAM or RUN command). Primary is the number of the primary processor. Backup is the number of the backup processor. A value of -1 indicates no backup processor is defined and the NFS manager process is not being run as a process pair.
Considerations SCF Commands for OSS NFS Considerations Consider the following points when using the INFO SERVER command. • • • INFO SERVER is a nonsensitive command. Use the STATUS SERVER command to obtain information about the current state of a SERVER object. Use the STATISTICS SERVER command to obtain statistical information about a SERVER object. Examples Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command.
Considerations SCF Commands for OSS NFS The resulting detailed display has the following format: NFS Detailed Info SERVER \SYS1.$ZNFS.ROOT *Mount Point.... *Program........ *Process........ Primary........ *Read Only...... *Root User OK... *Write Thru..... / $SYSTEM.ZOSSNFS.NFSSVRHP $SV001 *Server Type...... 1 *Backup........... FALSE *Priority......... TRUE *Max File Size.... TRUE *Null Alias OK....
INFO USER Command SCF Commands for OSS NFS INFO USER Command The INFO USER command displays the current attribute values for the specified USER objects. You can display attribute information about USER objects with or without detail. The information contained in the displays produced by INFO USER is described in detail under Examples on page 2-55. Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command.
Considerations SCF Commands for OSS NFS Examples Note. An asterisk (*) in any INFO command display indicates that you can change the value of the attribute using the ALTER command. The following command displays information (without detail) about all currently defined USER objects: ->INFO USER $ZNFS.* The resulting display has the following format: NFS Info USER \SYS1.$ZNFS.* Objname carolyn user *UID 1263 8 *GID 247 247 *Alias Name SOFTWARE.CAROLYN SOFTWARE.
LISTOPENS PROCESS Command SCF Commands for OSS NFS LISTOPENS PROCESS Command The LISTOPENS PROCESS command returns a list of file system opens associated with the NFS manager process. The information contained in the displays produced by LISTOPENS PROCESS is described in detail under Example on page 2-56. The LISTOPENS PROCESS command has the following syntax: LISTOPENS PROCESS process-name PROCESS process-name specifies the name of the PROCESS object for which open information is requested.
SCF Commands for OSS NFS LISTOPENS SUBSYS Command LISTOPENS SUBSYS Command The LISTOPENS SUBSYS command returns a list of remote mounts associated with the OSS NFS subsystem. You can list the remote mounts with or without detail. The information contained in the displays produced by LISTOPENS SUBSYS is described in detail under Examples on page 2-57.
NAMES EXPORT Command SCF Commands for OSS NFS The resulting display has the following format: NFS Listopens SUBSYS \SYS1.$ZNFS Host pcsys pcsys sunsys Mount Point / /usr /docs The display contains the following information: Host is the machine name of a host system that currently has one or more remote mounts against a part of the OSS NFS file hierarchy. Mount Point is the pathname of a directory that has been remotely mounted by the host.
Considerations SCF Commands for OSS NFS EXPORT export-name specifies the name of the EXPORT objects to be returned. Considerations Consider the following points when using the NAMES EXPORT command: • • • NAMES EXPORT is a nonsensitive command. Because some EXPORT object names can be up to 1024 characters long, names longer than the record length of the SCF output device are wrapped into multiple lines. The wildcard character for NAMES EXPORT is **, not *.
Example SCF Commands for OSS NFS Example The following command displays the names of all GROUP objects associated with the manager process $ZNFS: ->NAMES GROUP $ZNFS.* The resulting display has the following format: NFS Names GROUP \SYS1.$ZNFS.* GROUP bin nobody software turtle NAMES LAN Command The NAMES LAN command displays the names of all LAN objects that meet the lan-name and SEL specifications. This command is most useful if you use an object-name template.
NAMES NETGROUP Command SCF Commands for OSS NFS The resulting display has the following format: NFS Names LAN \SYS1.$ZNFS.* LAN NFSLAN NAMES NETGROUP Command The NAMES NETGROUP command displays the names of all NETGROUP objects that meet the netgroup-name specification. This command is most useful if you use wild-card characters in the object name you specify. For example, you can use an asterisk (*) in place of the name to specify all objects of the type you request.
SCF Commands for OSS NFS NAMES PROCESS Command NAMES PROCESS Command The NAMES PROCESS command displays the names of all objects that meet the process-name, SUB, and SEL specifications. This command is most useful when combined with the SUB and SEL options. The NAMES PROCESS command has the following syntax: NAMES PROCESS process-name [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] PROCESS process-name specifies the name of the PROCESS object to which the command applies.
NAMES SERVER Command SCF Commands for OSS NFS The resulting display has the following format: NFS Names PROCESS \SYS1.$ZNFS PROCESS $ZNFS LAN NFSLAN SERVER ROOT SERVER2 SERVER3 NAMES SERVER Command The NAMES SERVER command displays the names of all SERVER objects that meet the server-name and SEL specifications. This command is most useful if you use an object-name template. See Object-Name Templates on page 1-6.
NAMES SUBSYS Command SCF Commands for OSS NFS The resulting display has the following format: NFS Names SERVER \SYS1.$ZNFS.* SERVER ROOT USR GRD NAMES SUBSYS Command The NAMES SUBSYS command displays the names of the SUBSYS objects that meet the process-name, SUB, and SEL specifications. This command is most useful when combined with the SUB and SEL options.
NAMES USER Command SCF Commands for OSS NFS The resulting display has the following format: NFS Names SUBSYS \SYS1.$ZNFS SUBSYS $ZNFS PROCESS $ZNFS LAN NFSLAN SERVER ROOT SERVER2 SERVER3 NAMES USER Command The NAMES USER command displays the names of all USER objects that meet the user-name specification. This command is most useful if you use an object-name template. See “Object-Name Templates on page 1-6.
SCF Commands for OSS NFS PRIMARY PROCESS Command PRIMARY PROCESS Command The PRIMARY PROCESS command causes the manager process to switch to its backup processor. The primary processor then becomes the backup processor. The PRIMARY PROCESS command has the following syntax: PRIMARY PROCESS process-name , backup-processor-number PROCESS process-name specifies the name of the PROCESS object that is to switch processors. backup-processor-number specifies the number of the backup processor.
SCF Commands for OSS NFS Considerations The START LAN command has the following syntax: START LAN lan-name [ , SEL [ NOT ] state ] LAN lan-name specifies the name of the LAN object to be started. SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you want to start only LAN objects in the STOPPED summary state.
SCF Commands for OSS NFS Example Example The following command starts a LAN object named LAN0: ->START LAN $ZNFS.LAN0 START SERVER Command The START SERVER command starts one or more server processes. 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.
SCF Commands for OSS NFS • • Example It is recommended that server processes be run in persistent mode. If the primary processor in which a server process is to run fails, the START SERVER command automatically attempts to start the server process in the backup processor. To terminate the operation of a SERVER object, use the STOP SERVER or ABORT SERVER command. Example The following command starts a server named NSERV11: ->START SERVER $ZNFS.
SCF Commands for OSS NFS 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.
SCF Commands for OSS NFS STATS LAN Command You should not include the SUB ALL option without the SEL STOPPED option, or the following operations occur: • • • • LAN0 and SRV1 are started as part of starting the subsystem. Applying the START command to all subordinate LAN objects generates a warning that LAN0 is already started. Applying the START command to all subordinate SERVER objects generates a warning that SRV1 is already started.
Example SCF Commands for OSS NFS Example The following command displays statistics for the LAN object named LAN: ->STATS LAN $ZNFS.LAN The resulting display has the following format: NFS Stats LAN \SYS1.$ZNFS.LAN Reset Time.... 28 Aug 1995, 11:33:58.632 Sample Time... 28 Aug 1995, 12:09:24.328 Bad Calls .......... 0 I/O Errors .......... 0 Messages Dropped..... 0 Message Sizes <=128 <=256 Recv 14 0 Send 0 24 Procedure 100003 100003 100003 100003 100005 100005 (2). 4 (2). 6 (2). 16 (2). 17 (1). 1 (1).
STATS PROCESS Command SCF Commands for OSS NFS Name is the name of the procedure. Count is the number of times the procedure has been called by the LAN interface process. Procedures with zero counts are not displayed. Elapsed Secs is the total elapsed (wall-clock) time required for the LAN interface process to reply to an RPC call. Avg. Resp is the average response time in seconds, which is calculated by dividing the elapsed time by the count.
Considerations SCF Commands for OSS NFS Considerations Consider the following points when using the STATS PROCESS command: • • STATS PROCESS is a nonsensitive command without the RESET option, but a sensitive command with the RESET option requiring super-group access. The information contained in the displays produced for subordinate objects is described under the individual command descriptions for each object.
Example SCF Commands for OSS NFS Sample Time is the time at which the PROCESS statistics sample was taken. Configured Size is the total number of bytes configured for the extended memory pool. Current Size is the number of bytes currently allocated from the extended memory pool. If the number of bytes allocated are consistently near or over one-half the total pool size, the pool might be overused.
STATS SERVER Command SCF Commands for OSS NFS Sample Time is the time at which the PROCESS statistics sample was taken. Configured Limit is the maximum number of openers allowed. Current Usage is the current number of openers. Maximum Used is the maximum number of openers since the statistics were reset, the process was initiated, or a backup takeover occurred. STATS SERVER Command The STATS SERVER command returns statistics for a SERVER object.
Example SCF Commands for OSS NFS Example The following command displays statistics for the server named $ZNFS.ROOT: ->STATS SERVER $ZNFS.ROOT The resulting display has the following format: NFS Stats SERVER \KT22.$ZNFS.ROOT Reset Time.... 21 Sep 1995, 18:57:16.601 Sample Time... 21 Sep 1995, 18:57:30.272 Bad Calls............ 0 I/O Errors........... 0 Messages Dropped.....
STATUS LAN Command SCF Commands for OSS NFS Read Hits indicates the number of times the server did not have to reperform an operation because it could return the previous response from a duplicate request. Write Hits is not applicable for the transaction cache. STATUS LAN Command The STATUS LAN command reports the status of a LAN object. You can display status information about LAN objects with or without detail.
Examples SCF Commands for OSS NFS The resulting display has the following format: NFS Status LAN \SYS1.$ZNFS.NFSLAN Objname NFSLAN State STARTED Restart YES System 251 PPID 1,33 Trace OFF LastErr 0 The display contains the following information: Objname is the name of the LAN object. State is the summary state of the LAN object. Restart indicates whether a subsequent START SUBSYS command will attempt to restart the LAN interface process (YES) or will not attempt to restart it (NO).
SCF Commands for OSS NFS STATUS PROCESS Command Primary PID indicates the processor number and process identification number (PIN) of the LAN interface process. Restart indicates whether a subsequent START SUBSYS command will attempt to restart the LAN interface process (YES) or will not attempt to restart it (NO).
Considerations SCF Commands for OSS NFS SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you are requesting status information about only objects in a specified summary state. See Summary States on page 1-7 for the names and descriptions of these states. Considerations Consider the following points when using the STATUS PROCESS command: • • • STATUS PROCESS is a nonsensitive command.
STATUS SERVER Command SCF Commands for OSS NFS The resulting detailed display has the following format: NFS Detailed Status PROCESS \SYS1.$ZNFS System Name....... State............. Backup State...... Trace............. Last Error........ \SYS1 STARTED STOPPED OFF 0 System Number..... Primary PID....... Backup PID........ Takeovers......... 212 1,59 NONE 0 The detailed display contains the following information: System Name is the name of the system on which the process is running.
Considerations SCF Commands for OSS NFS SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you are requesting status information about only SERVER objects in a specified summary state. See Summary States on page 1-7 for the names and descriptions of these states. Considerations Consider the following points when using the STATUS SERVER command: • • • STATUS SERVER is a nonsensitive command.
Examples SCF Commands for OSS NFS LastErr is the number of the last error encountered by the server process. The following command displays the detailed status information for a SERVER object named $ZNFS.ROOT: ->STATUS SERVER $ZNFS.ROOT, DETAIL The resulting detailed display has the following format: NFS Detailed Status SERVER \SYS1.$ZNFS.ROOT State.............STARTED Restart........... YES System Name.......\SYS1 System Number..... 206 Primary PID.......6,62 Backup PID........ NONE Last Error........
SCF Commands for OSS NFS STATUS SUBSYS Command STATUS SUBSYS Command The STATUS SUBSYS command returns status information for all objects that meet the specified process-name, SUB, and SEL specifications. You can display status information about the specified objects with or without detail. The information contained in the displays produced by STATUS SUBSYS is described in detail under Examples on page 2-86.
Examples SCF Commands for OSS NFS • The information contained in the displays produced for subordinate objects are described under the individual command descriptions for each object. Examples The following command reports the status of the SUBSYS object associated with the manager process $ZNFS: ->STATUS SUBSYS $ZNFS The resulting display has the following format: NFS Status SUBSYS \SYS1.
STOP LAN Command SCF Commands for OSS NFS Reuse Server ID indicates whether the subsystem can reuse a server ID when restarting a stopped server. This attribute can be reset by using the ALTER SUBSYS command. Last Error is the number of the last error encountered. Last Error Detail indicates the actual last error that occurred. This field is only present when Last Error has a nonzero value. STOP LAN Command The STOP LAN command terminates the operation of a LAN object in a controlled manner.
SCF Commands for OSS NFS • • Example The STOP LAN command clears the RESTART attribute. The RESTART attribute determines whether or not a subsequent START SUBSYS command initiates an attempt to restart the stopped LAN object. The STOP LAN command should only be used in situations where you will not want to restart the same configuration of LAN interface and server processes that are currently running. To stop a LAN object without clearing the RESTART attribute, use the STOP SUBSYS command.
SCF Commands for OSS NFS STOP SERVER Command STOP SERVER Command The STOP SERVER command terminates the operation of a SERVER object in a controlled manner. The STOP SERVER command does not abruptly terminate inprogress activities. When the operation is complete, the SERVER object is in the STOPPED summary state.
SCF Commands for OSS NFS Example running. To stop a SERVER object without clearing the RESTART attribute, use the STOP SUBSYS command. • For SERVER objects, active NFS requests are requests in progress. ° A normal stop succeeds only if there are no active requests. ° An orderly stop causes the server to enter the STOPPING summary state, reject new requests, and wait for all active requests to complete before stopping the server process.
SCF Commands for OSS NFS Considerations SUBSYS process-name specifies the name of the SUBSYS object whose operation is to be terminated. The SUBSYS object uses the name of the manager process with which it is associated. ORDERLY specifies that the STOP operation rejects new requests, and waits for all active links to be dropped before terminating the object. If you omit ORDERLY, the STOP operation succeeds only if no active links exist when you issue the command.
SCF Commands for OSS NFS • • • • Example The STOP SUBSYS command does not clear the RESTART attribute. The RESTART attribute determines whether or not a subsequent START SUBSYS command initiates an attempt to restart the stopped LAN and SERVER objects. STOP SUBSYS is useful in situations where you will want to restart the same configuration of LAN interface and server processes that was running when the command was issued.
SCF Commands for OSS NFS Considerations Considerations Consider the following points when using the STOPOPENS command: • • • • • STOPOPENS is a sensitive command requiring super-group access. Use this command to prevent the OSS NFS subsystem from being accessed by new clients when you are preparing to stop it. While the STOPOPENS command is in effect, remote mount requests receive no response. Clients attempting to perform remote mounts eventually time out and abort or retry their requests.
TRACE LAN Command SCF Commands for OSS NFS For a LAN object, select-word can be any of: [ ALL ] [ HOST “host-name” ] [ MNT { DUMP } | RPC { 100005.2 } { EXPORT } | { 100005.5 } { MNT } | { 100005.1 } { NULL } | { 100005.0 } { UMNT } | { 100005.3 } { UMNTALL } | { 100005.4 } ] [ NFS { CREATE } | RPC { 100003.9 { GETATTR } | { 100003.1 { LINK } | { 100003.12 { LOOKUP } | { 100003.4 { MKDIR } | { 100003.14 { NULL } | { 100003.0 { READ } | { 100003.6 { READDIR } | { 100003.16 { READLINK } | { 100003.
SCF Commands for OSS NFS TRACE LAN Command NOCOLL indicates that the trace collector process should not be initiated. PAGES pages designates how much space, in pages, is allocated in the extended data segment used for tracing. PAGES can be specified only when a trace is being initiated, not when its parameters are being modified. pages is an integer in the range 4 through 64, or it is equal to 0. If you omit this option or specify 0, the default value of 64 is applied to the trace.
SCF Commands for OSS NFS Considerations NFS specifies a remote procedure call in the NFS protocol that is to be traced. The specified NFS procedures are traced only if they meet the other trace LAN criteria also. RPC specifies a remote procedure call by its program number, version number, and procedure number. If you omit the version number, all versions are traced. The specified NFS procedures are only traced if they meet the other trace LAN criteria also.
Examples SCF Commands for OSS NFS • • Duplicate or overlapping bit mask selection criteria are permitted, but the effect varies based on the specific values. If you specify more than one HOST, SERVER, RPC, MNT, or NFS value, or more than one value in the message category (the RPCMSG, SPIMSG, SYSMSG, UNKNOWN, or ALL values), the values are ORed.
SCF Commands for OSS NFS Considerations Considerations Consider the following points when using the VERSION LAN command: • • VERSION LAN is a nonsensitive command. When you issue a VERSION LAN command, the LAN object must not be in the STOPPED summary state. Example The following command displays version information about the LAN object named NFSLAN: ->VERSION LAN $ZNFS.NFSLAN The resulting display has the following format: VERSION LAN \SYS1.$ZNFS.
SCF Commands for OSS NFS • Considerations The product module version within SCF. SUB [ ALL | NONE | ONLY | subtype ] specifies the subordinate object select option. You can specify SUB ALL to request information about all objects subordinate to the object, or you can specify one of the object types to request information about that object. SEL [ NOT ] state specifies the summary state select option.
SCF Commands for OSS NFS VERSION PROCESS Command The resulting detailed display has the following format: Detailed VERSION \SYS5.$ZNFS SYSTEM \SYS5 NFS (NFSD40 01FEB96 01FEB96 ) GUARDIAN - T9050 - (N40) SYSTEM \SYS1 NFS (NFSD40 01FEB96 01FEB96 ) GUARDIAN - T9050 - (N40) SCF KERNEL - T9082C30 - (30NOV95) (06NOV95) NFS PM - NFS - T9628D40 - O1FEB96 O1FEB96 VERSION PROCESS Command The VERSION PROCESS command displays the OSS NFS product name, product number, and release date of the PROCESS object.
SCF Commands for OSS NFS Considerations Considerations Consider the following points when using the VERSION PROCESS command: • VERSION PROCESS is a nonsensitive command. Examples The following command displays the banner of the process $ZNFS: ->VERSION PROCESS $ZNFS The resulting display has the following format: VERSION PROCESS \SYS1.
SCF Commands for OSS NFS Considerations SEL [ NOT ] state specifies the summary state select option. You can use the SEL option to specify that you are requesting version information about objects only in a specified summary state. See Summary States on page 1-7 for the names and descriptions of these states. Considerations Consider the following points when using the VERSION SERVER command: • • VERSION SERVER is a nonsensitive command.
A SCF Command Summary for OSS NFS This appendix lists, in alphabetic order, the syntax for each of the SCF commands supported for the OSS NFS subsystem. It is included here as a quick reference for those already familiar with the SCF commands for OSS NFS. ABORT LAN lan-name [ , SEL [ NOT ] state ] ABORT SERVER server-name [ , SEL [ NOT ] state ] ABORT SUBSYS process-name [ , SUB [ ALL | NONE | ONLY | subtype [ , SEL [ NOT ] state ] ] ] ADD EXPORT export-name [ [ , attribute-spec ] ...
SCF Command Summary for OSS NFS ADD NETGROUP netgroup-name [ [ , attribute-spec ]... ] attribute-spec for ADD NETGROUP is: [ netgroupx-name ] [ ( [ host-name ] , [ user-name ] , [ domain-name ] ) ] ADD SERVER server-name [ [ , attribute-spec ]...
SCF Command Summary for OSS NFS ALTER GROUP group-name [ [ , attribute-spec ]... ] attribute-spec for ALTER GROUP is: [ ADD-MEMBER { { [ DEL-MEMBER { { user-name } user-name [ , user-name ]... ) } ] user-name } user-name [ , user-name ]... ) } ] ALTER LAN lan-name [ [ , attribute-spec ]... ] [ , SEL [ NOT ] state ] attribute-spec for ALTER LAN is: [ ADDR-CHECK { ON | OFF } ] [ ADD-DOMAIN { domain-name } { ( domain-name [ , domain-name ]...
SCF Command Summary for OSS NFS ALTER PROCESS process-name [ [ , attribute-spec ]... ] [ , SEL [ NOT ] state ] attribute-spec for ALTER PROCESS is: [ [ [ [ [ [ BACKUP [ backup-cpu-number ] ] BACKUPDEBUG { ON | OFF } ] COLLECTOR [ process-name ] ] DEBUGONERR { ON | OFF } ] LOGFILE [ file-name ] ] MSGFILE file-name ] ALTER SERVER server-name [ [ , attribute-spec ] ...
SCF Command Summary for OSS NFS DELETE GROUP group-name DELETE LAN lan-name [ , SEL [ NOT ] state ] DELETE NETGROUP netgroup-name DELETE SERVER server-name [ , SEL [ NOT ] state ] DELETE USER user-name INFO EXPORT export-name [ , DETAIL ] IINFO GROUP group-name [ , GROUPID group-id ] [ , DETAIL ] INFO LAN lan-name [ , DETAIL ] [ , SEL [ NOT ] state ] INFO NETGROUP netgroup-name INFO PROCESS process-name [ , DETAIL ] [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] INFO SERVER server-name
SCF Command Summary for OSS NFS NAMES NETGROUP netgroup-name NAMES PROCESS process-name [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] NAMES SERVER server-name [ , SEL [ NOT ] state ] NAMES SUBSYS process-name [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] NAMES USER user-name PRIMARY PROCESS process-name , backup-cpu-number START LAN lan-name [ , SEL [ NOT ] state ] START SERVER server-name [ , SEL [ NOT ] state ] START SUBSYS process-name [ , SUB [ ALL | NONE | ONLY
SCF Command Summary for OSS NFS STATUS PROCESS process-name [ , DETAIL ] [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] STATUS SERVER server-name [ , DETAIL ] [ , SEL [ NOT ] state ] STATUS SUBSYS process-name [ , DETAIL ] [ , SUB [ ALL | NONE | ONLY | subtype ] ] [ , SEL [ NOT ] state ] STOP LAN lan-name [ , ORDERLY | , FORCED ] [ , SEL [ NOT ] state ] STOP SERVER server-name [ , ORDERLY | , FORCED ] [ , SEL [ NOT ] state ] STOP SUBSYS process-name [ , ORDERLY | , FORCED ] [ , SUB [ ALL
SCF Command Summary for OSS NFS select-word for LAN is: [ ALL ] [ HOST “host-name” ] [ MNT { DUMP } | RPC { 100005.2 } { EXPORT } | { 100005.5 } { MNT } | { 100005.1 } { NULL } | { 100005.0 } { UMNT } | { 100005.3 } { UMNTALL } | { 100005.4 } ] [ NFS { CREATE } | RPC { 100003.9 { GETATTR } | { 100003.1 { LINK } | { 100003.12 { LOOKUP } | { 100003.4 { MKDIR } | { 100003.14 { NULL } | { 100003.0 { READ } | { 100003.6 { READDIR } | { 100003.16 { READLINK } | { 100003.5 { REMOVE } | { 100003.
B Summary of All SCF Commands Table B-1 lists the SCF commands and, for each command, indicates whether it is supported by OSS NFS, a general command you can use to manipulate and inquire about SCF, or a general SCF command that is not applicable or useful with OSS NFS. Table B-1.
Summary of All SCF Commands Table B-1.
Glossary address mask. A bit mask used to select bits from an Internet address for subnetwork addressing. The mask is 32 bits long. It selects the network portion of the Internet address and one or more bits from the local portion. address resolution. Conversion of an Internet address into a corresponding physical address. Depending on the underlying network, the resolution might require broadcasting on a local network. Address Resolution Protocol (ARP).
bridge Glossary bridge. A router that connects two or more networks and forwards packets among them. Usually, bridges operate at the physical network level. Bridges differ from repeaters: bridges store and forward complete packets, while repeaters forward electrical signals. broadband. A characteristic of any network technology that multiplexes multiple, independent network carriers onto a single cable (usually using frequency-division multiplexing).
Compaq NonStop Kernel Open System Services (OSS). Glossary range 192 through 255, the second octet is in the range 0 through 255, and the third octet is in the range 0 through 255. The remaining octet in the address is used for the subnetwork number and host number. The subnetwork number varies in length. The subnetwork number’s width is typically represented by a bit mask. The rest of the available bits uniquely identify the host connected to the subnetwork.
dotted-decimal notation Glossary dotted-decimal notation. A representation for a 32-bit binary integer that consists of four decimal (base 10) numbers separated by periods (dots), each of which represents one of the four 8-bit values in the integer. Many Internet application programs accept dotteddecimal notation in place of destination machine names. ECHO.
file system Glossary file system. In the OSS environment, a collection of files and file attributes. A file system provides the namespace for the file serial numbers that uniquely identify its files. Open System Services provides a file system (see also ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.1-1990], Clause 2.2.2.38); the Guardian environment provides a file system; and OSS NFS provides a file system.
hierarchical routing Glossary hierarchical routing. Routing based on a hierarchical addressing scheme. Most Internet routing is based on a two-level hierarchy in which an Internet address is divided into a network portion and a host portion. Gateways use only the network portion until the datagram reaches a gateway that can deliver it directly. Subnetworking introduces additional levels of hierarchical routing. hop count. A measure of distance between two points in the Internet.
IP Glossary information. NonStop Himalaya manuals often use the term “connectivity” in this context, while other vendors use the term “connectivity” to mean hardware compatibility. IP. See Internet Protocol (IP). IP datagram. The basic unit of information passed across the Internet. An IP datagram is to the Internet as a hardware packet is to a physical network. It contains source and destination addresses, along with data. ISO. International Organization for Standardization.
logical name Glossary logical name. In NFS, a case-insensitive alphanumeric name that starts with a letter and contains eight or fewer characters. Logical names are used to name LAN and SERVER objects. MAC address. See media access control (MAC) address. media access control (MAC) address. A 12-digit hexadecimal number used as an address for network access.
OSS Glossary OSS. See Open System Services (OSS) Parallel Library TCP/IP. A Compaq networking product that provides increased performance, scalability, and fault-tolerance by creating parallel TCP/IP protocol stacks implemented as an Shared Runtime Library (SRL) on the NonStop Kernel operating system. pathname. A name that identifies a file by specifying which directories must be searched in order to find the link to the file.
SMTP Glossary SMTP. See Simple Mail Transfer Protocol (SMTP). SNAP. See Subnetwork Access Protocol (SNAP). socket. An end-point for stream-oriented communication. A socket has a file descriptor. source quench. A congestion-control technique in which a system experiencing congestion sends a request back to the source of the packets causing the congestion asking that the source stop transmitting.
Transmission Control Protocol over Internet Protocol (TCP/IP) Glossary on. TCP allows a process on one system to send a stream of data to a process on another. It is connection-oriented; that is, before transmitting data, participants must establish a connection. Software implementing TCP usually resides on the operating system and uses the Internet Protocol (IP) to transmit information across the Internet.
XDR Glossary Open System Services NFS SCF Reference Manual—522582-001 Glossary -12
Index A ABORT LAN command 2-5 ABORT SERVER command 2-7 ABORT SUBSYS command 2-8 Access remote root users 2-18, 2-33 without mapped user ID 2-18, 2-37, 2-53 Active links 2-87, 2-88, 2-89, 2-91 ADD EXPORT command 2-9 ADD GROUP command 2-11 ADD LAN command 2-12 ADD NETGROUP command 2-15 ADD SERVER command 2-16 ADD USER command 2-20 Address mask glossary-1 Address resolution glossary-1 Address Resolution Protocol (ARP) glossary-1 ADDR-CHECK attribute 2-13, 2-26 ADD-ACCESS attribute 2-23 ADD-DOMAIN attribute 2-2
D Index Commands (continued) sensitive 2-4 summary of SCF commands B-1 COMMENT attribute 2-21, 2-37 Connection glossary-3 Connectionless service glossary-3 Continuation of commands 2-3 Core gateway glossary-3 CPU attribute LANs 2-12, 2-26 servers 2-17, 2-32 CPUs, switching 2-66 D Data stack, swapping 2-14, 2-19, 2-27, 2-34, 2-50 Data swap volume 2-50 Debug mode, backup process 2-30, 2-50, 2-51 DEBUGONERR attribute 2-31 DEL attribute 2-29 DELETE EXPORT command 2-37 DELETE GROUP command 2-38 DELETE LAN com
H Index General SCF commands B-1 GROUP objects adding 2-11 deleting 2-38 displaying attribute values 2-43 displaying names of 2-43, 2-59 setting attributes 2-11 GROUPID attribute groups 2-11 users 2-21 Guardian glossary-5 H Hardware address glossary-5 Help command 2-1 Hierarchical routing glossary-6 Hierarchy of objects 1-3 HISTOGRAM attribute 2-13, 2-26 Histogram, display 2-47 Hosts allowing remote mounts 2-9 mount request name checking 2-13, 2-26 HOSTS file 2-14, 2-27 Host-name attribute for netgroups
M Index M Manager process 2-10 restarting 2-9, 2-92 stopping 2-8, 2-90 Mapped user IDs access without 2-18, 2-33 defining 2-37 Maximum characters in a command 2-3 MAX-FILE-SIZE attribute 2-18, 2-32 Media access control (MAC) address glossary-8 MEMBER attribute, groups 2-11 Message files 2-31 Message lengths, counting 2-13, 2-26 MNTPOINT attribute 2-17, 2-32 Mount point glossary-8 Mount requests, host name checking 2-13 Mounts affect on stopping objects 2-88, 2-89, 2-90 listing remote 2-57 local 1-3, 2-17,
P Index P Parallel Library TCP/IP glossary-9 Pathname glossary-9 PING glossary-9 PRI attribute LANs 2-13, 2-27 servers 2-18, 2-33 PRIMARY PROCESS command 2-66 Primary processor LANs 2-13, 2-27 servers 2-17, 2-32 switching 2-66 Priority LAN process 2-13, 2-27 server process 2-18, 2-33 PROCESS attribute LANs 2-13, 2-27 servers 2-17, 2-33 PROCESS object changing attributes 2-30 displaying attribute values 2-48 displaying names of 2-62 displaying statistics about 2-73 status of 2-80 stopping 2-90 Processors,
T Index Stack, data 2-14, 2-19, 2-27, 2-34 START LAN command 2-66 START SERVER command 2-68 START SUBSYS command 2-69 STARTED state 1-7 Starting SCF 2-2 Statistics, resetting 2-71, 2-73, 2-76 STATS LAN command 2-71 STATS PROCESS command 2-73 STATS SERVER command 2-76 STATUS LAN command 2-78 STATUS PROCESS command 2-80 STATUS SERVER command 2-82 STATUS SUBSYS command 2-85 STOP LAN command 2-87 STOP SERVER command 2-89 STOP SUBSYS command 2-90 STOPOPENS SUBSYS command 2-92 STOPPED state 1-7 stopping 2-8 Sto
V Index USER objects (continued) displaying names of 2-65 setting attributes 2-20 V Version information LANs 2-97 manager process 2-100 subsystem 2-98, 2-100 VERSION LAN command 2-97 VERSION NULL command 2-98 VERSION PROCESS command 2-100 VERSION SERVER command 2-101 Virtual data 2-14, 2-19, 2-27, 2-34 W Wild-card characters 1-6 WRITE-THRU attribute 2-19, 2-34 Z ZNFSUSR files 2-19 Special Characters (PC)NFS Daemon (PCNFSD) glossary-9 Open System Services NFS SCF Reference Manual— 522582-001 Index -7
Special Characters Index Open System Services NFS SCF Reference Manual— 522582-001 Index -8
