Your input file for the utility must conform to the C language syntax. If you are unfamiliar with C, refer to Example of valid syntax for the input data set.
In addition, be aware of the following rules:
MQCHAR fields are code page converted, but MQBYTE is left untouched. If the encoding is different, MQSHORT, MQLONG, MQINT64, MQUINT64, MQINT32, and MQUINT32 are converted accordingly.
This is because the utility for creating conversion-exit code does not provide the facility to convert these data types. To overcome this, you can write your own routines and call them from the exit.
Other points to note:
struct TEST { MQLONG SERIAL_NUMBER; MQCHAR ID[5]; MQSHORT VERSION; MQBYTE CODE[4]; MQLONG DIMENSIONS[3]; MQCHAR NAME[24]; } ;
This corresponds to the following declarations in other programming languages:
10 TEST. 15 SERIAL-NUMBER PIC S9(9) BINARY. 15 ID PIC X(5). 15 VERSION PIC S9(4) BINARY. * CODE IS NOT TO BE CONVERTED 15 CODE PIC X(4). 15 DIMENSIONS PIC S9(9) BINARY OCCURS 3 TIMES. 15 NAME PIC X(24).
Supported only on WebSphere MQ for z/OS.
TEST EQU * SERIAL_NUMBER DS F ID DS CL5 VERSION DS H CODE DS XL4 DIMENSIONS DS 3F NAME DS CL24
Supported on z/OS only
DCL 1 TEST, 2 SERIAL_NUMBER FIXED BIN(31), 2 ID CHAR(5), 2 VERSION FIXED BIN(15), 2 CODE CHAR(4), /* not to be converted */ 2 DIMENSIONS(3) FIXED BIN(31), 2 NAME CHAR(24);
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
vax |