Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Filesets
Open System Services Management and Operations Guide—527191-005
5-5
Creating a Unique Fileset
•
Decreases the likelihood of needing fileset recovery by decreasing the value
used for MAXDIRTYINODETIME from its default value to 10 seconds
•
Makes the fileset automatically restart when necessary if the automatic startup
service is used, and uses the processor (specified as -1) used by the disk
process for the fileset to perform any fileset repairs needed
•
Specifies that the OSS name server for the fileset retains the results of
nonretryable Network File System (NFS) operations for 70 seconds
•
Assigns the fileset MINE to the storage pool defined by the storage-pool file
with the name of ZOSSMYPL
•
Allows read and write access to the fileset by default
•
Accepts the FTIOMODE and NORMALIOMODE default settings for file opens
4. Start the fileset with the SCF START FILESET command.
Figure 5-2 on page 5-6 shows how a fileset is mounted at a mount point when the
fileset is started. The figure illustrates the effects of the following command:
START FILESET $ZPMON.USER1
The files new1, new2, and new3 in the fileset USER1 are not available to users
until this command is entered, although they are in the system on the disk volume
$DATA5. Previous commands, such as:
ADD FILESET $ZPMON.USER1, CATALOG $USR1CAT, POOL ZOSSU1PL, &
MNTPOINT "/usr/utils/src"
START FILESET $ZPMON.USER1
.
.
.
STOP FILESET $ZPMON.USER1
would have allowed these files to be created in the storage-pool file ZOSSU1PL
(not shown) on the catalog volume $USR1CAT (not shown).
After the fileset USER1 is mounted, the files new1, new2, and new3 are available
as /usr/utils/src/new1, /usr/utils/src/new2, and
/usr/utils/src/new3.