Contents | Index | Previous | Next

TTY Output Format of Events

TTY event output can be formatted or unformatted. Formatted output is also called fancy format. Output format is configurable in LD 117 using the CHG FMT _OUTPUT command.

Fancy Format Output

Formatted output appears in the following template:

<severity> <report id> <date> <time> <prim_seq_no> <cp_id> <cp_ad>
DESCTXT: <descriptive text>
OPRDATA: <operator data>
EXPDATA: <expert data>

Field
Description
<severity>
"***" (critical); "**" (major); "*" (minor); " " (blank for info)
<report id>
The report id consists of an event category (e.g. BUG, ERR, etc.) and an event number (1200, 230, etc.). It is padded with blanks at the end to ensure it is 9 characters long (4 characters max. for category and 5 digits max. for number). Examples of report ids are: ERR230, ACD3560, and BUG30.
<date>
DD/MM/YY
<time>
HH:MM:SS
<prim_seq_no>
Primary sequence number of the event (length of 5 digits)
<cp_id>
The Component ID is a 15 character string which indicates the id of the subsystem generating the alarm
<cp_ad>
The Component address is a 15 character string which indicates the address of the subsystem generating the event
<descriptive text>
This is an optional string which describes an event
<operator data>
This is an optional field which holds a 160 character string containing extra text or data to assist the operator in clearing a fault. This field contains any data output with a filtered SL-1 alarm (e.g. loop number, TN, etc.)
<expert data>
This is an optional variable length character string which contains extra text or data for a system expert or designer.
The following are samples of fancy format output:

       VAS0010 15/12/92 12:06:11 00347 VMBA     VAS 5