Specifying LOGPRINT=DETAIL in an RXX Analysis Report generates the following information, which continues for as many pages as necessary (not all pages are shown in this sample).
(CONTINUED) Date: mm/dd/ccyy Time: hh.mm.ss Page: 2 LOGPRINT DETAIL REPORT CMD TBL DBID URI BLOCK L# TSN JOB NAME R-UNIT MP USER ID AREA MONITOR INFO INPUT RECORD FPR RXX }Œ DATE TIME CLOCK SEC.USER MOVE TO LRID PREV LRSN LBSN TASK STATUS RECL DATA } ADDIT MSG 15 00000401 00000003 00 00001A18 DLV1C131 17,003 SQLDG001 MSG SCFDG001JVM00037 38 mm/dd/ccyy hh.mm.ss B6F7A1DA0D189903 username 00000000 00000608 00000607 00000008 00000006 1 B 0175 6C3B ADDIT MSG 15 00000402 00000003 00 00001A18 DLV1C131 17,003 SQLDG001 MSG SCFDG001JVM00037 39 mm/dd/ccyy hh.mm.ss B6F7A1DA0D1D7363 username 00000000 00000609 00000608 00000009 00000006 1 B 0175 6C3B ADDIT MSG 15 00000403 00000003 00 00001A18 DLV1C131 17,003 SQLDG001 MSG SCFDG001JVM00037 40 mm/dd/ccyy hh.mm.ss B6F7A1DA0D2152A3 username 00000000 0000060A 00000609 0000000A 00000006 1 B 0175 6C3B . . . DELET MSG 15 00000401 00000003 00 00001A18 DLV1C131 17,003 SQLDG001 MSG SCFDG001JVM00037 83 mm/dd/ccyy hh.mm.ss B6F7A1DB93E43B61 username 00000000 00000635 00000634 00000035 00000006 1 B 015E 6C3B DELET MSG 15 00000402 00000003 00 00001A18 DLV1C131 17,003 SQLDG001 MSG SCFDG001JVM00037 84 mm/dd/ccyy hh.mm.ss B6F7A1DB93E7C541 username 00000000 00000636 00000635 00000036 00000006 1 B 015E 6C3B . . .
Log Detail Report Headings
CA Datacom/DB record-at-a-time command. In addition to record-at-a-time commands such as ADDIT, UPDAT, DELET, and COMIT, commands used internally can also appear in the report. Internal commands that support restart and recovery requirements are not normally documented, but because they might be seen in this report, a summary description follows.
CA Datacom/DB table name in the Request Area. Blank for records without table names. For 'CYCLE' (the internal command), the table name contains 'STA' (for start of a cycle) and 'END' (for end of a cycle). A cycle refers to a sequential group of log blocks copied from the LXX to the RXX during one spill.
Database ID. Blank for records without database ID's. Printed as a decimal number.
Unique Row Indentifier. Blank for records without a URI number. Printed in hexadecimal format. Contains the literal 'NON-URI ' for areas not loaded as URI.
Data area block number. Blank for records without a data block. Printed in hexadecimal format.
Data area block record number. Blank for records without a data block number. Contains '00' for records with a data block, if the area is loaded with the URI option. Printed in hexadecimal format.
Transaction Sequence Number. Blank for records not part of a transaction. Printed in hexadecimal format.
Job name.
Run unit number.
Blank if not running r10 or later as a MUFplex. Otherwise contains a MUFplex number of which Multi-User Facility logged this log record.
User ID. First 8 characters of the 32-byte user ID passed on the request.
Data area name containing row.
Monitor information, if this request was made through the CA Datacom CICS Services or the CA Datacom Server.
Number of this input log record.
Full Parent name, if this table is partitioned, or a partition.
To indicate this is a recovery file. In z/OS, can contain LXX.
Date the log record was added. Printed in the form mm/dd/ccyy.
Time the log record was added. Printed in the form HH.MM.SS.
Result of a hardware STCK (store clock) instruction at the time the log record was added.
Security user requesting maintenance.
Block number to where an update moved a record. Printed in hexadecimal format.
Log record ID. The physical block number within the LXX where the log record was added in the first three bytes. The last byte is a sequential number within this log block, such that the first record is 1, and so forth. This field is provided to assist Technical Support, should the need arise. Printed in hexadecimal format.
Previous log record ID. Log records for a transaction are chained in reverse back to a previous one of low values.
Log record sequence number. An internal number used by CA Datacom/DB in support of the logging features. Incremented by one as log records are added, can restart at 1, based upon internal DB requirements. This field is provided to assist Technical Support, should the need arise. The number is printed in hexadecimal.
Log block sequence number. An internal number used by Technical Support of the logging features. Incremented by one as log blocks are used. Can start at many numbers and can restart as required internally by CA Datacom/DB. This field is provided to assist Technical Support, should the need arise. The number is printed in hexadecimal.
Number of the task area which was used when this log record was generated.
Status of log record. Can contain one or more letters. A blank ends the status. The possible letters are:
A Specifies that the transaction was aborted and is to be rolled back.
B Specifies that this record is subject to transaction backout.
F Specifies that the first log record after transaction was force spilled.
M Specifies an update command caused the record to move.
U Specifies that this request was rolled back.
V Specifies a virtual table.
1 Specifies the first logged record for this transaction.
X Specifies this log record is part of an ADDIT/DELET set, done in support of a partitioned table update that changed the partition in which the row is stored.
These letters may be in any order. They are present only when required/desired to support the CA Datacom/DB facilities. They are provided for Technical Support and are not always present even though the description would indicate that it should be present.
Size of the log record. It is printed in hexadecimal. This field is provided to assist Technical Support, should the need arise.
Size of the log data in this log block. It is printed in hexadecimal. This field is provided to assist Technical Support, should the need arise.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|