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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-18
Configuration Database Files Used for the OSS
Message-Queue Server
•
Comments are allowed; see the sample file shown in Figure 5-3 on page 5-7.
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:
where disk1, disk2, and disk3 are volume names specified to OSSSETUP.
Figure 4-2 on page 4-11 shows how a storage-pool file (ZOSSPOOL in the figure)
corresponds to the information in other database files in an OSS environment
configuration.
Configuration Database Files Used for the OSS Message-Queue
Server
To start the OSS message-queue server, the OSS Monitor requires a ZOSSSERV file
in the subvolume $SYSTEM.ZXOSSMON.
The ZOSSSERV file is the OSS message-queue server configuration database, and
it contains an automatically created entry that identifies the characteristics of the OSS
message-queue server process. This file must be edited by the system manager using
the SCF ALTER SERVER command.
When a default ZOSSSERV file is created by the OSS Monitor, it contains a #ZMSGQ
entry for the OSS message-queue server process, $ZMSGQ.
Attribute Fileset Fileset Fileset
Fileset name ROOT HOME TEMP
Storage-pool file name ROOTPOOL HOMEPOOL TEMPPOOL
Storage-pool file content:
•
Preconfigured or all defaults
accepted
•
Single pool volume specified
•
Two pool volumes specified
•
Three or more pool volumes
specified
$OSS
disk1
disk1
, disk2
all specified disks
$OSS
disk1
disk1
, disk2
all specified disks
$OSS
disk1
disk2
disk3