Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Commit_Agent_UR (ATRACMT, ATR4ACMT) z/OS MVS Programming: Resource Recovery SA23-1395-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A resource manager that has taken the server distributed syncpoint resource manager (SDSRM) role calls Commit_Agent_UR to tell RRS to commit the unit of recovery (UR) associated with the specified UR interest. The SDSRM can invoke this service to resolve an in_doubt unit of recovery to in_commit. Commit_Agent_UR changes the unit of recovery state to in_forget or forgotten. If a resource manager with an interest in a UR has taken the SDSRM
role, RRS will implicitly change the log_option to
ATR_DEFER_EXPLICIT under any of the following conditions:
If any of these conditions has occurred, RRS returns the ATR_UR_STATE_ERROR return code. The UR might be in any state, but, once it reaches in-forget, it will remain in that state until the Forget_Agent_UR service is called. RRS waits for Forget_Agent_UR to ensure that the resource manager that has taken the SDSRM role is always informed of the results of the UR and allows the resource manager to safely prevote its BACKOUT and COMMIT exits. Environment
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:
RestrictionsTo use the service:
CAUTION: The resource manager must ensure that
no application can be updating protected resources for the unit of
recovery being committed. This is necessary to ensure that no resource
manager taking part in the unit of recovery sees updates being made
on behalf of a unit of recovery at the same time as they are executing
syncpoint processing.
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. Syntax
ParametersThe parameters are explained
as follows:
ABEND codesThe call might result in an abend X'5C4' with a reason code of either X'001B0000' or X'001B0001'. 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
resource manager wants to commit the unit of recovery. Storage for
the call parameters has been allocated.
|
Copyright IBM Corporation 1990, 2014
|