Mapping RPC Data to the MQ Message Buffer

RPC data is described by Software AG IDL. See Software AG IDL File. The RPC Server for IBM MQ offers two possibilities to map IDL to MQ messages:

Mapping IDL as XML

IDL is mapped to XML format using the XML Mapping Editor. The outcome of this process is an XML mapping file (Workbench file with extension xmm). This resulting XMM file has to be specified by the configuration property entirex.bridge.xmm.

Mapping IDL as Text

The RPC Server for IBM MQ uses the predefined mapping of IDL data types to the MQ message buffer. See below. If your programs use arrays of groups, set the property entirex.bridge.marshalling to "Natural" or "COBOL". If your programs do not use arrays of groups, do not set entirex.bridge.marshalling.

Data Type Description Format Note
Anumber Alphanumeric number bytes, encoding the characters.  
AV Alphanumeric variable length Bytes up to the end of the buffer. 1, 4
AV[number] Alphanumeric variable length with maximum length Bytes up to the end of the buffer, maximal length number. 1
Knumber Kanji Same as data type A.  
KV Kanji variable length Same as data type AV. 1, 4
KV[number] Kanji variable length with maximum length Same as data type AV[number]. 1
I1 Integer (small) sign (+, -) and 3 bytes (digits).  
I2 Integer (medium) sign (+, -) and 5 bytes (digits).  
I4 Integer (large) sign (+, -) and 10 bytes (digits).  
Nnumber1[.number2] Unpacked decimal sign (+, -), number1 bytes (digits) [number2] bytes (digits), no decimal point.  
Pnumber1[.number2] Packed decimal sign (+, -), number1 bytes (digits) [number2] bytes (digits), no decimal point.  
L Logical 1 byte: X for true, all other false.  
D Date YYYYMMDD. 2
T Time YYYYMMDDhhmmssS. 3

Notes:

  1. Only as last value.
  2. YYYY year, MM month, DD day.
  3. YYYY year, MM month, DD day, hh hour, mm minute, ss second, S tenth of a second.
  4. Not possible when using COBOL.

Data types not supported:

  • Binary (B[n],BV, BV[n])

  • Floating point (F4, F8)