196.4.2.1 SELMSG

The first parameter TRACEPT determines whether switching-processing-messages (PP, CP or SW in general), OS-messages (SD, RCV or OS in general) or LAN-data (to have a more specific selection at the LAN-tracepoint the command SETLAN is used, see Section 196.6.1) are selected or whether Start- and Stopconditions should be set.
The following functions are possible for the StandardTracer:
1.
All messages and trace objects can be selected for the corresponding trace points
2.
Only those messages are selected, which fulfill one of the 4 groups with up to 8 conditions
3.
No message or no LAN object is selected
4.
Only those messages or LAN objects which fulfill one of the 4 groups with up to 8 conditions result in start or stop or stopall of tracing or in stop of PETRA
5.
Messages or LAN objects, which fulfill one of the 4 groups with up to 8 conditions, result during tracing in the specific message dependent change of selection conditions, which were defined in the "conditional conditions".
6.
The start, stop, stopall, PETRA condition is deactivated
7.
Up to 8 conditions can be formulated for post-selection (Attention: no condition groups valid for this function !!)
8.
The conditions formulated for post-selection are deleted
9.
The conditions for a group or for a trace point are deleted.
The following functions are possible for the FlagTracer:
1.
CP and PP messages can be selected for FlagTracer
The following functions are possible for the AutoTracer:
1.
CP and PP messages can be selected for AutoTracer
The following functions are possible for the RDSTracer:
1.
CP and PP messages of set monitors
2.
PP messages for RDS ISDN Tracer.
NOTE:  Be aware of the fact, that if the parameters CONDGRP and COND are ignored (both are optional !), the selection criteria will be reset, because the default value is OFF.
Selection of Messages and LAN Objects
By setting conditions it is possible to select only those traceobjects which are of interest for the user. The tracer is able to make the valuation of messages in 2 different ways:
•
The input of byte values as comparison data result in a tracer, which only enters the message into the trace buffer, when the addressed byte is exactly equal to one of this byte values. It is possible to enter multiple values (up to 50) for each byte. It is also possible, to specify several conditions (up to 8) for one group, which must be performed all for a selection of a message.
In the case of SELMSG with FLDTYPE = SDNO, please note that the state diagram number in the display commands is represented as a word, with the result that byte 0 in the state diagram number consists of the last two digits in the state diagram number.
•
At mask comparison (parameter FLDTYPE = PST), the position of one or more bits (= mask) which must be contained in the desired message byte, have to be entered as trace data. If these bit(s) occur in the message byte, the message is taken into the trace buffer. Are there, additional to the mask-bit(s), also other bits which are set in the certain message byte, then the message is also taken into the buffer, because it corresponds likewise to the given bit mask. With this method, it is possible now, to watch powersets or variable byte values contained in a message byte, on bit level.
Example:
 
BITPOS
BIT1&BIT4&&BIT7
B’01111010
H’7A
 
or
B’01111011
H’7B
 
or generally
B’x1111x1x
 
These two comparison methods may be combined, if needed, in any sequence for each condition group.
If several condition groups are defined the sequence of the groups has to be considered, because tracing works in following way:
The tracer checks the first group. If the conditions for the message are fulfilled, the message will be copied into the trace buffer corresponding to the definitions for that group (length, conditional conditions). Further groups will not be checked. If the conditions are not fulfilled the same procedure is repeated with the next group.
The user has the possibility to control the tracing himself by assigning in case of overlapping selections a lower groupnumber to the group which contains the more important definitions (that is: length, dynamic memories, conditional conditions,..).
Rule of thumb: the more restrictive a condition is the lower its group number should be.
Generally: if the condition of a group is a subset of another one it must have the smaller groupnumber
Conditional Conditions
The byte values defined for selections can also be set, changed and deleted automatically during the tracing dependent of message contents. That happens according to the defined conditional conditions (parameter COND=CCD1/..CCD8).
That means: from the message which matches the selection conditions are used up to eight bytes as condition for a future message. E.g. a LINE from the current message can be used as condition for a next message. Following conversions are made: LODAD, LODADP, LODEN, DTI, LTGLINE, LINE
Start, Stop, Stopall, PETRA Conditions and Trace Stop Netwide
The start condition describes the properties of a message or a LAN object which activates tracing (start object).
Example
 
