DSNU1553I csect-name utility-name DETECTS THE FOLLOWING ACTIVE URS: INFLIGHT= inflight-count, INABORT= inabort-count, INDOUBT= indoubt-count, POSTPONED ABORT= postponed-count COMMITTED= committed-count ABORTED= aborted-count

Explanation

The LOGCSR phase of the utility is complete or was skipped because no active units of recovery (URs) existed at the recovery point. The counts of units of recovery in the message indicate the number of units of work that have execution states that require rollback action to be performed during this recovery process in order to ensure recovery consistency.

csect-name

The name of the control section that issued the message.

utility-name

The name of the utility: RECOVER or FLASHCOPY WITH CONSISTENCY.

inflight-count

The number of inflight units of recovery. These units of recovery neither completed phase one of the commit process nor began the process of backing out during the recovery point. The utility will roll back the changes during the LOGUNDO phase.

inabort-count

The number of in-abort units of recovery. These units of recovery were in the process of being backed out during recovery point. The utility will roll back the changes during the LOGUNDO phase.

indoubt-count

The number of indoubt units of recovery. These units of recovery were interrupted between phase one and phase two of the commit process. They are treated as in-abort units of recovery, and the utility will roll back the changes during the LOGUNDO phase.

postponed-count

The number of postponed in-abort units of recovery. The backout of these units of recovery was postponed in an earlier restart process, and they were not attended to prior to the recovery point. The utility will roll back the changes during the LOGUNDO phase.

committed-count

The number of committed units of recovery. These units of recovery will be backed out during RECOVER backout log apply processing.

aborted-count

The number of units of recovery that have completed abort processing. These units of recovery will be backed out during RECOVER backout log apply processing.

If an active unit of recovery exists during the recovery point, the message text is followed by a table that shows the status of units of recovery that were active during the recovery to point-in-time on the objects being recovered. This table helps to identify the following conditions:

• Units of recovery that have changes on the recovered objects which need to be rolled back during the LOGUNDO phase.
• The scope of log records that require processing in order to roll back the changes.

For each active unit of recovery in the table, the table contains one line that shows information about the unit of recovery:

MEM T CONID CORRID AUTHORIZATION ID PLAN S URID DAY TIME

MEM

The name of theDb2 member to which this unit of recovery belongs. In a data sharing environment, this field identifies theDb2 member. In a non-data sharing environment, this field is blank.

T

The connection type:

B

Batch: A batch program or user.

I

Internal: A system service being performed on a user's behalf.

S

Subsystem: Work that originated from an attached subsystem, either CICS® or IMS/VS.

CONID

The connection identifier for related units of recovery. Batch connections are not related to any other connection. Subsystem connections with the same identifier indicate units of recovery that originated from the same subsystem.

CORRID

The correlation identifier, which is unique within a subsystem connection. It relates a unit of recovery to a particular CICS or IMS/VS transaction.

AUTHORIZATION ID

Authorization identifier of the user for whom this unit of recovery was created.

PLAN

Name of the plan that is allocated to the unit of recovery.

S

Status of the unit of recovery during the recovery point:

D

Indoubt: The unit of recovery had completed the first phase of commit, but Db2 had not received the second phase instruction. Its change on the objects being recovered must be rolled back.

E

Committed: The unit of recovery has been committed.

F

Inflight: The unit of recovery had not completed the first phase of commit. Its change on the objects being recovered must be rolled back.

P

Postponed abort: The unit of recovery has not yet completed backout afterDb2 was last restarted. Its change on the objects being recovered must be rolled back.

URID

The unit of recovery identifier, which is the log RBA of the beginning of this unit of work.

DAY

The day that the unit of recovery was created, in the format ddd. It is approximately the time of the first SQL statement of the application or the first SQL statement following a commit point.

TIME

The time the unit of recovery was created, in the format hh:mm:ss. It is approximately the time of the first SQL statement of the application or the first SQL statement following a commit point.

This line is followed by one or more lines that show information about the objects that are included in the job and are modified by this unit of recovery. If the object is partitioned, one line represents each partition that is included in the job and is modified by this unit of recovery:

DBNAME SPACENAME DBID/PSID PART RBA

DBNAME

The name of the database to which the table space or index space belongs.

SPACENAME

The table space or index space that is changed by this unit of recovery.

DBID/PSID

The database and page set object identifiers (OBIDs).

PART

The partition number, if the table space or index space is partitioned.

RBA

In a non data-sharing environment, the RBA of the first update made by this unit of recovery on this object. In a data-sharing environment, the LRSN of the first update made by this unit of recovery on this object.