The programming languages that can be used for a data-conversion exit are determined by the environment.
In this case, the DXREA field in the MQDXP parameter on input to the exit will have the value RC2079.
In this case, the DXREA field in the MQDXP parameter on input to the exit will have the value RCNONE (if the receiving application provided a buffer that was big enough for the message).
The distinguishing characteristic of a truncated message is that the length provided to the exit in the INLEN parameter will be less than the length implied by the format name contained in the MDFMT field in the message descriptor. The exit should therefore check the value of INLEN before attempting to convert any of the data; the exit should not assume that the full amount of data implied by the format name has been provided.
If the exit has not been written to convert truncated messages, and INLEN is less than the value expected, the exit should return XRFAIL in the DXRES field of the MQDXP parameter, with the DXCC and DXREA fields set to CCWARN and RC2110 respectively.
If the exit has been written to convert truncated messages, the exit should convert as much of the data as possible (see next usage note), taking care not to attempt to examine or convert data beyond the end of INBUF. If the conversion completes successfully, the exit should leave the DXREA field in the MQDXP parameter unchanged. This has the effect of returning RC2079 if the message was truncated by the receiver's queue manager, and RCNONE if the message was truncated by the sender of the message.
It is also possible for a message to expand during conversion, to the point where it is bigger than OUTBUF. In this case the exit must decide whether to truncate the message; the DXAOP field in the MQDXP parameter will indicate whether the receiving application specified the GMATM option.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
amqwak02223 |