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

Managing OSS Processes
You can manage the availability of OSS processes in several ways:
• Using the Kernel Subsystem, as described in “Making OSS Application Processes Persistent
with the Kernel Subsystem” (page 64)
• Using OSS tools that schedule periodic tasks, as described in “Using the cron Process”
(page 73)
• Using Guardian tools that schedule periodic tasks, as described in “Using the NetBatch
Product” (page 75)
You can manage workload-related behaviors of OSS processes best from the OSS environment
using OSS shell run command options that correspond to TACL RUN command options. See
“Managing OSS Process Scheduling” (page 69) and “Managing OSS Process Processor Use”
(page 71).
Making OSS Application Processes Persistent with the Kernel Subsystem
Just as the OSS Monitor can be made a persistent process using the SCF interface to the NonStop
Kernel subsystem, the same SCF interface provides commands to configure, start, and stop OSS
application processes that are persistent. A persistent process is automatically started when certain
criteria are met and then automatically restarted if events make the original copy of the process
unavailable. Such processes are called generic processes in SCF documentation. This subsection
provides suggestions for possible uses of this facility; for a complete description of the commands,
process attributes, and parameters, see the SCF Reference Manual for the Kernel Subsystem.
Generic OSS processes have the following characteristics:
• Both shell scripts and compiled programs can be made persistent.
• Each OSS process is started by configuring a copy of the Guardian OSH utility to start it.
• Each process has the following configurable attributes under the persistence manager (attributes
are the same as for a Guardian generic process):
◦ AUTORESTART
◦ CPU – Applies to names used for both NAME and ASSOCPROC attributes
◦ HOMETERM – Always the terminal used by the TACL for the ADD command
◦ MEMPAGES
◦ NAME – Always identifies a copy of OSH
◦ PRIMARYCPU
◦ PRIORITY – Always use the default priority
◦ PROGRAM – Always specifies $SYSTEM.SYSTEM.OSH
◦ SAVEABEND
◦ STARTMODE – Always must be MANUAL
◦ STOPMODE
◦ TYPE
64 Operating the OSS Environment