SELMSG,START,G1,CD1,SRC,34&57,e;
the Tracer is started if a message
SELMSG,START,G1,CD2,EV,3E,e;
occurs, which 4th Byte is 3E and its
 
first Byte is either 34 or 57.
The stop condition describes the properties of a message or a LAN object which deactivates tracing (stop object).
The stopall condition describes the properties of a message or a LAN object which deactivates the StandardTracer for all configured processors in a system (including the IS) and StandardTracer in partner systems if a netwide trace stop is defined (stopall object). If FLAGTR,STOPALL have been selected, the FlagTracer blocking is set, see Section 196.4.2.3 on page 196‑2591.
The PETRA-condition describes the properties of a message, which switches off the PETRA (PEripherial TRAcing) in the actual processor (PETRA-message). The message, provided with the object type PT, will be entered into the trace buffer. In this way it is easy to find the message within the trace buffer (using the commands DA, DB, DF, DL, DN, DA-T, DB-T, DF-T, DL-T, DN-T and type=PT).
IF STOP, STOPALL and / or PETRA conditions are defined at the same time, the tracer checks the STOP conditions first, then the STOPALL conditions and at last the PETRA conditions. If there are identically conditions defined on more trace points, then the tracer only checks the STOP conditions and if it is fulfilled, just the tracer in the current processor will be stopped. In this case the STOPALL conditions and PETRA conditions will be ignored, i.e. they have no effect!
In order to give the user sufficient time to define all the individual conditions required, the execution of the control condition is temporarily suspended until all conditions have been entered.
When a start condition is entered, the StandardTracer is also deactivated. (When a stop or stopall condition is entered, this would not be practical, because the StandardTracer should not be deactivated before the stop resp. stopall object has been received).
The definition status for the defined control conditions is terminated by the activation of the StandardTracer (command ON); these control conditions are then placed in the waiting state.
At this stage each message and each LAN object is checked by the activated trace points to determine whether it meets the defined control conditions.
After the start object has been received, tracing of the StandardTracer is activated and the start object entered in the buffer. (If no start condition is defined, tracing had been in effect from the activation of the tracer onward).
Further messages or LAN objects are then entered in the buffer according to the trace point selections.
When the stop object is received, tracing of the StandardTracer is deactivated and stopping is signaled at the console. The stop object is the last object to be entered in the trace buffer of the StandardTracer.
When the stopall object is received, tracing of the StandardTracer is deactivated in all processors in which a tracer is active and stopping is signaled at the console. The last object to be entered in the buffer is the stopall object. If FLAGTR, STOPALL have been selected, the tracing of the FlagTracer is stopped too, see Section 196.4.2.3 on page 196‑2591. If in a processor a netwide trace stop has been defined with the NETSTOP command, stop-instructions will be sent to the selected partner switches. In the partner switches the StandardTracer in all configured processors are stopped and in case of a defined netwide trace stop the stop instruction will be also forwarded to partner switches.
The defined control conditions remain available (status = R) and come into effect again with the next ON command.
The STATUS command indicates the states of the control conditions:
–
D (definition status)
–
R (reached)
–
W (waiting status)
Stop condition with station selection can be made using the following command:
SELMSG,SW,G1,CD1,STN,<stno>;
Example of trace selection for station number:
SELMSG,SW,G1,CD1,STN,<stno>;
Example of trace selection for circuit number:
SELMSG,SW,G1,CD1,PEN,<pen_number>;
TRCCONF – Trace profiles settings
•
Overview for TRACS/DIAGS improvements
The new feature allows storing / restoring DIAGS switches into / from specified file. The file is the one used for storing / restoring trace selection table.
New parameters were introduced on COPY,TAB-HD/HD-TAB branches in AMO TRACS.
- following commands can be used to store in file <file_name> the currently DIAGS switches set to on:
COPY,TAB-HD,<file_name>,<description>,,DIAGSON; // SAVE ONLY DIAGS SWITCHES THAT ARE ON
COPY,TAB-HD,<file_name>,<description>,,DIAGSALL; // SAVE ALL DIAGS SWITCHES THAT ARE ON OR OFF
COPY,TAB-HD,<file_name>,<description>,ALLSTD,DIAGSON;
 
