GLOBAL_EVENTS
#--------------------------------------------------------------------------
##########################################################################
# SPECIAL NOTE:
# Most procedures specify a response to "emergency" and
# "abort_limit" events and always use the same procedures.
# If this is the case, these specifications should be removed
# from the procedure files and place in the header file as
# @UNIVERSAL_EVENTS and @UNIVERSAL_REGISTERED_EVENTS. Then
# these responses will be in effect for all test procedures
#
# @GLOBAL_EVENTS specify events that are handled
# the same regardless of which test mode is active.
#
# If neither the next_mode or the test_procedure are specified, then
# the mode is just terminated and the normal path is taken.
#
# If the next_mode is specified, but the test_procedure is not,
# then the test will jump to that mode in this procedure.
#
# If the test_procedure is specified, but the next_mode is not,
# then the test will jump to that sub-procedure. If the sub-procedure
# exits via a RETURN, the the current procedure will begin executing
# at the default_next_mode specified for the test mode that was
# interrupted.
#
# If both next_mode and test_procedure are specified, the next_mode
# will be ignored. The return will be to the default_next_mode
# of the test mode that was interrupted by the event. If the
# test_procedure file does not exist or cannot be opened, then this
# mode will be executed next.
#
# Note: the RETURN macro may be used in the "next_mode" field to
# return control to a calling procedure.
# a maximum of 8 events may be specified as @GLOBAL_EVENTS
#
@GLOBAL_EVENTS
#event_name next_mode test_procedure
emergency 93 /specs/gp/gp_emergency
abort_limit 93 /specs/gp/gp_shutdown
test_done RETURN