DFDL predefined variables in IBM® Integration Bus
The following table describes how the integration node sets the values of DFDL predefined variables.
DFDL domain call point | DFDL external variable | Value set by broker |
---|---|---|
Input bit stream parsed from an input or request node Tree serialization at an output or request node |
encoding |
The integration node 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 integration node 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 product documentation online. The binary
number encoding is defined by one of the following items:
|
|
binaryFloatRep |
||
bit stream 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 integration node 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 integration node 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 product documentation online. In ESQL, the binary number encoding is defined by the ENCODING parameter. |
|
binaryFloatRep |