Common Facilities for Distributed Transactions › Manual Recovery Input Control File

Manual Recovery Input Control File

A manual recovery input control file can be used to explicitly specify whether an InDoubt distributed transaction should be committed or backed out. Its use is optional, but if included in a utility's execution JCL, it will be used as input to the following recovery operations:

• EXTRACT JOURNAL (unless ALL is specified)
• FIX ARCHIVE
• MERGE ARCHIVE (if COMPLETE is specified)
• PRINT JOURNAL
• ROLLBACK
• ROLLFORWARD (unless ALL is specified)

The Input Control file only affects InDoubt transactions. It will have no effect on transactions that were in a Commit or BackOut state; or forgotten.

If the Input Control File is not used to commit or back out an InDoubt transaction, its state will remain in doubt. Its updates will still be applied or remain applied on the database and no journal records will be generated for that transaction. The updates will be complete and the database intact, that is, no broken pointers. Provided the database is not used and updated, the InDoubt transactions can still be backed out or formally committed in a later recovery job.

The file contains 80-byte records whose format is:

<DTrid><Action>

Where <Dtrid> is a 26-character display-format DTRID and <Action> is either COMMIT or BACKOUT. If more than one record specifies the same DTRID value, all but the last one are ignored.

The following example specifies that the transaction identified by DTRID SYSTEM74::01650C9509CE38A3 should be backed out:

SYSTEM74::01650C9509CE38A3 BACKOUT

If manual control input entries are used in a recovery operation that creates an output journal file (FIX ARCHIVE, EXTRACT JOURNAL, and MERGE ARCHIVE), then additional distributed transaction journal records will be written to the output file to complete the transaction in the specified way.

The following is a sample of the report generated by FIX ARCHIVE. It lists entries in the manual recovery input control file and shows the effect of those entries in its summary report. In this example, the distributed transaction identified by CICSCICS::B8AD18E5A9BF0F41 is committed by the generation of new DCOM and DFGT journal records.

Input Control Records:
   CICSCICS::B8AD18E5A9BE1300   BACKOUT

   CICSCICS::B8AD18E5A9BF0F41   COMMIT

   . . .
Incomplete Distributed Transactions At Stop Time:
     NODE     DTRID-BID                                   STATE   ACTION
**** SYSTEM74 CICSCICS::B8AD18E5A9BF0F41-016507A67C2E6D53 InDoubt Commit
*GEN SYSTEM74 DTRID-BID  CICSCICS::B8AD18E5A9BF0F41-016507A67C2E6D53       DCOM
              LOC_ID         28 PGM_IE CICSDML1
*GEN SYSTEM74 DTRID-BIT  CICSCICS::B8AD18E5A9BF0F41-016507A67C2E6D53       DFGT