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

To define the storage-pool file that is associated with a fileset record:
1. Use a Guardian text editor to create the storage-pool file.
The storage-pool file must be in the same subvolume ($SYSTEM.ZXOSSMON) as the ZOSSFSET
file.
2. Enter the names of disk volumes that will contain the OSS files in this fileset, one disk volume
name on each line. See “The Storage-Pool Files” (page 110) for the rules about specifying disk
volumes in storage-pool files.
3. Exit the editor.
The name of the storage-pool file used for each fileset appears in that fileset’s database record.
The OSS Monitor uses this information to tell the OSS name servers where to put OSS data files.
Example 9 (page 147) shows the contents of a storage-pool file. This storage-pool file was created
during installation by copying the sample EDIT file OSSPOOL from the ZXOSSMON subvolume
of the installation volume and modifying it appropriately.
Starting (Mounting) or Restarting Filesets
An OSS fileset is not available to users until it is started or restarted. This action is also known as
mounting a fileset.
You start a fileset:
• At least once to create the catalog files for it
• After it has been deliberately stopped for any reason
• When it is not automatically restarted
If your site uses the STARTOSS utility, that utility starts all filesets named in the OSSINFIL file. See
“STARTOSS Utility” (page 405) for more information.
Alternatively, you can use the SCF START FILESET command to manually start or restart an existing
fileset. Only super-group users (255,nnn) can use the START FILESET command.
Certain failure conditions cause filesets to be automatically restarted. The following subsections
describe:
• “Automatic Restart of Filesets During OSS Monitor Startup” (page 147)
• “Automatic Restart of Filesets by the Automatic Startup Service” (page 148)
• “Automatic Restart of Filesets After OSS Name Server Failure” (page 148)
• “Automatic Restart of OSS Name Servers After Processor Failure” (page 148)
• “Potential Problems During Automatic Restart of Filesets” (page 148)
146 Managing Filesets