195.4.2.2 SELMSG

The first parameter TRACEPT determines whether 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: Section 195.5.1) are selected or whether Start- and Stopconditions should be set.

The following functions are possible:

All messages and trace objects can be selected for each trace point

Only those messages or LAN objects are selected, which fulfill one of the 4 groups with up to 8 conditions

No message or no LAN object is selected

Only those messages which fulfill one of the 4 groups with up to 8 conditions result in start or stop or stopall of tracing

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" .

The start, stop, stopall condition is deactivated

Up to 8 conditions can be formulated for post-selection

The conditions formulated for post-selection are deleted

The conditions for a group or for a tracepoint are deleted.

Note

Be aware of the fact, that if the parameters CONDGRP and COND are ignored (both are optional !), nothing will be traced at this tracepoint, because the defaultvalue 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.

•

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, 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.

A larger example for the usage of this function is given in the AMO Description of the TRACS, chapter Examples.

Start, Stop and Stopall Conditions

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 tracing (stopall object) for all configured processors in a HICOM system (including the IS).

If STOP and STOPALL conditions are defined together, the tracer checks at first the STOP conditions and then the STOPALL conditions. If there are identically conditions defined on both trace points, then the tracer only checks the STOP conditions and at positive result, only the tracer in the current processor will be stopped. In this case the STOPALL conditions will be ignored, i.e. they have no effect!

Note

A special case occurs, when messages or LAN objects with time selection should be taken into the trace buffer and a system restart happens (restart stability is on). When serializing with OS resources (SELSTOP,OS) no time and date information can be requested during a short period. The cause is, that the time data of the operation system (OS) are not valid, and DUMMY values are returned by the access routine of the OS.

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 tracer is also deactivated. (When a stop or stopall condition is entered, this would not be practical, because the tracer 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 tracer (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 is activated and the start message is 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 is deactivated. The stop object is the last object to be entered in the buffer.

When the stopall object is received, tracing is deactivated in all processors in which a tracer is active. The last object to be entered in the buffer is the stopall object.

The defined control conditions remain available (status = R for start, stop and stopall conditions) and come into effect again with the next ON command.

The STATUS command shows the states of the control conditions:

–

D (definition status)

–

R (reached)

–

W (waiting status)

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.