SCF Reference Manual for the Kernel Subsystem

EXTSWAP { $vol | [[$vol.]subvol.]filename }
HIGHPIN { ON | OFF }
HOMETERM $device[.#subdevice]
INFILE { $device | [[$vol.]subvol.]filename }
LIBRARY [[$vol.]subvol.]filename
MEMPAGES n
NAME $name
OUTFILE { $device | [[$vol.]subvol.]filename }
PFSSIZE n
PRIMARYCPU n
PRIORITY n
PROGRAM [[$vol.]subvol.]filename
SAVEABEND { ON | OFF }
STARTMODE { KERNEL | SYSTEM | APPLICATION | MANUAL | DISABLED }
STARTUPMSG "text"
STOPMODE { SPI | STANDARD | SYSMSG }
TYPE { FOXMON | SUBSYSTEM-MANAGER | OTHER }
USERID { groupname.username | groupnum,usernum }
ASSOCPROC name
specifies the name of an OSS application to be run as part of a named generic process, whose
persistence is monitored by the Kernel subsystem’s persistence-manager process ($ZPM). The
OSH that launches the process must also be made persistent. Thus, when you specify the
ASSOCPROC attribute, you must also:
• Specify the name of an OSH process in the NAME attribute
• Specify the OSH object file in the PROGRAM attribute.
• Use the STARTUPMSG attribute to specify the startup message that is sent to the OSS
application.
Thus, the persistent process object created through an ADD PROCESS command consists of
two distinct persistent processes: the OSH process and the OSS application process itself. An
ABORT, DELETE, or START command issued to this object affects both processes.
AUTORESTART n
specifies the number of times that the $ZPM persistence manager attempts to restart this process
within a 10-minute interval after an abnormal termination. The process abends or stops by a
means other than the ABORT command.
If n is 0 (the default), the process is not automatically restarted.
If n is 1 through 10, the process is restarted as many as n times in 10 minutes.
If n is greater than 0 when a processor fails, the processor is reloaded, its previously running
generic processes are restarted, but the value of n is not decremented. For more information
about what conditions decrement the count, see Table 5: Effect of Stopping on the Persistence
of a Generic Process (page 46).
For more information about using the AUTORESTART attribute, see “Persistence Considerations”
(page 45).
BACKUPCPU n
specifies the processor in which this process should start its backup process. For more
information, see “Controlling Where a Generic Process Starts” (page 43) and “Controlling
When a Generic Process Starts” (page 43).
To specify this attribute, you must also specify (or have previously specified) the PRIMARYCPU
attribute, but you must not specify the CPU attribute.
The variable n can be from 0 through the maximum number of processors (the BACKUPCPU
value specified cannot be the same as the PRIMARYCPU value).
You should not specify BACKUPCPU for any OSS persistent process.
ADD Command (Sensitive Command) 77