Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-6
Creating a Storage Pool
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.
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 on page 4-17 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.
Figure 5-3 on page 5-7 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 on page C-14 for more information.
Alternatively, you can use the SCF START FILESET Command to manually start or
restart an existing fileset, as described on page 12-65. 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 on page 5-8
•
Automatic Restart of Filesets by the Automatic Startup Service on page 5-9