System Output › Audit Report › CHRONOLOGICAL EVENT Report › CHRONOLOGICAL EVENT Report Fields

CHRONOLOGICAL EVENT Report Fields

The following is a description of the various fields that make up the CHRONOLOGICAL EVENT Report.

EVENT

• TIME—Time recorded for each event.
• TYPE—BGIN, COMT, ENDJ, or ABRT. ABRT's are further highlighted by "- >" next to the event time.
• DURATION—Run unit duration reported in seconds, for ENDJ and ABRT events.

IDENT

• RUN UNIT—Run unit numeric ID.
• PROGRAM—Application program name and processing type (ONL or BTC).

QUIESCE LVL/USER/EXT ID—Quiesce level at the time of the event, reported as a number of X's. A fully quiesce system is represented by a zero. If the number of concurrent run units exceeds 20, that number is reported.

User ID reported on the BGIN checkpoint journal record. If the report is run against journal files created prior to r16 SP4 (the user ID is not present in the BGIN), the report displays USER ID NOT CAPTURED. If the report is run against journal files created after r16 SP4, but the user does not sign on, the user ID field in the BGIN is filled with spaces, and the report displays NO USER SIGNON.

Ext ID reported on the BGIN checkpoint journal record. IF the report is run against journal files created before IDMS Server r16.1 or before IDMS r16 SP6 (the external ID is not present in the BGIN), the report displays spaces. If the report is run against journal files created after IDMS Server r16.1 or after IDMS r16 SP6 and the external ID field is not populated, the report displays spaces.

Note: Whether a run-unit affects the quiesce level is determined by the manner that an area is READY. Since the READY may occur sometime after the BIND RUNUNIT, the quiesce level may sometime appear to change erratically.

The following example shows the CHRONOLOGICAL EVENT Report:

 ID                   RELEASE                         CA IDMS JOURNAL ANALYZER                 DATE             TIME        PAGE
                      Rnn.nn                         CHRONOLOGICAL EVENT REPORT             mm/dd/yy          hh:mm:ss         2

 ---------EVENT---------  --------IDENT--------  ---QUIESCE LVL/USER/EXT ID---  ---------PAGES---------  ------------LOCKS----------
 TIME     TYPE  DURATION  RUN UNIT      PROGRAM                        READ       WRITTEN  REQUESTED  REQUESTED   SELECT   UPDATE

 mm/dd/yy

 hh:mm START*************************************                     *************************************************END hh:mm

 hh:mm:ss BGIN               27414 FILLJNL1 BTC  X
                                                 USER01
                                                 CUSTOMER99
                                                                      SHR  UPD EMP-DEMO-REGION   LOW=       75,001  HIGH=   75,050
                                                                        SHR UPD ORG-DEMO-REGION   LOW=       75,151  HIGH=   75,175
 hh:mm:ss COMT               27414 FILLJNL1 BTC  X                        19           15      65         94         4       38
 hh:mm:ss ENDJ     hh:mm     27414 FILLJNL1 BTC  0                         0            8      32         67         0       30
 hh:mm:ss BGIN               27415 FILLJNL2 BTC  X
                                                 USER01
                                                                      SHR  UPD ORG-DEMO-REGION   LOW=       75,151  HIGH=   75,175

PAGES

• READ—Number of pages read from the database.
• WRITTEN—Number of pages written to the database.
• REQUESTED—Number of pages requested that were satisfied by a read of a database page or an access into the buffer pool.

LOCKS

• REQUESTED—Number of record locks requested by the run (recovery) unit, automatically or upon request.
• SELECT—Number of select (shared) locks maintained by the run (recovery) unit.
• UPDATE—Number of update (exclusive) locks held at the termination of the run (recovery) unit.

TIME LINE—A line of asterisks is printed for each hour of activity.

AREAS OPENED—Each area readied by the run unit is listed with the following information: usage mode, area name, and page range.

NO EVENTS POSTED—A line of asterisks is printed for each hour when no events were posted although at least one run unit was active.

NO ACTIVITY—A line of asterisks is printed for each hour when no run units were active.

Note: The CHRONOLOGICAL EVENT Report manipulates data on the Archive Journal file to show PAGES and LOCKS in relation to the work accomplished by the 'recovery unit'. A recovery unit is that segment of CA IDMS activity bounded by BIND, COMMIT, ROLLBACK, and/or FINISH. In this context, a run unit may be one or several recovery units. As maintained by CA IDMS, these values are incremented throughout the run unit and are only reset to zero at the end of the run unit. UPDATE LOCKS is the exception. It is reset to zero at the end of each recovery unit. Therefore it is reported without manipulation.