196.5 Technical Clarification

The following standard trace points and their corresponding trace object types are defined for message tracing:

OS calls ON_P_SEND_MESSAGE_I, ON_P_SEND_MESSAGE_N, ON_P_SEND_MESSAGE_P, ON_P_SEND_MSG_I_NO_FREE, ON_P_SEND_MSG_N_NO_FREE, ON_P_SEND_MSG_P_NO_FREE with object type SD

OS calls ON_P_RECEIVE_MESSAGE and ON_P_ACCEPT_MESSAGE, with object type RCV

LAN trace point in the trace interface procedure in LAN subsystem.This LAN trace interface procedure is called by the various LAN layers with corresponding object types: ETHRV, ETHSD, TCP, TPI, IPDSD, IPDRV

CP trace point in the trace interface procedure in call processing, with object type CP (used in StandardTracer and AutoTracer)

PP trace point in the trace interface procedure in peripheral processing, with object type PP (used in StandardTracer and AutoTracer)

FLAGTR-tracepoint in trace interface procedure of CP and PP

Monitorpoints for the Realtime Diagnostic System (RDS) in CP and PP

Note

Since the call processing complexes DH (device handler) and PP (peripheral processor) are produced as a single memory-resident subsystem, only the PP has a trace point. This point is used to trace both the DH messages and the PP messages. It is possible to limit the trace objects to either DH messages or PP messages by defining selection criteria before the trace run.

The user may select any of the CALL gates of the GDT as trace point CALL-GATE by specifying the SELECTOR. Memory selections can be defined and activated for up to 8 gates. Prior to definition, the tracer simply checks to make sure that the selector belongs to a call gate. Before using this function, the user should therefore consider whether specification of the desired selector might affect the dynamic properties of the overall system.
Special care should be taken when using OS or DB call gates since some of them are also used by the tracer to enter the dynamic memories in the trace buffer (e.g. ON_P_RECEIVE_UNITS, ON_P_SEND_UNITS); such a case would result in a deadlock in the processor.

For call processing trace points and for the trace point ’Call Gate’, the contents of the following memories can be entered in the trace buffer:

1. CPB : Element of DB_D_CPB_TBL for the associated CPB index.
(if /= 0) and, if necessary, CPB extension (object type CB)

2. DCLD : 1st line: Element of DB_D_CP_DEV_STATE, DB_D_CP_DEV_STATUS
and DB_D_QC_DEV_STATUS (object type CT)
2nd line: Element of DB_D_CP_DEV_TYP (CPDT) and
DB_D_CP_LOGICAL_DEV_TBL (object type CT)
In addition, one element of the following is taken
depending on the device type:
DB_D_CP_DD_EXT_G_ATND (object type DCDEGA)
DB_D_CP_DEV_TBL_EXT_ATND (object type DCDTEA)
DB_D_TM_M_ATND_TIME_I_SERV (object type DCTMATIS)
DB_D_CP_DEV_TBL_TRUNK (object type DCDTT)

3. DCLT : One Element of the following is taken depending on the line type:
DB_D_TLN_DATA_TBL (subscriber table, object type DCST)
DB_D_TRUNK_DATA_TBL (trunk table, object type DCTT)

4. CPCRF : Element of DB_D_CP_NW_CR_TBL (object type CPCRF)

5. DDHD : Element of DB_D_DH_DEV_TBL (object type DT)

6. DHCRF : Element of DB_D_DH_NW_CR_TBL (object type DHCRF)

If an error is detected during tracing, the tracer enters in the trace buffer a data record with an error indication. The user may encounter this procedure if he selects a dynamic memory in a processor in which this dynamic memory is not located (e.g. SELDYN, CP, ALL as a command in the BPA for Hicom 3000; DB_D_DH_DEV_TBL is in the LTG). In the case of the display commands with TYPE=ALL these error indications are visible; they are indicated by the fact that "ER" is specified as the object type, and a 4 digit hexadecimal number is specified as the code (in this specific case the code "070A" indicating error type "No table" for object type "DT").

This hexadecimal number consists of 2 bytes:

•

first Byte indicates the type of Error

–

first hexadecimal digit indicates Group of conditions, which is affected


1st digit of 1st byte	meaning
0	insignificant
1	Error in Group 1
2	Error in Group 2
3	Error in Group 3
4	Error in Group 4

–

second hexadecimal digit is an Error code


