SCF Reference Manual for the Kernel Subsystem
• When specifying a file name, avoid including the system name (unless the file must reside on
a specific system). Omitting the system name allows the process to be system-independent.
• Wild cards are not supported for the ADD command.
Considerations for OSS Persistent Processes
• The STARTUPMSG attribute can have a maximum length of only 128 characters. If a longer
command line is required to start the OSS application process, you can circumvent the 128
character limit by starting a script which includes the longer command line.
• The RUN command for the OSS process must include a '-name' option to set the process name
to the same value as the one contained in the ASSOCPROC attribute.
• The ASSOCPROC attribute value, unlike the value for NAME, is not reserved as a process
name in the configuration database. You must therefore make sure that no configured or
running process has the same name as the one specified in the ASSOCPROC attribute. The
system will validate ASSOCPROC at the time an ADD or ALTER command is issued, but you
must make sure that no other process is using the name specified in ASSOCPROC attribute
before you issue the START command.
• When you specify the CPU attribute using the ALL option or a processor list, make sure that
the value of ASSOCPROC attribute, as well as the matching -name value conveyed through
the STARTUPMSG attribute, contain no more than three characters in addition to the dollar
sign ($) character. You must observe this restriction because the numbering scheme applied
to the PROCESS value is also applied to the ASSOCPROC value. When such processes are
run, a two-digit number is appended to the name of each instance of the process, indicating
the processor in which that instance runs.
An ENV variable called $ZCPU facilitates this numbering scheme. $ZPM supplies values for
this variable when processes are created in different CPUs. In this way, it provides a unique
name for every instance of a process. The $ZCPU variable should be included as part of the
run command’s -name specification, which you can include in either the STARTUPMSG attribute
itself or in a shell script that STARTUPMSG invokes. $ZPM resolves the $ZPU variable only
for persistent process objects whose CPU specification is either the keyword ALL or a list of
processors.
For details about writing a shell script, see the Open System Services Management and
Operations Guide.
• If you want the initial environment to be the initial logon state, specify -ls in the the
STARTUPMSG attribute or in a shell script that the startup message invokes.
• If you want the OSS persistent process to direct standard input, standard output, or standard
error information to TTY devices, the command line in STARTUPMSG must redirect STDN,
STDOUT, or STDERR to the appropriate devices.
• The BACKUPCPU attribute is not supported for OSS persistent processes.
• An OSS persistent processes must specify the STARTMODE attribute as MANUAL.
• For OSS persistent processes, the PRIORITY attribute should be allowed to retain its default
value.
• An OSH process delays for ten seconds before it launches the OSS process.
Examples
• To add a process specifying only required attributes:
-> ADD PROCESS $ZZKRN.MY-OWN-PROCESS, &
NAME $GT72, &
ADD Command (Sensitive Command) 83