Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

• Is unrestricted by default
• Accepts the FTIOMODE and NORMALIOMODE default settings for file opens
• Start the fileset with the SCF START FILESET command.
Figure 18 (page 145) 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.
Figure 18 Starting (Mounting) a Fileset
Creating a Storage Pool
You create a storage pool by creating a storage-pool file.
You can use any valid Guardian file identifier for the name of a storage-pool file. However, you
should not name a storage-pool file OSSPOOL so that your storage pool definition is not overwritten
by the sample file in a reinstallation or an upgrade of the OSS environment.
Creating a Fileset 145