SCF Reference Manual for the Kernel Subsystem

Processor Reload Considerations
The effect on a generic process of a later processor reload (not the first reload of the processor
after a system load) depends on all of these circumstances:
• The object state the process was in before the processor reload
A process in the STOPPED state, ABORTED substate is not restarted.
• The configured start mode
A prosthetic has a start mode of KERNEL, SYSTEM, or APPLICATION and that is not in the
ABORTING state or ABORTED substate is automatically started when its processor comes up
regardless of the autoconfigured AUTORESTART value.
A process with a start mode of MANUAL is automatically restarted when its processor comes
up, if it is not in the ABORTING state or ABORTED substate and if one of these is true:
◦ You entered a START command after the processor was down.
◦ It had been running when the processor went down, and its configured AUTORESTART
value is greater than 0.
As a result of a processor reload, both of these conditions are true:
• The persistence count is not decremented.
• The $ZPM persistence manager starts the generic process.
Table 7 lists these processor reload considerations.
Table 7 Later Processor Reload Considerations for Persistence
Situation 2Situation 1Consideration
Is either ABORTING state or
STOPPED state, ABORTED substate
Is either STARTED state or
STOPPED state, STOPPED
substate
Generic process object state prior
to processor load…
If…
Has any valueIs KERNEL, SYSTEM,
APPLICATION, or (if it had been
started) MANUAL
Start mode…and if…
Is reduced to 0 by ABORTIs not decrementedPersistence count…Then…
Doesn’t restart the process.Restarts the process regardless of
the current persistence count.
$ZPM…and…
($ZPM might restart the generic
process in the backup processor
if that processor comes up before
the primary processor.)
Abnormal Event Considerations
An abnormal event is defined as an event that stops a process other than an SCF ABORT command
or a processor failure. For example:
• The process abends and its object state becomes STOPPED, while its substate is not ABORTED
(as shown by an SCF STATUS command display for the process).
• The process is stopped outside SCF, perhaps by a TACL STOP command.
After an abnormal event stops a generic process:
• The $ZPM persistence manager restarts the process if its persistence is greater than zero, even
if its start mode is MANUAL.
• $ZPM decrements the persistence count.
Table 8 lists these abnormal event considerations.
Controlling When a Generic Process Starts 47