Rollback Required (QTNRBRQD) API
Required Parameter Group:
| 1 | Resource handle | Input | Binary(4) |
| 2 | Error code | I/O | Char(*) |
Threadsafe: Yes
The Rollback Required (QTNRBRQD) API puts the commitment definition currently active for the activation group of the program making the request into a rollback-required state. When a commitment definition is in a rollback-required state, protected resources cannot be used until a rollback operation is performed.
Authorities and Locks
None.
Required Parameter Group
- Resource handle
- INPUT; BINARY(4)
The resource handle returned by the Add Commitment Resource (QTNADDCR) API when the API commitment resource was added to the current commitment definition.
- Error code
- I/O; CHAR(*)
The structure in which to return error information. For the format of the structure, see Error code parameter.
Restrictions
You are prevented from putting the current commitment definition in a rollback-required state when:
- The resource handle is not valid.
- Commitment control is not active for the program making the request to put the commitment definition into a rollback required state.
- Commit or rollback processing is in progress for the current commitment definition.
In all other instances, the current commitment definition is put in a rollback-required state.
Error Messages
| Message ID | Error Message Text |
|---|---|
| CPF24B4 E | Severe error while addressing parameter list. |
| CPF3C90 E | Literal value cannot be changed. |
| CPF3CF1 E | Error code parameter not valid. |
| CPF8362 E | Request for commit resource is not valid; reason code &1. |
| CPF8367 E | Cannot perform commitment control operation. |
API introduced: V2R3
[ Back to top | Journal and Commit APIs | APIs by category ]