Open System Services NFS Management and Operations Guide

DATAPAGES number-of-pages [ E[XTENSIBLE] ]
specifies the amount of virtual memory disk storage, in 2048-byte pages, to be allocated
for use as general dynamic memory. If an odd number is specified, DP2 rounds it up to
the nearest even number.
number-of-pages is an integer in the range 0 through 65280. If you specify the keyword
EXTENSIBLE or E, the memory segment will be extensible. If this parameter is omitted, 2040
pages of extensible segment memory are assigned.
The value 0 (zero), for number-of-pages, causes the OSS NFS manager process to
allocate pages dynamically on an as-needed basis, which is frequently an economical way
to run the process. During operation in this mode, an initial allocation guarantees enough
storage to start the process, and storage is extended as needed until one or more of these
conditions exist:
• Approximately 4 megabytes have been allocated.
• The virtual memory limit is reached.
• The underlying disk file space is unavailable.
However, dynamic allocation has the risk that memory cannot be extended after the
subsystem has been running for some time. If you can reasonably predict the amount of
memory needed, you should specify that value in the DATAPAGES parameter.
MAXSERVERS number-of-servers
specifies the maximum number of SERVER objects that can be in the STARTED state. SERVER
objects are started by the START SERVER and START SUBSYS commands. If this parameter
is omitted, a value of 16 is assigned.
PURGEDB [ TRUE | FALSE ]
specifies whether existing configuration data should be purged (TRUE) or retained (FALSE).
If this parameter is omitted, the default value is FALSE. If set to TRUE, all data in existing
OSS NFS configuration files except for the user alias files (ZNFSUSR and ZNFSUSR1) is
purged. Setting PURGEDB to TRUE is equivalent to specifying a FUP PURGEDATA command
on each OSS NFS database file.
Configuration data describes each object defined by the OSS NFS subsystem (except for
the SUBSYS object) plus certain internal information about the subsystem. This data is
retained in files on the subvolume specified by the CONFIG parameter so that OSS NFS
objects do not have to be defined each time the OSS NFS subsystem is started.
Example
The following TACL command starts the OSS NFS manager process, $ZNFS, and brings up the
OSS NFS subsystem in the STOPPED state. The run options specify that:
• The command interpreter is to return immediately with a TACL prompt when the command
has been dispatched.
• Processor 2 is the primary processor.
• The OSS NFS manager process runs at priority 150.
• NULL is the OSS NFS manager process home terminal.
The parameters set specify that:
• CPU 3 is the backup processor.
• $SYSTEM.ZOSSNFS is the subvolume for the OSS NFS configuration file
• $SYSTEM.ZOSSNFS will be purged.
RUN NFSMGR /NAME $ZNFS, NOWAIT, CPU 2, PRI 150, TERM $NULL/&
BACKUPCPU 3, CONFIG $SYSTEM.ZOSSNFS, PURGEDB TRUE
44 Installing and Configuring OSS NFS