2nd digit of 1st byte	meaning	comment
1	nr. of comparison positions incorrect	the tracer administration variables have been destroyed
2	Index for extended CPB incorrect	it was not possible to read the extended CPB with the established extended index because the index limits were found to show implausibilities during database access
3	Index for the table incorrect	this occurs if the Lodad-Packed in the message results in Loden = 0 or DTI = 0 or if there is a conflict between the Lodens or DTI obtained from the Lodad-Packed and the corresponding memory index limits in the database
4	Lodad-Packed incorrect	it is not possible to derive the loden from the Lodad-Packed contained in a call processing message; An example for this is the tracing at trace point PP for S0 bus messages. TSI = 0 is applicable in the DH, in the CP it would result in Loden = NULL. The same applies to the trace point GATE
5	Message length incorrect	an inadmissible message token was transferred to the tracer
6	Offset incorrect for token	an inadmissible message token was transferred to the tracer
7	No table	the relevant database table is not present in the processor in which the tracer is running
8	Trace point inadmissible	the tracing routine was branched to from a point which does not coincide with the scheduled trace points
9	Gate not assigned as trace point	the CALL gate tracing routine was activated from a code point that does not coincide with the assigned administration data
A	Number of condition groups incorrect	the tracer’s administration data has been (number of condition groups implausible) destroyed

•

second Byte indicates involved Object type


errorcode 2nd byte	object type	comment
00	SD	an attempt was made to trace the message contents for a SEND_MESSAGE call
01	RCV	an attempt was made to trace the message contents for a RECEIVE_MESSAGE call
02	PT	an attempt was made to trace the message contents at the logical PETRA tracepoint
03	CP	an attempt was made to trace the message contents at the CP trace point
04	PP	an attempt was made to trace the message contents at the PP trace point
07	TIME	an attempt was made to trace time information
08	CB	an attempt was made to trace the contents of an element of DB_D_CPB_TBL
09	CT	an attempt was made to trace the contents of an element of DB_D_CP_LOGICAL_DEV_TBL or DB_S_CP_DEV_TYPE or DB_D_CP_DEV_STATE or DB_D_CP_DEV_STATUS
0A	DT	an attempt was made to trace the contents of an element of DB_D_DH_DEV_TBL
0B	DCST	an attempt was made to trace the contents of an element of the dynamic subscriber table DB_D_TLN_DATA_TBL
0C	CPCRF	an attempt was made to trace the contents of an element of DB_D_CP_NW_CR_TBL
0D	DDTT	an attempt was made to trace the contents of an element of the dynamic trunk table DB_D_TRUNK_DATA_TBL
0E	DHCRF	an attempt was made to trace the contents of an element of DB_D_DH_NW_CR_TBL
0F	DCDEGA	an attempt was made to trace the contents of an element of DB_D_CP_NW_CR_TBL
10	DCDTEA	an attempt was made to trace the contents of an element of DB_D_CP_DD_EXT_G_ATND
12	DCTMATIS	an attempt was made to trace the contents of an element of DB_D_TM_M_ATND_TIME_I_SERV
13	DCDTT	an attempt was made to trace the contents of an element of DB_D_CP_DEV_TBL_TRUNK
16	TPI	an attempt was made to trace the data of the TPI LAN layer
17	TCP	an attempt was made to trace the data of the TCP LAN layer
1A	IPDSD	an attempt was made to trace the data of IP Dual Port Ram Send
1B	IPDRV	an attempt was made to trace the data of IP Dual Port Ram Receive
1C	ETHSD	an attempt was made to trace the data of a protocol header of the outgoing frame in the ethernet driver
1D	ETHRV	an attempt was made to trace the data of a protocol header of the incoming frame in the ethernet driver
1E	FLAGTR-CP	an attempt was made to trace the message contents of FlagTrace in CP
1F	FLAGTR-PP	an attempt was made to trace the message contents of FlagTrace in PP
20	RDSMON CP	an attempt was made to trace RDS-MON-CP message
21	RDSMON-PP	an attempt was made to trace RDS-MON-PP message
22	RDS-ISDN	an attempt was made to trace RDS-ISDN message
23	AUTOTR-CP	an attempt was made to trace AutoTracer CP messages
24	AUTOTR-PP	an attempt was made to trace AutoTracer PP messages
FF	cannot be determined	an error was detected during tracing from a CALL gate which is not dependent on the object type

OpenScape 4000 V10, Volume 1: AMO Descriptions, Service Documentation, Issue 5, ID: P31003H31A0S107057620

© 09/2025 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.