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

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-002
2-7
Starting the OSS Monitor
messages recorded using the Event Management Service (EMS) through either of the
following:
•
The OSS shell logger command
•
Program calls that use the syslog() function and related functions
For more information about the logger command, see the logger(1) reference
page either online or in the Open System Services Shell and Utilities Reference
Manual. For more information about the syslog() function, see the syslog(3)
reference page either online or in the Open System Services Library Calls Reference
Manual.
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 Appendix A, Messages. 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 on page 5-38.
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 on page 2-7.
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 on page 2-15.
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 task described under Maintaining ZOSSFSET After
Changing Your Node Number on page 4-11.
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