Common Facilities for Distributed Transactions › Reporting on Distributed Transactions

Reporting on Distributed Transactions

A distributed transaction journal record consists of a fixed portion and up to three variable arrays of data. The fixed portion contains the distributed transaction identifier (DTRID) and a local branch ID (BID), which identifies an individual branch of the distributed transaction. The fixed portion can be followed by any of the following:

• A list of local transaction identifiers (LIDs), one for each branch of the transaction that made local database changes
• A list of external transaction identifiers if the transaction is known externally by another identifier, such as an XA XID or an RRS URID
• A list of interests that other resource or transaction managers have in the distributed transaction

The recovery utilities report some or all of the above information in their detailed report and list distributed transactions that were incomplete at stop time in their summary report.

The following example shows the output that is produced by PRINT JOURNAL REPORT FULL when it encounters a typical DCOM record. If the REPORT TERSE option is specified, neither external transaction identifiers nor resource manager interests are included. Other recovery utilities show similar information.

NODE SYSTEM74 DTRID-BID   SYSTEM74::01650C9509CE38A3-01650C90A4CDA0BD        DCOM
  LOC_ID    10016  PGM_ID PROCDISM
  RRS URID  B8DEBCA57E84B6700000000D01020000                                 *...v=d..........                *
  RM NAME   SYSTEM74::RRS_RMI   TYPE RRS    ROLE SDSRM STATE InDoubt       FLG1/2 0001 EXITS 40 0034000000000000
            D9D9E240C24040404040404040404040B8DEBCA57E84B670000000D01020000  *RRS b             ...v=d........*
            18C1E3D94BC2F8F9F0F9F7F8F6C1F2C1F8C1C1F4F04BC9C2D4               *.ATR.B8909786A2A8AA40.IBM       *
  RM NAME   SYSTEM73::DSI_CLI   TYPE IDMS   ROLE CRM   STATE InDoubt       FLG1/2 0000 EXITS 76 0000000000000000
            E2E8E2E3C5D4F7F301650C90A4CDA9040000000080000001650C2E949172E101 *SYSTEM73....u.z............mj...*
            650c9509cE38A380000000000000000E2E8E2E3C5D4F7F303D9C51D340C4C3   *..n..t..........SYSTEM.73REAL DC*
            400000000000000D5C4E2E3C5D4F7F3000000000000000000000000          * .........NDSYSTEM73............*
            00000000                                                         *....

A brief description of the report's contents follows. For an in-depth discussion of the meaning of this report, see CA IDMS Database Administration Guide.

• Node SYSTEM74 identifies the name of the system that produced the journal entry, in this case, SYSTEM74.
  • DTRID-BID SYSTEM74::01650C9509CE38A3-01650C90A4CDA0BD identifies the DTRID and the BID of the top-level branch of the distributed transaction for which the DCOM record was written. The DTRID is SYSTEM74::01650C9509CE38A3 and the BID is 01650C90A4CDA0BD.
  • DCOM is the type of distributed transaction journal record that is being reported.
• LOC_ID 10016 identifies the work done by a local transaction branch that is included in the distributed transaction. In this case, the local identifier is 10016.
  • PGM_ID PROCDISM identifies the name of the application program that started the local transaction branch. In this case, the program is PROCDISM.
• RRS URID B8DEBCA57E84B6700000000D01020000 identifies the transaction, as it is known externally.
• RM NAME SYSTEM74::RRS_RMI identifies a resource manager that has registered an interest in the distributed transaction. In this case, the resource manager is RRS.
  • TYPE RRS indicates that the RM type is RRS.
  • ROLE SDSRM indicates that this interest is the controlling interest for the transaction, and therefore RRS is the transaction's coordinator.
  • STATE InDoubt indicates the interest's state. In this case, the interest is in an InDoubt state.
  • FLG1/2 0001 displays flags that are used to restart the transaction following a system failure.
  • EXITS 40 0034000000000000 shows the exits that have been registered by the resource manager and the responses returned by the exits that have already been called during the life of the transaction.
  • D9D9E240C2... shows the data (in hex and character format) that the resource manager wishes preserved should it be necessary to restart the transaction following a system failure. This information will vary depending on the resource manager that registered the interest.
• RM NAME SYSTEM73::DSI_CLI identifies a resource manager that has registered an interest in the distributed transaction. In this case, the resource manager is a CA IDMS system named SYSTEM73.
  • TYPE IDMS indicates the type of the resource manager.
  • ROLE CRM indicates that this interest is not a controlling interest for the transaction. Therefore, the associated resource manager (SYSTEM73) is a participant in the transaction.
  • FLG1/2 0000 displays flags that are used to restart the transaction following a system failure.
  • EXITS 76 0000000000000000 shows the exits that have been registered by the resource manager and the responses returned by the exits that have already been called during the life of the transaction.
  • E2E8E2E3C5... shows the date (in hex and character format) that the resource manager wishes to have preserved if it is necessary to restart the transaction following a system failure. This information will vary depending on the resource manager that registered the interest.