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

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.
• Comments are allowed; see the sample file shown in Example 9 (page 147).
Additions to or deletions from a storage-pool file take effect only after the fileset is restarted
(remounted).
Beginning with RVU G06.10, when HP shipped a system with the OSS environment preconfigured,
a storage-pool file named ZINSPOOL was defined for the single predefined fileset and specified
the disk volume $OSS. Beginning with RVU G06.15, when HP ships a system with the OSS
environment preconfigured or you use the OSSSETUP utility to configure your system, the initial
storage-pool files can be:
FilesetFilesetFilesetAttribute
TEMPHOMEROOTFileset name
TEMPPOOLHOMEPOOLROOTPOOLStorage-pool file name
$OSS$OSS$OSSStorage-pool file content
when preconfigured or all
defaults accepted
disk1disk1disk1Storage-pool file content
when single pool volume
specified
disk1, disk2disk1, disk2disk1, disk2Storage-pool file content
when Two pool volumes
specified
disk3All specified disksAll specified disksStorage-pool file content
when Three or more pool
volumes specified
where disk1, disk2, and disk3 are volume names specified to OSSSETUP.
Figure 13 (page 105) shows how a storage-pool file (ZOSSPOOL in the figure) corresponds to the
information in other database files in an OSS environment configuration.
Configuration Files 111