MQXF_DATA_CONV_ON_GET

The MQXF_DATA_CONV_ON_GET function identifier is used with MQ_GET_EXIT.

See MQ_GET_EXIT for information about the interface to this call, and a sample C language declaration.

Usage notes

If registered, this entry point is called when messages arrive at the application but before any data conversion has occurred. This can be useful if the API exit needs to perform processing, such as decryption or decompression, before the message is passed to data conversion. The exit can, if necessary, cause data conversion to be bypassed by returning MQXCC_SUPPRESS_FUNCTION; for more information, see MQAXP structure.

Registering for this entry point on a client has the effect of causing the data conversion to be performed locally on the client machine. For correct operation it might, therefore, be necessary to install the application conversion exits on the client. Note that MQXF_DATA_CONV_ON_GET is also used for asynchronous consume.

When using the MQ_GET_EXIT call, use MQXF_DATA_CONV_ON_GET, with exit reason MQXR_BEFORE, to register a before MQGET data conversion exit function.

There is no MQXR_AFTER exit function for MQXF_DATA_CONV_ON_GET; the MQXR_AFTER exit function for MQXF_GET provides the required capability for exit processing after data conversion.

Separate entry points are defined for the MQ_GET_EXIT call, so to intercept both exit functions, the MQXEP call must be used twice; for this call use function identifier MQXF_DATA_CONV_ON_GET.

Because the MQ_GET_EXIT interface is the same for MQXF_GET and MQXF_DATA_CONV_ON_GET, a single exit function can be used for both; the Function field in the MQAXP structure indicates which exit function has been invoked. Alternatively, the MQXEP call can be used to register different exit functions for the two cases.