Skip to main content
Omnitracs Knowledge Base

Routed (QMASS) Text Forward Messages - Type 606

Routed (QMASS) Text Forward Messages (Type 606)

Routed text forward messages are obtained by QTRACS as a result of periodic polling of the NMC by the Communications Manager process. Each of them is delivered to the appropriate external application via this Routed Text Forward Message transaction. This transaction may only be received in systems that are running with the QMASS feature enabled.

All Routed Text Forward Messages will be delivered to a single external application if QTRACS has been instructed to do so. To enable delivery of this transaction to an external application, the following Account Preferences must be set: Enable QMASS Features = *YES; and External Application to Receive QMASS Text Messages ={a valid external application}.

Routed Text Forward Message transaction formats

From To Size Type Field Description
1 5 9 Packed Global Message Handle
6 8 3 Character Transaction Type = 606
9 9 1 Character Destination Entity Type
10 19 10 Character Destination Entity Identifier
20 24 9 Packed Reserved - returned as zero
25 25 1 Character Reserved - returned as blank
26 26 1 Character Forward Message Priority
27 30 7 Packed Reserved - returned as zero
31 31 1 Binary Reserved - returned as binary zero - all 8 bits are off
32 32 1 Character QMASS Routed Copy
33 42 10 Character QMASS Auxiliary ID of Sender
43 73 31 Character QMASS Return Auxiliary ID String
74 173 100 Character Reserved - returned as blanks
174 176 3 Zoned Reserved - returned as zero
177 179 3 Zoned Reserved - returned as zero
180 186 13 Packed Message Time
187 190 4 Zoned Message Length
191 2090 1900 Character Message Body

Routed Text Forward Message transaction field descriptions

Field Description
Global Message Handle (GMH) This packed decimal field contains the global message handle. The global message handle (GMH) is a universal handle that can be used to reference a specific message. Each return message is assigned a global message handle by QTRACS.
Transaction Type This is the code that identifies the transaction as a routed copy of a text forward message. It is a 3-character numeric field that will contain 606.
Destination Entity Type This is a one-character code that identifies the entity type of the destination of the message, where:
V the message was sent to an owned vehicle
T the message was sent to an auxiliary vehicle.
Destination Entity Identifier This is the 10-character destination identifier. It identifies the destination entity of the message. This should always be a registered QTRACS vehicle identifier.
Forward Message Priority This is the priority of the forward message; where:
0 normal service
1 important (activates driver paging system if installed)
2 sleepy service
3 important sleepy
4 low priority
9 emergency service (highest priority forward message).
QMASS Copy This single byte character value indicates whether this is a routed copy of the message, where:
0 = original
1 = copy This field will always be set to '1' in this transaction.
QMASS Auxiliary ID of Sender This 10-character field contains the QTRACS auxiliary identifier of the sender of this binary message. This is a QTRACS Type 'B' entity.
QMASS Return Auxiliary String This 31-character string contains the text included in routed return messages from the vehicle to the auxiliary account. This text is specified by the owner of the vehicle at the time the vehicle is made available through QMASS.
Message Time This 13-digit packed decimal numeric field contains the time and date that the message was received by the NMC. This field is in the QTRACS GMT seconds format and may be converted for display using the QTRACS date/time APIs.
Length This is the length (in bytes) of the message as it is stored in the message body field.
Message Body This field contains the body of the text message. It is a variable length field. The length of the field (in bytes) is indicated in the message length field described above. This field can contain a maximum of 1900 bytes of data. The body of a routed forward message is always delivered to an auxiliary account in fully expanded format regardless of whether or not the original forward message was freeform or macro. The account that receives this QTRACS message does not have any way of determining the forward macro number that was used by the originating system.
  • Was this article helpful?