Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

The backup OSS name server does a close of the OSS SEEP when the primary OSS name server
closes the OSS SEEP, which results in the graceful stop of the OSS SEEP.
OSS SEEP-Related EMS Events
The OSS name server generates EMS events to $0 and $ZLOG under the following conditions:
• The OSS SEEP is successfully started. The EMS event reports the OSS SEEP state change from
STOPPED to RUNNING.
• The OSS SEEP is stopped or an OSS SEEP death occurs. The EMS event reports the OSS SEEP
state change from RUNNING to STOPPED.
• The OSS SEEP failed to start. The EMS event reports the OSS SEEP state change from STOPPED
to STOPPED with the error indicating the reason for failure.
• There is an error sending an authorization request to the OSS SEEP. The EMS event reports
a communication error with the OSS SEEP.
NOTE: For an OSS SEEP creation failure or upon an OSS SEEP death, the OSS name server
attempts to restart the OSS SEEP after a predefined interval of 30 seconds. The restart is done
indefinitely until the OSS SEEP creation succeeds or the SEEPENABLED attribute value is set to OFF.
After the EMS event for an OSS SEEP start failure is generated, the same EMS event is not generated
for a predefined hold-off period of 2 minutes.
For an OSS SEEP death due to a CPU failure, the restart is attempted immediately using the following
order for the first available CPU:
1. The CPU specified in the SEEPCPU attribute
2. The backup CPU specified in the first word of the SEEPPARAMTEXT attribute
3. The OSS name server’s CPU
234 Managing Security