Open System Services Management and Operations Guide (G06.29+, H06.07+)

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-005
2-26
Making OSS Application Processes Persistent with
the Kernel Subsystem
•
When more than 128 characters are required to correctly start an application or
script, a script requiring less than 128 characters in its STARTUPMSG attribute can
be run to start the command or script that needs to be made persistent.
The following SCF commands for the NonStop Kernel subsystem support OSS generic
processes:
•
ABORT – Stops a persistent process
•
ADD – Initially configures a persistent process
•
ALTER – Changes the configuration of a persistent process
•
DELETE – Removes the configuration for a persistent process
•
INFO – Provides information about the configuration of a persistent process
•
STATUS – Provides information about the current state of a persistent process
•
START – Starts a persistent process when it is not started automatically
Examples
1. Suppose your site needs to monitor an application log and routinely runs the
command
tail -f log
from an OSS shell prompt at a dedicated operator console. To make this process
persistent, enter the following commands:
a. From a TACL prompt:
WHO
which produces output that includes the HOMETERM value you need to use,
such as:
Home terminal: $ZTN0A.#PT4KH30
...
b. Then, at an SCF prompt for the NonStop Kernel subsystem:
ADD PROCESS OSSAPP,
NAME $OSH1,
AUTORESTART 10,
HOMETERM $ZTN0A.#PT4KH30,
PRIMARYCPU 1,
STARTMODE MANUAL,
USERID OSS.APPS,
PROGRAM $SYSTEM.SYSTEM.OSH,
ASSOCPROC $OSS1,
STARTUPMSG "-ls -name /G/oss1 -p /bin/tail -f log"
c. Because the configuration uses a STARTMODE of MANUAL, you must enter
the following command at an SCF prompt to start the process:
START PROCESS $ZZKRN.#OSSAPP
These commands configure and start the persistent process object OSSAPP in
processor 1, using the named process $OSH1 to launch the OSH utility. Then OSH