How the exit is invoked

 

When enabled, the API-crossing exit is invoked:

• By all applications that use the CICS adapter of WebSphere MQ for z/OS

• For the following MQI calls:

  • MQCLOSE

  • MQGET

  • MQINQ

  • MQOPEN

  • MQPUT

  • MQPUT1

  • MQSET

• Every time one of these MQI calls is made

• Both before and after a call

This means that using the API-crossing exit degrades the performance of WebSphere MQ for z/OS, so plan your use of it carefully.

The exit program can be invoked once before a call is executed, and once after the call is executed. On the before type of exit call, the exit program can modify any of the parameters on the MQI call, suppress the call completely, or allow the call to be processed. If the call is processed, the exit is invoked again after the call has completed.

The exit program is not recursive. Any MQI calls made inside the exit do not invoke the exit program for a second time.

 

Parent topic:

Using the API-crossing exit

fg15280_