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

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 “Open System Services
Monitor” (page 251)). 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 5 (page 55). Characters used in wildcard matches
are not case-sensitive.
Table 5 Wildcard Characters in OSS Monitor Commands
Uses and ExamplesCharacters
An asterisk represents any number of characters (including zero) in an entity name. Use this
character to save keystrokes when:
*
◦ Entering a single name.
For example, you can enter RO* for ROOT.
◦ Naming many entities at once.
For example, /us* matches /user1, /us, and /usr.
A question mark represents any single character.For example, h?p matches hop and hip,
but not help.
?
Square brackets enclose a choice of characters you want to match. You can specify a range
of characters by separating them with a hyphen, with the lower ASCII value to the left of the
[ ]
hyphen. Uppercase A has a lower ASCII value than lowercase a, and there are characters
between Z and a. For example:
◦ [Cc]hapter matches both Chapter and chapter.
◦ [ch]apter matches both capter and hapter (but not chapter).
◦ chapter[1-3] matches chapter1, chapter2, and chapter3.
Managing the OSS Subsystem 55