Previous Topic: Grand SummaryNext Topic: CHRONOLOGICAL EVENT Report Fields

System Output › Audit Report › CHRONOLOGICAL EVENT Report

CHRONOLOGICAL EVENT Report

The CHRONOLOGICAL EVENT Report outlines all recorded activity in a timewise sequence. The user is presented a detailed view of run unit events in contrast to the ACTIVITY Report which summarizes run unit activity during user-defined time intervals (for example, hourly). Although much of the information contained in the CHRONOLOGICAL EVENT report is identical to the PROGRAM Reports, the information is reported in a strictly chronological order.

Each reported event includes the current quiesce level which indicates the degree of total run unit concurrency.

Note: In CA IDMS environments, the quiesce level can be non-zero although no user tasks are active because all active RHDCRUAL system run units are reflected in the quiesce level count. Events for the RHDCRUAL program will not be reported unless RHDCRUAL=YES was specified on the PROCESS parameter card when the journal extract records were produced.

The CHRONOLOGICAL EVENT Report is normally requested on special demand only. For example, when unusual activity is recorded in the ACTIVITY Report, you can use the CHRONOLOGICAL EVENT Report to acquire a detailed view of such activity by specifying the appropriate time intervals on the REPORT parameter cards.

If a PROGRAM Report shows run units with excessively long durations, or a large number of program aborts, the cause may be resource contention among concurrently executing run units. In which case, the CHRONOLOGICAL EVENT Report of the time period in question will reveal the contending programs, and the ABORT COINCIDENCE Report will reaffirm coincidence of such programs.

If you are required to manually recover part of the CA IDMS database, the following functions are generally performed:

  1. A quiesce point must be determined in order to limit the extent of the recovery by the ROLLBACK or the ROLLFORWARD utilities.
  2. The ROLLFORWARD utility is executed with the PRINT parameter to list the before and after images.
  3. You search through a stack of ROLLFORWARD image reports to establish a quiesce point on which to synchronize the recovery.
  4. The ROLLBACK or ROLLFORWARD utility is executed with the appropriate DATE and TIME parameters.

Note: The CHRONOLOGICAL EVENT Report offers you a reasonable alternative to steps 2 and 3. A significant savings in computer resources, paper, and research time can be realized if this report is used to establish the recovery quiesce point. The concise format of the CHRONOLOGICAL EVENT Report eases your burden in this most unenviable task.