Note: The message
type "MSG," or "DATA," can be retrieved without a field ID. All other
message types must use a field ID.
If any message data
is to be sent along with an attachment, that message is sent following
the attachment header. The field name for this type of message is
either "MSG" or "DATA." The following sample is based on the map that
is used in the code example provided on the Common Messaging Interface
documentation.
The map for this message
is described as: 'SHORT;LONG;DOUBLE;CHAR,,50'.
The following table
shows the data values for the message data.
Data Values for the Message Data
|
|
|
|
|
|
|
|
|
"ABCDEFGHIJKLMNOPQRSTUVWXYZ";
(blank padded to 50)
|
The following table
shows the data type values for the message data.
Data Types for the Message Data
|
|
|
|
|
add with tibrvMsg_AddI16()
|
|
|
add with tibrvMsg_AddI32()
as appropriate
|
|
|
add with tibrvMsg_AddF64()
|
|
|
add with tibrvMsg_AddString()
|
The following table
shows the layout of the message data.
Fields for the Message Data
|
|
|
|
|
|
|
The number of data pieces
to follow. For this example, the value of the field is "4".
|
|
|
|
The data type of the
first data item. Because this data item is a short, the value for
this field is "1".
|
|
|
|
The actual value of
the first parameter being sent. In this case, because it is a short,
the value is added to the message by using tibrvMsg_AddI16(). The
value for this field is "100".
|
For each parameter that
is sent, repeat fields 2 and 3 in the previous table, setting the
appropriate values and incrementing the field IDs.