When used in viewing mode, LINC/MON can display all logical records from a log file. Both log message records (transactions) and activity records (for example BOJ, EOJ) are accessible, provided they have been stored in the log file.
Each logical record is displayed in two parts.
Note: Log information can only be read when the block in which it is contained is written to the file. Thus you will not always be able to read the latest log information.
Log File Heading Information
The heading information for a log file logical record consists of seven items of basic identification information common to all record types, followed by specific items for each record type. Log records for system activities contain different information from log records for transactions and comment records. These different sets of information are shown in the following tables.
The following table lists the common heading items, with their equivalent log file property names.
| Monitor Name | Log File Property Name |
|---|---|
| Log Rec Length | Log Record Length |
| Pivot Nbr | Log Pivot |
| Log Day | Log Date |
| Log Time | Log Time |
| Log From | Source Description |
| Log Type | Log Record Type |
| Log Msg Length | Message Length |
The following table lists the heading items that are specifically displayed for system activities (for example, BOJ and EOJ).
| Monitor Name | Log File Property Name |
|---|---|
| Index 1 | Index 1 |
| St-Pivot | Start Pivot |
| Cu-Pivot | Current Pivot |
| Stn | Station Name |
| Program Name | Program Name |
| Output Type | Output Type |
| Mix Number | Mix Number |
| Status | Status |
| Action | Action |
| Abort Pivot | Abort Pivot |
| History | History |
| Integrity | Integrity |
| DMSREAD | Report reads |
| DMSWRITE | Report writes |
| Fnam | FNAM |
| File Equates | File Equates |
The following table lists the heading items that are specifically displayed for transaction log records.
| Monitor Name | Log File Property Name |
|---|---|
| S/Host | Source Host |
| S/Database | Source Database |
| S IP Pivot | Source Input Pivot |
| P/Host | Parent Host |
| P/Database | Parent Database |
| P/Requestor | Parent Requestor |
| P/IP Pivot | Parent Input Pivot |
| P/Auto Count | Auto Count |
| Subsystem | Subsystem Number |
| Ispec Name | Ispec |
| Msg Length | Length |
| Stn | Station Name |
| Msg Type | Message Type |
| Msg Requestor | Message Requestor |
| Reply Indicator | Reply Indicator |
| Error Indicator | Error Indicator |
| Recovery Indicator | Recovery Indicator |
| Station Type | Station Type |
| Msg Pivot | Message Pivot |
| DMS Read | Message Reads |
| DMS Write | Message Writes |
| Unique | Unique Number |
| Lang/New Lang | Language Number/New Language Number |
Comment records contain certain properties in common with transaction records, and additional information, as shown in the following table.
| Monitor Name | Log File Property Name |
|---|---|
| Comment Type | Comment Type |
| Comment Literal | Comment Literal |
Log Entry Text
If any text is associated with the log entry, then the text can be displayed on Page 2 by entering the DISPLAY command. Text is only associated with transaction log records, and is displayed in the same format as it was entered or sent to the screen. The heading information remains displayed on Page 1.
Examples of text are Ispec screens sent to a station by a COMSTP program, and Ispec screens sent to a COMSTP program from a station.