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

EMS messages logged through the logger command or the syslog() function are described
in the Operator Messages Manual.
The OSS subsystem as described in this guide produces the informative and diagnostic messages
discussed in “Messages” (page 335). Those messages are returned when you use either the SCF
commands for the OSS Monitor or the CVT utility, as discussed under “Managing and Repairing
Fileset Catalog Files” (page 170).
You start the OSS subsystem by starting the OSS Monitor at least once. The OSS Monitor was
probably started when the OSS environment was installed. If you need to start or restart the OSS
Monitor, see “Starting the OSS Monitor” (page 51).
OSS Monitor commands can be used on the subsystem itself, on server objects, or on fileset objects.
Use on the subsystem itself is discussed in the following subsections. Using OSS Monitor commands
on servers and filesets is discussed in later sections of this guide.
Although you cannot stop the entire subsystem without stopping its individual components and the
OSS file system, you can temporarily stop the OSS Monitor. See “Stopping the OSS Monitor”
(page 56).
Starting the OSS Monitor
The OSS Monitor can be started as either a normal process or a persistent process. Starting the
OSS Monitor as a persistent process also allows you to enable the automatic startup service for
selected OSS servers and filesets after a system load or restart.
Before starting the OSS Monitor, note that:
• The security process $ZSMP should be running before the OSS Monitor is started. If $ZSMP
is not running, security auditing, user aliases, and supplementary groups are not available
for the OSS environment.
• If your node number has changed since the last time the OSS Monitor was started, you should
perform the maintenance task described for the “The ZOSSFSET File” (page 101).
Beginning with the G06.15 release version update (RVU), if your system was ordered preconfigured
or your initial OSS configuration was performed by using the OSSSETUP utility, you can start
$ZSMP by using the STARTOSS utility; see “STARTOSS Utility” (page 405) for more information.
Alternatively, you can perform these actions yourself.
Starting the OSS Monitor as a Normal Process
1. Log in as the super ID.
2. At a TACL prompt, enter:
OSSMON / NAME $ZPMON, NOWAIT, CPU nn, TERM name, PRI pri / &
[ AUTOSTART { AUTO | MANUAL } ]
CPU nn
is the processor number of the processor you want the OSS Monitor to run on. The processor
number you specify is arbitrary and should be chosen based on the system workload for all
the processors.
TERM name
is the name of the home terminal for the OSS Monitor. Make sure that this terminal is always
available and that it is not a Telserv or Multilan session. The $ZHOME process can be specified
for name.
PRI pri
is the priority to run the OSS Monitor at. The value used should be lower than the priority used
by $ZSMP (198).
Managing the OSS Subsystem 51