Information in the LUOW Detail report
These sections are listed in order by LUOW number:
- The first line of the section identifies the LUOW.
- The second line contains column headings for the information about log records that have been associated with the LUOW.
- The third line (and each subsequent line) provides information about a specific log record. Log records are listed in order by the record timestamp.
If input log sources contained log records from a single version of IMS, the heading of the LUOW Detail report notes the IMS version as R=n (n is the version number). If input log sources contained log records from multiple versions of IMS, the LUOW Detail report contains a column indicating the IMS version that created each individual record.
The following table lists and describes the fields on the LUOW Detail report.
Field | Description |
|---|---|
LUOW | The LUOW field contains the LUOW number that Log Analyzer assigned arbitrarily during the analysis job. For more information, see Creating-LUOWs. LUOWs on the report are listed in sequence by the value in the LUOW field. |
Log recs | The Log recs field contains the count of log records that Log Analyzer associated with the LUOW. |
Rec tkns | The Rec tkns field contains the count of recovery tokens that Log Analyzer found in log records that are associated with the LUOW. |
UOW-1 | The UOW-1 field contains the UOW-1 number that Log Analyzer obtained or created and assigned to this LUOW. For more information, see LUOW-numbers-and-UOW-1-numbers. |
Code | The Code field contains the two-character log record type code and (if applicable) the two-character log record subtype code that identify the type and subtype of the log record. For a list of log record type codes, see IMS-log-record-types. |
Type | The Type field describes the log record type. For a list of log record types, see IMS-log-record-types. |
R | If input log sources contained log records from multiple versions of IMS, the R field contains the IMS version that created the log record. To make room for this column, the three high-order (left-most) digits of the Log Sequence Num field are omitted. |
Log Seq Num | The Log Seq Num field contains the log sequence number (in hexadecimal format) that IMS assigned to the log record. |
Time | The Time field contains the timestamp that IMS has assigned to the log record. Records for the LUOW are listed in sequence by the values in the Time field. |
Variable | The Variable field can contain relevant information that Log Analyzer 'snipped' (copied) from within the log record. This field can extend to multiple lines, depending on the type of record. For more information about variable data, see Variable-data-snipped-from-log-records. If this field contains the following string, no variable data was considered to be important to snip for this type of log record: (no formatted data) Log Analyzer can include other notations in parentheses, such as (start unit-of-recovery). These notations indicate comments that Log Analyzer has added to help you interpret the flow of events. If Log Analyzer is reporting FA log record databases that were read during the LUOW, this field includes the following notations:
A notation of OTHERS in the readDBs list indicates that read-only activity was incompletely recorded because the region exceeded MainView’s defined maximum number of database trailers. MainView recorded the excess activity in an overflow trailer named OTHERS. To prevent this condition, increase the values of the MainView DBTS and DBTS4BMP parameters. |
DATA ==>> | For type 01 records and type 03 records, the DATA ==>> field displays snipped data that Log Analyzer obtains if you have specified the LUOWDETAILDATA keyword. When you specify this keyword, Log Analyzer copies data from the first segment of the record, beginning at the specified offset within the record and continuing to the specified length. The offset is relative to 0. For more information, see LUOWDETAILDATA-keyword. If the specified offset is past the end of the record, the report indicates the error by displaying the following string instead of snipped data: */*/* no data */*/* If the specified offset is before the end of the record but the specified length is past the end of the record, the report displays as much of the snipped data as possible and indicates the condition by placing an asterisk within the field label as follows: DATA*==>> |