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

Example 9 A Storage-Pool File
==
== File: $SYSTEM.ZXOSSMON.OSSPOOL
==
== This file is a sample POOL file. A POOL file defines the disk volumes
== where OSS files of an OSS FILESET can be created. OSS FILESETs, which
== are managed by the OSS Monitor ($ZPMON), have an attribute named POOL,
== which is the name of a Guardian EDIT file that resides in the subvolume
== $SYSTEM.ZXOSSMON. Multiple OSS FILESET objects may share a common
== POOL file.
== The contents of this file are a list of disk volumes, one per line.
== Up to 20 disk volumes may be specified in a POOL file. Leading whitespace
== is not allowed before a filename, but trailing whitespace is allowed.
== Comment lines are allowed and start with the characters ==
==
== This sample POOL file specifies 3 disk volumes where OSS files may be
== created.
==
$OSS1
$OSS2
$OSS3
==
== **************************************************************************
== * WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING *
== **************************************************************************
== * *
== * 1) This file, $SYSTEM.ZXOSSMON.OSSPOOL, is a sample file that is *
== * replaced each time the T8622 product is installed. Do not configure *
== * OSS FILESETs to use this file as a POOL file, since this file will be *
== * overwritten during each T8622 installation. *
== * *
== * 2) Do not use the volume $SYSTEM in POOL file, as OSS files should not *
== * be placed on $SYSTEM. *
== * *
== * 3) The contents of a POOL file may be changed at any time, however, *
== * changes only take affect when the associated FILESET is started. *
== * *
== * 4) For installations that use SQL/MP and have OSS programs with *
== * embedded SQL statements in them, do not use volumes that have 8 *
== * character names (including the $). SQL/MP has a restriction that *
== * it cannot access programs that reside on volumes with 8 character *
== * names. *
== * *
== **************************************************************************
Automatic Restart of Filesets During OSS Monitor Startup
The OSS Monitor uses the ZOSSFSET file to record the state of each fileset (for example, STARTED,
STOPPED, or DIAGNOSING). Whenever a fileset is started, an entry is made indicating that the
fileset is in the STARTED state. When the fileset is stopped, the state of the fileset is changed to
STOPPED.
When the OSS Monitor is started for the first time after a system load, it checks the desired-state
configuration for all filesets to determine which filesets it must start or restart. Refer to “Automatic
Restart of Filesets by the Automatic Startup Service” (page 148) for more information.
When the OSS Monitor is restarted at any other time, it performs a restart sequence. The OSS
Monitor checks the recorded state of each fileset.
For each fileset that was left in the STARTED state, the OSS Monitor checks whether the OSS name
server for that fileset is still running. If that OSS name server is still running and the fileset was left
in the STARTED state, the OSS Monitor assumes that the fileset is still in the STARTED state and is
not corrupt.
Starting (Mounting) or Restarting Filesets 147