A description of the fields in the Formatted Record Dump follows:
Identifies the type of journal record (TIME, BGIN, AREA, COMT, ENDJ, ABRT, BFOR, or AFTR).
Specifies the node name of the central version on which the transaction executed. If the journal being analyzed was created in local mode, this field will contain *local*.
Identifies the UTC date on which the journal record was written to the journal file (TIME record only) or placed into the journal buffer (all other records). The date is given in the same form as LOCAL DATE.
Identifies the UTC time at which the journal record was written to the journal file (TIME record only) or placed into the journal buffer (all other records). The time is given in the same form as LOCAL TIME.
Identifies the sequence number assigned to the journal record.
Identifies the unique identifier (LID) assigned to the transaction for which the journal record was written.
(BFOR and AFTR records only) Identifies the function code of the navigational DML verb issued by an application program or the SQL or LRF runtime processor.
(AREA, BFOR and AFTR records only) Identifies the page group associated with the area in which the user record is stored.
(BGIN, COMT, ENDJ, and ABRT records only) Identifies the name of the program with which the transaction is associated.
Identifies the date on which the journal record was either written to the journal file (TIME record only) or placed into the journal buffer (BGIN, COMT, ENDJ, and ABRT records only). The date is given in the form mm/dd/yy, where mm is the month, dd is the day, and yy is the last two digits of the year.
Identifies the time at which the journal record was either written to the journal file (TIME record only) or placed into the journal buffer (BGIN, COMT, ENDJ, and ABRT records only). The time is given in the form hhmmssht, where hh is hours on a 24-hour clock, mm is minutes, ss is seconds, and ht is hundredths of a second.
(BGIN, COMT, ENDJ, and ABRT records only) Identifies the number of open transactions after the journal record was written to the journal file.
(BGIN, COMT, ENDJ, and ABRT records only) Is the identifier consisting of a 4-character name that designates the originating interface (for example, BATC, DBDC, or CICS) and a numeric identifier assigned to the transaction by the interface.
The user ID of the user signed on who executed the application causing the BGIN to be written.
The external identity of the user signed on to web based application. This field and title will not be displayed if the external identity is equal to spaces.
(COMT, ENDJ, and ABRT records only) Indicates the number of calls to IDMSDBMS issued by the transaction. Execution of each navigational DML request involves one call; execution of each LRF or SQL request typically involves multiple calls. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of pages requested by the transaction (including pages found in a buffer). A page request does not result in a page read if the page is in the buffer pool. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of pages physically read from disk. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of pages physically written to disk. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of database records requested by IDMSDBMS for the transaction. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of records updated by the transaction. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of times the current-of-transaction field in the subschema control block for the transaction was updated. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of CALC records stored on their target page. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of CALC records not stored on their target page. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of VIA and/or DIRECT records stored on their target page. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of VIA and/or DIRECT records not stored on their target page. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of noncontiguous segments stored for variable-length records. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Identifies the number of records relocated from their home page. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of locks acquired by the transaction. On COMT checkpoints, this value is a running total for the transaction.
(COMT, ENDJ, and ABRT records only) Indicates the number of shared locks held by the transaction at the time the checkpoint record was written.
(COMT, ENDJ, and ABRT records only) Indicates the number of exclusive locks held by the transaction at the time the checkpoint record was written.
(AREA records only) Identifies the name of the area for which the checkpoint record was written.
(AREA records only) Identifies the page number of the first page in the area.
(AREA records only) Identifies the page number of the last page in the area.
(AREA records only) Identifies the mode in which the transaction accessed the area (SHARED, PROTECTED, or EXCLUSIVE).
(AREA records only) Identifies the mode in which the transaction opened the area (RETRIEVAL or UPDATE).
(BFOR and AFTR records only) Indicates that the user record is a CA IDMS/DB database record. For native VSAM records, this field reads THIS IS A NATIVE VSAM RECORD.
(BFOR and AFTR records only) Specifies the location of the user record occurrence relative to the beginning of the database page (given as a decimal offset).
(BFOR and AFTR records only) Specifies the length in bytes of the prefix portion of the user record.
(BFOR and AFTR records only) Indicates the record id of the user record. An asterisk following the record id indicates that this is a logically deleted record.
(BFOR and AFTR records only) Specifies the length in bytes of the entire user record (prefix and data portion) as found in the database record line index.
(BFOR and AFTR records only) Specifies the function code of the navigational DML verb issued by an application program or the SQL or LRF runtime processor.
(BFOR and AFTR records only) Specifies the database key of the user record occurrence in hexadecimal format.
(BFOR and AFTR records only) Specifies the page and line number, in decimal format, of the database key of the user record occurrence.
(BFOR and AFTR records only) Specifies a trace entry indicating the IDMSDBMS routine that issued the database call (for CA internal use only).
Identifies the contents of the user record in decimal (display) format.
Identifies the contents of the user record in hexadecimal format.
(Not on sample report) Indicates that the journal entry is a continuation of the previous BFOR or AFTR image for the transaction. The number is the displacement of this portion of the record image relative to the entire image.
(DIND, DCOM, DBAK, DPND, and DFGT records only) Identifies the distributed transaction identifier (DTRID) and the branch identifier (BID) of the top-level branch of the distributed transaction for which the journal record was written.
|
Copyright © 2013 CA.
All rights reserved.
|
|