Forward Binary Message - Type 604

Submitting a Forward Binary Message (Type 604)

This transaction is used to request the transmission of a binary message to one or more vehicles. The receipt of this transaction will cause QTRACS to place a call to OMCRTMSG. The parameter list will be constructed using values supplied in the transaction. Refer to the OMCRTMSG section of this document for additional information.

Forward binary message transaction format

From	To	Size	Type	Field Name
1	5	9	Packed	Local GMH
6	8	3	Character	Transaction Type = 604
9	18	10	Character	Sender
19	19	1	Character	Reserved - set to blanks
20	21	3	Packed	Reserved - set to zero
22	241	220	Character	Destination List
242	243	3	Packed	Times to Transmit
244	244	1	Character	Priority
245	245	1	Character	Schedule
246	246	1	Character	Return Receipt
247	247	1	Character	Word Wrap
248	257	10	Character	Response Indicator
258	259	3	Packed	Binary Data Type
260	261	3	Packed	Reserved - set to zero
262	271	10	Character	Application ID
272	278	7	Character	Reserved - set to blanks
279	279	1	Character	Body Type Indicator
280	282	5	Packed	Message Body Length
283	3132	2850	Character	Message Body

Field Name	Description
Local GMH	This packed decimal field contains the Local GMH as assigned by the application requesting that this message be sent. Upon receipt of this transaction, QTRACS will assign a Global Message Handle. If requested, QTRACS will return that GMH to the external application defined in the Application ID field. QTRACS discards the Local GMH upon receipt.
Transaction Type	This field must be set to 604.
Sender	Source entity identifier. Denotes the source (sender) of the message. The source must be a simple entity: user, application or vehicle.
Destination List	List of up to 20 destination entity identifiers (addressees). Each entry must be an ID of a valid user, vehicle, address list, vehicle group, or wildcard. Each entry is 11 characters long to allow for indirection (@) to be specified. The list is terminated by first blank entry. Note that to send to all users, all vehicles, or to the NMC there must be only one destination: ALLVEH, ALLUSR, or *NMC.
Times to Transmit	Times to transmit. This field is passed through to the NMC. It is only used for components of the message that are transmitted over the OmniTRACS link. A zero value in this field will cause the NMC to transmit the message based on its internal defaults. This field should be set to zero unless there are very specific transmission requirements. Setting this field to a value other than zero may adversely affect the characteristics of the transmission priority.
Priority	Message transmission priority. Valid values are: 0 normal priority 1 important priority 2 sleepy priority 3 sleepy plus priority 4 low priority 9 emergency priority
Schedule	Schedule for off-peak (batch) transmission where: 0 disable 1 enable
Return Receipt	This field must be set to 0.
Word Wrap	This field must be set to 0.
Response Indicator	This field must be set to *NONE.
Binary Data Type	This field indicates the type of data that is contained in the binary message body, where: 004 SensorTRACS data 006 JTRACS data 007 TrailerTRACS data
Application ID	If the calling application would like QTRACS to return the GMH for this message, then this field should contain the registered QTRACS external application id to which the 692 transaction will be sent. See an explanation of the 692 transaction for more details. This is only necessary in a RI (remote integration) environment.
Body Type Indicator	This field must be set to 'B' (binary).
Message Length	This is the length (in characters) of the message as it is stored in the Binary Message Body field. The maximum length is 2850.
Binary Message Body	This field contains the body of the message. It is a variable length field. The length of the field (in characters) is indicated in the Message Length field described above.