Resync control statement
Resync control statements are used by IMS DEDB Fast Recovery to process the in-doubt transactions in the sync point process.
If there are any transactions with in-doubt status at IMS, MVS™, or a system abnormal termination in a two-phase
commit process environment such as DBCTL, use the Resync control statements to either commit or
abort in the sync point process.
You can have IMS DEDB Fast Recovery prepare a skeleton of the Resync control statements for any in-doubt transactions that IMS DEDB Fast Recovery might detect during an IMS DEDB Fast Recovery job.
Related reading: See Preparing and using Resync control statements for further
information.
Subsections:
Rules for control statements
- A control statement is coded in the form of an 80-column punched-card image between column 1 and column 72.
- A control statement must be in a single line; it cannot be continued on succeeding lines.
- The two keyword parameters UOR= and ACT= must be specified.
- A keyword parameter can start in any column, provided the statement ends by the 72nd column.
- No blanks can be inserted between keywords, =, and parameters.
- Two keyword parameters must be separated by commas (,), and no blanks are allowed before or after a comma (,).
- At least one blank is needed after the last (second) parameter, if the parameter does not end in the 72nd column.
- Characters following blanks after the last keyword in a control statement are regarded as comments.
- You cannot specify any keyword parameter more than once in a control statement.
- Two or more control statements cannot be specified for one in-doubt transaction.
- A control statement can be specified only for an in-doubt transaction.
Control statement format
- UOR=recovery-token |ALL
-
- recovery-token
- Specifies the Recovery Token ID for an in-doubt transaction. The Recovery Token ID is 24
characters long. The first eight characters specify a subsystem ID. If the ID is shorter than 8
bytes, the ID starts from the left side and blank characters fill the remaining bytes. The next 16
characters specify 8-byte hexadecimal codes.
Example:
UOR=CICS1 A3E4F8B43EF0E902
- ALL
- Specifies that the process determined by the ACT= parameter is to be run for all in-doubt
transactions. If the UOR=recovery-token is also specified, the action is
superseded for the transaction.
Example:
UOR=ALL,ACT=COMMIT UOR=CICS1 A3E4F8B43EF0E902,ACT=ABORT
The transaction indicated by recovery token
CICS1 A3E4F8B43EF0E902
is aborted. All other in-doubt transactions are committed.
- ACT=COMMIT|ABORT
-
- COMMIT
- Specify COMMIT to commit the transaction.
- ABORT
- Specify ABORT to abort the transaction.
Example of a statement:
UOR=CICS1 A3E4F8B43EF0E902,ACT=COMMIT