As the name implies, the Read Event Log File (RE) command displays the latest 256 entries in the Event Log file associated with a particular LANIC card.
Note
An event log file associated with a local or remote node may only be read locally, that is, from the disk"based File Server Node on which it resides. Reading an event log file over the LAN is not allowed, and no transmission over the LAN occurs when using this command.
The syntax for this command is:
RE[,FileAddress]where,FileAddress This parameter is the Station Address of the node whose event log file is to be read. It is entered as 6 pairs of hexadecimal digits separated by hyphens. If defaulted, the address used is the Station Address of the LANIC card with the lowest LU value installed.
When this command is entered, Node Manager software retrieves the applicable file and displays it in the following form:
| TIME | DATE | ERR# | LU | DA | SA | LEN | DSAP | SSAP | CTRL |
|
|
|
|
|
|
|
|
|
|
where,
| Time | : indicates the time of the entry, AM and PM. |
| Date | : indicates the day, month, and year of the entry. |
| ERR# | : Two hexadecimal digits representing a packet error status byte. (See Figure 5"1.) |
LU | : The Logical Unit number (decimal) of the LANIC card through which |
| the logged packet was received. |
DA | : The Destination Address of the logged packet, 12 hexadecimal digits. |
SA | : The Source Address of the logged packet, 12 hexadecimal digits. |
| LEN | : The length of the packet in bytes, specified as 4 hexadecimal digits. |
DSAP | : The DSAP of the logged packet, 2 hexadecimal digits. |
| SSAP | : The SSAP of the logged packet, 2 hexadecimal digits. |
| CTRL | : The logged packet's Control field value, 2 hexadecimal digits. (See Table 5"10.) |
The ERR# value may be decoded to binary, and with Figure 5"1, the cause of packet error may be deciphered.