Safeguard Reference Manual (G06.29+, H06.08+, J06.03+)

Event-Exit-Process Commands
Safeguard Reference Manual — 520618-030
15 - 34
Event-Exit Design, Management, and Operation
•
The event-exit process can be a process pair to ensure its continuous availability to
handle authorization requests. If it is not a process pair, the event-exit process is
unavailable to handle requests during its initialization interval after a restart.
•
Any user file maintained by the event-exit process must support 32-byte user alias
names and their passwords.
•
To avoid the possibility of deadlocks, the event-exit process must not perform
waited operations after initialization.
The Safeguard $ZSMP starts and manages the event-exit process. Each time $ZSMP
starts the event-exit process, it first attempts to kill any process with the same process
name not started by the $ZSMP. An EMS message notes this action. If the $ZSMP
finds that the event-exit process was not started by the $ZSMP, it does not send
messages to the event-exit process until it successfully kills the process and restarts it.
Be careful to avoid name collisions.
When the ENABLED flag is set to ON, $ZSMP attempts to start the event-exit process.
Safeguard tries maximum of three attempts to start this process. For every attempt that
fails, an EMS event is logged. If all attempts fail, Safeguard stops the process creation
attempt and turns the ENABLED flag to OFF. An event is also logged if Safeguard
encounters an error while resetting the ENABLED flag to OFF. If the event-exit process
creation request fails, you must verify the ENABLED flag for the process. If the
ENABLED flag has not been turned OFF by Safeguard, you must turn the flag OFF
manually.
If the event-exit process stops abruptly, $ZSMP attempts to restart the process until it
is successfully restarted or disabled. An EMS message is sent to the console informing
the operator each time Safeguard attempts a restart. Safeguard tries maximum of
three attempts to restart the process. To avoid a negative impact to the performance of
the $ZSMP, Safeguard attempts each restart after a specified interval. If the process
creation fails at the end of three attempts, the ENABLED flag is reset to OFF. Requests
are not sent to the event-exit process until the restart is successful.
If the processor in which the event-exit process is running becomes unavailable, the
backup CPU is used as the primary CPU. If neither the primary or backup CPU is
available, the event-exit process is rest
arted in the same CPU as the $ZSMP.
$ZSMP opens the event-exit process with the name $name.#Z
SEEP, where name is
the name assigned in the event-exit configuration record. Because the event-exit
process can be opened by processes other than Safeguard security processes, the
subdevice name #ZSEEP allows the event-exit process to determine the intention of
the opener. It also allows the event-exit process to determine which message protocol
is being used.
To avoid deadlocks, the event-exit process is a security process. Messages received
from the event-exit process are not be sent to the event-exit process. Child processes
Note. HP recommends that when $ZSMP is attempting to start the event-exit process,
Safecom must not be used to issue any other commands, until the result of the process
creation is displayed at the Safecom prompt.