Open System Services Management and Operations Guide (G06.29+, H06.07+)

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-005
2-13
Starting the OSS Monitor
Monitor can no longer start an OSS name server or the FSCK utility. A valid terminal
device must exist when the OSS Monitor starts these programs.
One possible solution to the problem is to select a permanent terminal such as an
asynchronous terminal or a terminal-simulator process (such as $ZHOME) and then
specify that device as the OSS Monitor home terminal. For example, to specify the
$ZHOME process as the home terminal for the OSS Monitor, enter:
OSSMON /NAME $ZPMON, NOWAIT, TERM $ZHOME, PRI 180/
Naming the OSS Monitor Process
The OSS Monitor must be given the process name $ZPMON. An attempt to run the
OSS Monitor terminates immediately if $ZPMON is already running or if the OSS
Monitor is given a process name other than $ZPMON.
If the wrong process name is specified, the OSS Monitor abends with completion code
3 (Abnormal, voluntary, but premature termination) and with the Subsystem
Programmatic Interface (SPI) error-number token ZSPI^ERR^BAD^NAME.
Using OSS Monitor Commands
OSS Monitor management operations are performed using the Subsystem Control
Facility (SCF) to enter OSS Monitor commands. When the OSS Monitor is running,
anyone with the proper permission can enter SCF commands to the OSS Monitor.
To start SCF from a TACL prompt, issue the following command:
SCF
The SCF prompt (->) appears. Issue the following SCF command:
ASSUME PROCESS $ZPMON
to begin to communicate with the OSS subsystem. ($ZPMON is the name of the OSS
Monitor process.) You can now enter OSS Monitor commands; however, some
commands are restricted for use only by members of the super group and others are
restricted for use only by the super ID.
Using Wildcard Characters in OSS Monitor Commands:
•
You can use standard UNIX file and directory wildcard characters when specifying
an entity name given as a parameter in certain SCF commands (as indicated in
Section 12, Open System Services Monitor). An entity name is the name of a
fileset, an OSS name server, the OSS sockets local server, or the OSS message-
queue server.
•
The wildcard characters are the asterisk (*), question mark (?), and square
brackets ([ ]). The use of these characters is described in Table 2-3 on page 2-14.
Characters used in wildcard matches are not case-sensitive.