- following commands can be used to restore (save to database) the DIAGS switches from specified file:
COPY,HD-TAB,<file_name>,NO,LIST;
COPY,HD-TAB,<file_name>,NO,Y;
COPY,HD-TAB,<file_name>,ALLSTD,Y;
Command DISPLAY,TRCCONF,<directory_name>; outputs the files created with command "COPY,TAB-HD...".
RES,DIAGS; resets the DIAGS switches to the default values:
for ZAND/ALLDATA/CNTRYCD = 0 (IM) defaults are
CP complex: S15 = ON
CP2 complex: S04 = ON
for ZAND/ALLDATA/CNTRYCD = K (USA) defaults are
CP complex: S15 = ON
CP2 complex: S04 = ON
DB complex: S00,S01 = ON
NOTE:  The user can save existing trace settings and DIAGS switches values into a file on HD and import them afterwards.
Example of saving the DIAGS switches and trace settings into a file:
<CHANGE-DIAGS:COMP=DH,S03=ON;
CHANGE-DIAGS:COMP=DH,S03=ON;
H500: AMO DIAGS STARTED
H03: S03 OF COMPLEX DH IN LTG HAS BEEN CHANGED TO 'ON'
AMO-DIAGS-111 ADMINISTRATION OF DIAGNOSTIC SWITCHES, SWITCHING UNIT
CHANGE COMPLETED;
<exe-tracs:bp;
EXE-TRACS:BP;
H500: AMO TRACS STARTED
AMO TRACS VARIANT/VERSION 5E/001 OF 2016-05-24
TRACER VARIANT/VERSION 5E/001 OF 2016-05-26
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*res,all;
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*selmsg,sw,g1,all;
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*msglen,sw,g1,3000;
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*copy,tab-hd,":diag:tracesettings","SW trace with 3000 bytes messages",allstd,diagson;
H23: WRITING OF TRACE SELECTION TABLE COMPLETED
H56: WRITING OF DIAGS SWITCHES SELECTION COMPLETED
(LOADDISP COMPLEX IS NOT AFFECTED)
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*res,all
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*sta,c
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*display,trcconf,:diag:;
DISPLAYED DIRECTORY: :DIAG:
+------------------+-----------------------------------------------------------+
| TRACE NAME | DESCRIPTION |
| | AND ACTIVATED DIAGS SWITCHES IN FILE |
+------------------+-----------------------------------------------------------+
| TRACESETTINGS | SW TRACE WITH 3000 BYTES MESSAGES |
| | CP:14,15 DH:03 DB:03,10 CP2:02,04,09 |
+------------------+-----------------------------------------------------------+
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
*copy,hd-tab,:diag:tracesettings,allstd,y;
H24: READING OF TRACE SELECTION TABLE COMPLETED
********************************************************************************
* STANDARD TRACER *
********************************************************************************
MAX:UNLTD SELOBJ:0 ACTOBJ:0 TRC:OFF SITE:AMO RST:OFF
STARTCD:D STOPCD:D PETRACD:D STOPALLCD:D
SELECTIONS AT TRACEPOINT CP :
CONDITIONGROUP 1 ( MAX. MESSAGE LENGTH = 3000 BYTES ) :
ALL MESSAGES ARE ENTERED INTO THE TRACE BUFFER
SELECTIONS AT TRACEPOINT PP :
CONDITIONGROUP 1 ( MAX. MESSAGE LENGTH = 3000 BYTES ) :
ALL MESSAGES ARE ENTERED INTO THE TRACE BUFFER
STANDARD TRACER FILE :DIAG:NUME_TRACE02
********************************************************************************
* COMMON INFORMATION *
********************************************************************************
USER:
SERI:OS
BUFFER OF THE RESIDENT TRACER: 7 BUFFER AT 64000 BYTE
STDTR:0 FLAGTR:0 AUTOTR:7 RDSTR:0 FREE:0
TRACE BUFFER POOL: 20 BUFFER AT 64000 BYTE
STDTR:0 FLAGTR:0 DISPLAY:0 RDSTR:0 FREE:20
********************************************************************************
H55: S14 OF COMPLEX CP IN CC IS ALREADY SET TO 'ON'
H55: S15 OF COMPLEX CP IN CC IS ALREADY SET TO 'ON'
H55: S03 OF COMPLEX DH IN LTG IS ALREADY SET TO 'ON'
H55: S03 OF COMPLEX DB IN CC IS ALREADY SET TO 'ON'
H55: S03 OF COMPLEX DB IN LTG IS ALREADY SET TO 'ON'
H55: S10 OF COMPLEX DB IN CC IS ALREADY SET TO 'ON'
H55: S10 OF COMPLEX DB IN LTG IS ALREADY SET TO 'ON'
H55: S02 OF COMPLEX CP2 IN CC IS ALREADY SET TO 'ON'
H55: S04 OF COMPLEX CP2 IN CC IS ALREADY SET TO 'ON'
H55: S09 OF COMPLEX CP2 IN CC IS ALREADY SET TO 'ON'
H57: READING OF DIAGS SWITCHES SELECTION COMPLETED
(LOADDISP COMPLEX IS NOT AFFECTED)
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
 
