GDSX (Extended General Device Support) Manual

Service Routines
Extended General Device Support (GDSX) Manual—529931-001
8-77
^SIGNALINTERRUPT
external openers. You can issue SCF commands against GDSX during and after the
shutdown process.
Considerations
•
When ^SHUTDOWN is called, all active LINEs and SUs are queried to determine
whether they have external openers. If no external openers exist, then the primary
and backup GDSX processes are stopped and an EMS event message is
generated indicating that a shutdown occurred. The message is as follows:
STATUS *1002* GDS NORMAL SHUTDOWN
If there are external openers, the tasks are allowed to complete current I/Os from
or to the openers, and the tasks continue to exist until all external openers are
closed, or until SCF ABORT LINE and/or ABORT SU commands are issued. In
the interim, an EMS event message notifies you that a shutdown is in progress
(pending) and that the GDSX process will be stopped only after all external
openers are closed or terminated. The message is as follows:
STATUS *1006* GDS SHUTDOWN PENDING
During this interval all new open attempts against the GDSX process are rejected,
except those from SCF.
•
You can still issue an SCF INFO TASK command on a LINE or SU to determine its
tcb.state.<1> value after ^SHUTDOWN is called. If this bit is set to 1, the task is in
the stop-pending state, meaning that it will die after all its openers are closed.
Once all the openers are closed or terminated, the primary and backup GDSX
processes are stopped.
•
A call to ^SHUTDOWN is the same as issuing the following SCF STOP command:
STOP PROCESS $GDSX-process-name
•
A call to ^TERMINATE is the same as issuing the SCF STOP command with an
exclamation point:
STOP PROCESS $GDSX-process-name !
^SIGNALINTERRUPT
The ^SIGNALINTERRUPT entry point for the ^SIGNALTIMEOUT procedure sets a
timer to a given number of units of elapsed time. When the time expires, the calling
task receives an indication in the form of a system message on $RECEIVE in the case
of a DEVICE^HANDLER task or on $RECEIVE in the case of a LINE^HANDLER task.
Except for the following considerations, the syntax, condition code settings, and
considerations regarding this procedure are the same as the SIGNALTIMEOUT
procedure in the Guardian Procedure Calls Reference Manual.
CALL ^SHUTDOWN