How queue managers process exit functions

 

The processing performed by the queue manager on return from an exit function depends on both ExitResponse and ExitResponse2. Table 1 below summarizes the possible combinations and their effects for an MQXR_BEFORE exit function, showing:

For an MQXR_AFTER exit function:

For an MQXR_CONNECTION exit function:

In all cases, where an exit or the queue manager sets CompCode and Reason, the values set can be changed by an exit invoked later, or by the API call (if the API call is invoked later).

MQXR_BEFORE exit processing
Value of ExitResponse CompCode and Reason set by Value of ExitResponse2 (default continuation) Chain Value of ExitResponse2 (default continuation) API
MQXCC_OK exit Y Y
MQXCC_SUPPRESS_EXIT exit Y Y
MQXCC_SUPPRESS_FUNCTION queue manager N N
MQXCC_SKIP FUNCTION exit N N
MQXCC_FAILED queue manager N N

 

Parent topic:

WebSphere MQ API exit parameter structure (MQAXP)


fg14610_