list mst
Issue 4 May 2002
8-183
555-233-123
Vector Event Trace (D92 Only)
Message type:
0x11
Message format:
Events are defined in $BASEPJ/hdrs/evnt_defs.h. Events based on the call_p will
have the following auxiliary data:
Events based on the grp_m will have the following auxiliary data:
IMT (D92)
The messages described in this section cannot be controlled directly through any
of the MST screens. They are enabled/disabled through TCM but their output
goes to the MST buffer. See [IMT] for details on these messages.
A read-only field in the “change mst” screen, “Other Tracing?”, alerts the user that
one or more of these types of messages is enabled.
0x21 - IMT proc_errs
Message format:
Message[1-4]
= cid (defined in $BASEPJ/hdrs/capro.h)
Message[5-6]
= event
Message[7+]
= auxiliary data (based on event)
Message[7-8]
= vector number
Message[9-10]
= step number
Message[7-10]
= hunt group number
Message[1-4]
= process number(lname)
Message[5-8]
= sequence number (defined in *.p/hdrs/main_err.h, for example:
$BASEPJ/gmtce.ss/hmm.p/hdrs/main_err.h)
Message[9-12]
= data 1
Message[13-17]
= data 2
Summary of Contents for Definity SI
Page 1: ...0DLQWHQDQFH IRU YD D 1 7 6HUYHU 6 Volumes 1 2 and 3 555 233 123 Issue 4 May 2002...
Page 62: ...Maintenance Architecture 555 233 123 1 26 Issue 4 May 2002...
Page 92: ...Management Terminals 555 233 123 3 26 Issue 4 May 2002...
Page 204: ...Routine Maintenance Procedures 555 233 123 5 100 Issue 4 May 2002...
Page 250: ...LED Interpretation 555 233 123 7 10 Issue 4 May 2002...
Page 2804: ...Maintenance Object Repair Procedures 555 233 123 10 2018 Issue 4 May 2002...