Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Backout_UR (ATRBACK, ATR4BACK) z/OS MVS Programming: Resource Recovery SA23-1395-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
A resource manager or application program calls the Backout_UR service to indicate that the changes for the unit of recovery (UR) are not to be made. In response, RRS requests that the resource managers return their resources to the values they had before the UR was processed, then issues a return code to the caller. This call performs the same services as the Application_Backout_UR (SRRBACK) service, with one exception: Backout_UR provides return codes for many error conditions that cause Application_Backout_UR to abnormally end the calling program with abend code X'5C4'. For a description of Application_Backout_UR, see z/OS MVS Programming: Callable Services for High-Level Languages. EnvironmentThe requirements for the caller are:
Programming requirementsEither link edit your object code with the linkable stub routine ATRRCSS (31 bit) or ATRR4CSS (64 bit) from SYS1.CSSLIB, or LOAD and CALL the callable service. The high level language (HLL) definitions for the callable service are:
RestrictionsThe UR state must be in-reset or in-flight. The UR must not be in local transaction mode. Input register informationBefore issuing the call, the caller does not have to place any information into any register unless using it in register notation for the parameters, or using it as a base register. Output register informationWhen control
returns to the caller, the GPRs contain:
When control returns to the caller, the ARs
contain:
Some callers depend on register contents remaining the same before and after issuing a call. If the system changes the contents of registers on which the caller depends, the caller must save them before calling the service, and restore them after the system returns control. Performance implicationsNone. SyntaxWrite the call as shown in the syntax diagram. You must code the parameters in the CALL statement as shown.
ParametersThe parameters are explained
as follows:
ABEND codesThe call might result in an abend X'5C4' with a reason code of either X'00170000' or X'00170001'. See z/OS MVS System Codes for the explanations and actions. Return codesWhen the service returns control to the resource manager, GPR 15 and return_code contain a hexadecimal return code.
ExampleIn the pseudocode example, the
calling program backs out a UR.
|
Copyright IBM Corporation 1990, 2014
|