Trace record contents

Table 1 is the sample record broken into fields which are described after the table.

Table 1. Fields for Trace 22
RECORD 1
1	2	3	4	5	6	7	8
16.27.00.80	ID = 22	NPMADD		NPM		02933B90
RECORD 2
NCC=M SENT TO NODE2 (01) VIA LINE13
RECORD 3
CONNECTS NODE1 (01) AND NODE3 (01) REST= 200
RECORD 4
CES=90/054,015:39:34 STATUS=ACTIVE

The trace has the following format:

Record 1 has the same format as trace identifier 21.
Record 2:
- NCC - the type of network communication control (NCC) record traced. This value is always M for this record.
- RECV FROM or SENT TO - whether the record is coming from a node or going to a node.
- The name of the node.
- The member of the node connected with this node. The member is enclosed in parenthesis.
- VIA - indicates where this record originated from or was sent. Values for this field are:
  LINEnnnn
  
  The line to which JES2 sent this record or from which JES2 received this record.
  
  MLINEn
  
  The member of the MAS at this node to which this member sent the record or from which this member received the record.
  
  console identifier
  
  The console from which the operator entered the $ADD, $DEL, or $T CONNECT command.
Record 3:
- CONNECTS - contains the node names and member numbers on either side of the connection that this add record describes. The member number appears in parenthesis.
- REST - the resistance of the connection.
Record 4:
- CES - the connection event sequence as described for trace identifier 21. This field is not available if the connection is a static connection.
- STATUS - the current status of the connection this record represents. This value can either be ACTIVE or HELD.
Record 5:
- OLDCES - the connection event sequence associated with an existing NAT, which this record is replacing.
- OLDSTATUS - the status of this connection before this record was created. This value can be either ACTIVE, INACTIVE, HELD, or NONE.
Note: This record is not created when receiving a record or when the connection is a static connection.
Record 6:
FULLPATH determines whether JES2 updates the nodes attached table using the information from this record. This value can be either YES or NO.