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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-17
Configuration Files Used for the OSS Name Servers
The Storage-Pool Files
The storage-pool files define the disk volumes that each fileset is currently allowed to
use when creating new files. The storage-pool files must be created or edited by the
system manager using a Guardian text editor. They must be present and must contain
valid data before the OSS Monitor is started.
HP recommends:
•
The Guardian file identifier for a storage-pool file should either start with Z or have
the form mnemonicPOOL, where mnemonic is a four-character identifier that
associates that storage-pool file with its corresponding fileset. For example, in a
system with only one fileset named ROOT, the storage-pool file should be named
ROOTPOOL.
•
The file identifier ZOSSPOOL should not be used, to avoid conflict with an
unreleased HP feature.
•
The file identifier OSSPOOL should not be used, to avoid conflict with the file
identifier for the sample storage-pool file installed with the OSS product set.
Entries in a storage-pool file must follow these rules:
•
The name of a disk volume can consist of a dollar sign ($) followed by 1 to 6
uppercase letters and digits (A through Z and 0 through 9). The character after the
$ must be a letter. (Avoid 8-character disk volume names to avoid problems with
HP NonStop SQL/MP program objects that might reside in the OSS environment.)
•
One disk volume name can be specified on each line.
•
Up to 20 entries are allowed in the file.
•
The disk volumes specified:
°
Cannot be optical disks.
°
Cannot be administered through the NonStop Storage Management
Foundation (SMF).
°
Should not be in any other storage pool. Disk volumes can be shared among
storage pools, but that practice makes it very difficult to monitor and control
free space within a fileset.
•
HP recommends that:
°
A fileset should not include the disk volumes $SYSTEM or $DSMSCM in its
storage pool.
°
The root fileset should have more than one disk volume in its storage pool to
allow for future expansion.
°
A small fileset should have only one disk volume in its storage pool for best
performance.