Use RES,DIAGS; command mentioned above to reset the DIAGS switches from database.
The default trace profiles can be found under :DIAG:TRCCONF on the Hard Disk (they are added with the first RMX-HF applied to the system). They can be listed using the command below:
*display,trcconf;
H60: DEFAULT DIRECTORY IS ":DIAG:TRCCONF"
DISPLAYED DIRECTORY: :DIAG:TRCCONF
+------------------+-----------------------------------------------------------+
| TRACE NAME | DESCRIPTION |
| | AND ACTIVATED DIAGS SWITCHES IN FILE |
+------------------+-----------------------------------------------------------+
| 1 | GVS TRACE1 FOR REPRODUCIBLE FAULTS |
| | CP:14 |
+------------------+-----------------------------------------------------------+
| 2 | GVS TRACE 1 WITH ACL FOR REPRODUCIBLE FAULTS |
| | CP:14 |
+------------------+-----------------------------------------------------------+
| 3 | GVS TRACE2 FOR HIGH TRAFFIC |
| | CP:14 |
+------------------+-----------------------------------------------------------+
| 4 | GVS TRACE2 WITH ACL FOR HIGH TRAFFIC |
| | CP:14 |
+------------------+-----------------------------------------------------------+
| 5 | GVS TRACE 3 FOR PATH PROBLEMS |
| | CP:14 DH:03 DB:03 |
+------------------+-----------------------------------------------------------+
| 6 | GVS TRACE 3 WITH ACL FOR PATH PROBLEMS |
| | CP:14 DH:03 DB:03 |
+------------------+-----------------------------------------------------------+
| 7 | ISDN MESSAGES ONLY (TRACE FOR SERVICE) |
| | NONE |
+------------------+-----------------------------------------------------------+
| 8 | GCS/GVS GENERAL TRACE TO CAPTURE MOST TYPES OF PROBLEM |
| | CP:14 DH:03 DB:03,10 CP2:02,04 |
+------------------+-----------------------------------------------------------+
| 9 | GVS CDR GENERAL TRACE FOR REPRODUCIBLE FAULTS |
| | CP:14 CDR:10,11 |
+------------------+-----------------------------------------------------------+
| 10 | GVS CDR TRACE FOR CHARGE CALCULATION PROBLEMS |
| | CP:14 CDR:10,11,12 |
+------------------+-----------------------------------------------------------+
| 11 | GVS CDR HIGH TRAFFIC (INCLUDING CHARGE CALCULATION) |
| | CP:14 CDR:10,11,12 |
+------------------+-----------------------------------------------------------+
| 12 | GVS CDR TRACE FOR HUNG COSTI BUFFER ISSUES |
| | CP:14 CDR:10,11,15 |
+------------------+-----------------------------------------------------------+
TRACER INPUT IN BPA (STANDARD TRACER ) PLEASE:
 
To activate such a trace profile execute the following command:
COPY,HD-TAB,<trace_name>,ALLSTD,Y;
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.