The following table describes how the broker sets the values of DFDL predefined variables.
DFDL domain call point | DFDL external variable | Value set by broker |
---|---|---|
Input bitstream parsed from an input or request node Tree serialization at an output or request node |
encoding |
The broker sets the value of this variable
from the coded character set identifier that is
active. The coded character set identifier is defined
by one of the following items:
|
byteorder |
The broker sets the values of these variables from the binary number encoding that is active. Note that the binary number encoding is a combination of the byte order and floating point representation. The byte order and floating point representation are separated by using masks. For more information about masks, see MQ encoding masks in the WebSphere® MQ information center. The binary
number encoding is defined by one of the following items:
|
|
binaryFloatRep |
||
Bitstream parsed through an API call. For example, an ESQL CREATE command that includes a parse clause. Tree Serialization through an API call. For example an ESQl ASBITSTREAM command. |
encoding |
The broker sets the value of this variable from the coded character set identifier parameter. In ESQL, the coded character set identifier is defined by the CCSID parameter. |
byteorder |
The broker sets the value of these variables from the binary number encoding parameter value. Note that the binary number encoding value is a combination of the byte order and floating point representation. The byte order and floating point representation are separated by using masks. For more information about masks, see MQ encoding masks in the WebSphere MQ information center. In ESQL, the binary number encoding is defined by the ENCODING parameter. |
|
binaryFloatRep |