Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
LERAD exit routine z/OS Communications Server: SNA Programming SC27-3674-00 |
|||||||||||||||
A LERAD exit routine is identified in an ACB exit list when the application program wants a routine to be automatically invoked when a logic error (in contrast to a physical error) is detected. Generally, a logic error results when an RPL-based request is made that is inherently contradictory, for example, when attempting to use an CID that is not valid. The SYNAD exit routine handles physical errors (such as hardware malfunctions). The LERAD exit routine, if specified, is entered for recovery action return codes of 20 and 24 (decimal). Handling errors and special conditions, discusses the use and logic of LERAD exit routines in detail. When the LERAD exit routine returns control to VTAM®, VTAM leaves registers 0 and 15 intact so that the routine can pass information in these registers back to the part of the application program from which LERAD is invoked. VTAM returns control to the next sequential instruction in the application program following the RPL-based request. Because the routine is executed under the same system scheduling control block as the part of the program that issues the RPL-based or CHECK macroinstruction, LERAD can branch to other parts of the program. If LERAD is entered from an RPL-based request or if the CHECK is issued in an asynchronous exit routine, the program must eventually branch to register 14. If the routine returns control to the next sequential instruction by branching to the register 14 address, VTAM restores the register from the save area whose address is in register 13. If the exit routine is running under an SRB, different conditions apply for return. See Execution of exit routines.
|
Copyright IBM Corporation 1990, 2014
|