Print Suspect/Recovery Records

This section describes how to print suspect records and recovery records.

Suspect Records

Recovery information relating to incomplete transactions is stored in the suspect transaction portion of the transaction manager’s recovery file in certain situations. For example:

  • during a forced restart of the transaction manager; or

  • when an administrator forcibly terminates a distributed transaction using Online Services.

In these cases, transactions are lost to the transaction manager and therefore cannot be completed normally. Transaction integrity may be compromised. For example, a branch of a distributed transaction on one database might be committed while another branch is backed out.

Each record represents a suspect transaction. The print program T1STJP can be used to:

  • identify the suspect transactions; and

  • determine their status when they were last under the control of the transaction manager.

Recovery Records

Recovery information relating to all prepared distributed transactions or branches which are incomplete are stored in the recovery portion of the transaction manager’s recovery file.

The print program T1STJP can also be used to print these records.

Running the Print program T1STJP

The sample job member ATMSPRNT, which is located in the installation JOBS library, can be used to run the print program T1STJP. Before executing this job, modify the ADARUN parameters and Natural parameters according to the requirements of your installation.

This utility requires that the transaction manager is active. Set up the job step as if it were using Adabas Transaction Manager to coordinate its transactions. That is, suitable client runtime controls must be defined, the job step must use an ADALNK module which has the Adabas System Coordinator stub linked in, and the Adabas Transaction Manager library must be available to the job step.

Program execution is controlled by parameters read from the CMSYNIN input. Two parameters are expected:

Parameter Description
Record ID The identity of the records for which data will be read. Possible values are

  • STJ: for suspect transaction records

  • PRR: for recovery records

Note:
The contents of the recovery records are likely to change frequently and rapidly. Thus, the report has only limited use in determining the status of a transaction that cannot be brought to completion for some reason. Online Services can also be used to display suspect transaction records or recovery records online.

Note:
The batch hardcopy report from the print program does not include an interpretation of a transaction’s status codes; for these, you need to use Online Services.

TM ID The node ID of the transaction manager. If this parameter is omitted, it will default to the node ID of the transaction manager that is associated with the Adabas System Coordinator Group specified in the job’s client runtime controls.

Suspect transaction and recovery records are not reported in any particular sequence. The field marked "Last act" in the report provides an indication of the time when the record was stored.