Considerations for COMMIT CONTINUE-SYNC CONTINUE-ABORT CONTINUE
A 16-byte recovery token is used to uniquely identify a unit of recovery to IMS. This token is supplied by the CCTL.
The commit, sync, and abort continue behavior is used by the CCTL when multiple Units Of Recovery (UOR) are being performed within a single Unit Of Work (UOW). For CCTLs that employ COMMIT CONTINUE, SYNC CONTINUE, and ABORT CONTINUE behavior, the following recovery token information is strongly recommended by IMS. For commit and resolve indoubt processing, IMS passes the recovery token to identify the unit of work for which the requested action is to be taken.
The recovery token is constructed as shown in the following table:
| CCTL-id | binary value | commit_number |
|---|---|---|
| 8 | 5 | 3 |
- CCTL-id
- Is the CCTL ID (1 to 8 characters).
- binary value
- Is a 5-byte binary origin application value assigned by the CCTL to the application when it is scheduled. The concatenation of CCTL and binary value (CCTL-id || binary value) is unique across the entire Unit of Work.
- commit_number
- Is a 3-byte binary commit number. The commit number should be initialized to binary zeroes when the application is scheduled and then incremented after each commit is processed for the application. The concatenation of CCTL-id, binary value, and commit number (CCTL-id || binary value || commit number) is unique across the Unit of Recovery.
The CCTL must ensure that the passed recovery token is unique. IMS only validates that the recovery token is unique, it does not verify the structure of the token.
The installation uses the /DISPLAY CCTL command to determine what units of work are in INDOUBT status in IMS. The installation can use the /CHANGE command (when necessary) to manually delete indoubt units of work in IMS. The /CHANGE command (when necessary) to manually delete INDOUBT units of work IMS. The /CHANGE command only affects unit of work status in IMS. There is no communication with the CCTL.