Exit EXECs
Exit EXEC InterfaceI Communication Error Exit I LOG Error Exit
The programmable operator facility exit EXECs have the same parameter list pro
vided as an EXEC action routine, with the exception that no RT ABLE parameter
field value and no message text are stacked for the EXEC. When an exit EXEC is
called, contents of the program stack depend upon which exit is being invoked.
Descriptions of the stack contents for the different types of exits follow:
Notes:
1. Some of the parameter values have no meaning for a particular exit EXEC and
their use is left to the discretion of the EXEC writer. For example, requester's
userid and nodeid have no meaning for the communication error EXECs,PROPPCHK and PROPHCHK. 2. The programmable operator facility does not trap VMCONIO-type or CP EMSGs produced by exit EXECs as it does for action routines.
ThePROPPCHK EXEC is invoked when the programmable operator facility
determines that communication with a node that is being checked has changed sta
tus. When this occurs, the following information is stacked,LIFO, for the EXEC.
1. Entries having the format
"nodeidup" or "nodeid DOWN" where:
nodeid is the RSCS nodeid of a node that has changed communication
status.UP indicates that the node had not been responding and has resumed
responding to acknowledgement requests.DOWN indicates that the node had been responding and has ceased respond
ing.
2. Total number of nodeid entries stacked.
ThePROPHCHK EXEC is invoked when the programmable operator determines
that communication with the logical operator node (if it is being checked) has
changed status. If the status has changed, a line is stackedLIFO for the EXEC.
The line is either"nodeid UP" or "nodeid DOWN", where "nodeid" is the RSCS
nodeid of the logical operator and"UP" and "DOWN" have the same meaning as
forPROPPCHK. If a virtual machine resource limit is reached, such as "disk-full", it may not be pos
sible to write another record to the programmable operator facility log file. If this
happens, a user-written EXEC is invoked to perform whatever recovery action the
user thinks is desirable or necessary. The user EXEC must have the filename of
The Programmable Operator Facility 451
Exit EXEC Interface
The programmable operator facility exit EXECs have the same parameter list pro
vided as an EXEC action routine, with the exception that no RT ABLE parameter
field value and no message text are stacked for the EXEC. When an exit EXEC is
called, contents of the program stack depend upon which exit is being invoked.
Descriptions of the stack contents for the different types of exits follow:
Notes:
1. Some of the parameter values have no meaning for a particular exit EXEC and
their use is left to the discretion of the EXEC writer. For example, requester's
userid and nodeid have no meaning for the communication error EXECs,
The
determines that communication with a node that is being checked has changed sta
tus. When this occurs, the following information is stacked,
1. Entries having the format
"nodeid
nodeid is the RSCS nodeid of a node that has changed communication
status.
responding to acknowledgement requests.
ing.
2. Total number of nodeid entries stacked.
The
that communication with the logical operator node (if it is being checked) has
changed status. If the status has changed, a line is stacked
The line is either
nodeid of the logical operator and
for
sible to write another record to the programmable operator facility log file. If this
happens, a user-written EXEC is invoked to perform whatever recovery action the
user thinks is desirable or necessary. The user EXEC must have the filename of
The Programmable Operator Facility 451