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-8
Starting the OSS Monitor
OSSSETUP utility, you can start $ZSMP by using the STARTOSS utility; see
STARTOSS Utility on page C-14 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).
AUTOSTART { AUTO | MANUAL }
specifies whether the automatic startup service should start servers or filesets
that are configured for automatic startup. If this parameter is specified on the
command line, it overrides any previous specification of an AUTOSTART
PARAM. This parameter also overrides the current value for the AUTOSTART
attribute of the subsystem; see the SCF ALTER SUBSYS, ALTER MON, and
ALTER PROCESS Commands on page 12-32 for more information.
3. Use the TACL STATUS command to verify that the OSS Monitor process $ZPMON
is running:
STATUS $ZPMON
4. If the OSS Monitor process is not running, check the Event Management Service
(EMS) log for related event messages. See Appendix A, Messages, for explanation
of any messages received and possible corrective actions.
Starting the OSS Monitor from a TACL prompt with an AUTOSTART value of AUTO
does not take full advantage of the automatic startup service. To fully use the automatic
startup service (so that the OSS environment is brought up when the system is
loaded), you must start the OSS Monitor as a persistent process.