IT22585: MQ_TERM_EXIT API exit function not being called on MQDISC when it is failing with rc 2009

APAR status

• Closed as program error.

Error description

• An application using an API Exit invokes MQ_INIT_EXIT.
  
  Later the same application calls MQDISC on a valid HConn which
  fails with MQRC 2009 CONNECTION BROKEN.
  
  In this case MQ_TERM_EXIT is not being called.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of API exits which rely on the API exit termination entry
  point (MQ_TERM_EXIT) to be called.  An example of what the
  user's code might do in this routine is free memory it has
  allocated in an earlier routine (eg. MQ_INIT_EXIT).
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The MQ code responsible for calling the MQ_TERM_EXIT function
  was omitting this call, in the case where the MQDISC call was
  failing.
  
  Omitting the call to MQ_TERM_EXIT would have been the right
  thing to do, if the HConn was continuing as a valid value,
  because the associated exit library could possibly have received
  further API exit calls.
  
  However it was the wrong thing in this case because the HConn
  was being disconnected and removed from use, and so would not be
  valid in future, and so would never have received further API
  exit calls.  It was therefore correct to call MQ_TERM_EXIT and
  unload the exit library.
  

Problem conclusion

• The MQ code has been corrected so that, in cases where the HConn
  is being invalidated and removed from use, the MQ_TERM_EXIT
  entry point is called, and the exit library unloaded.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.9
  v9.0 CD    9.0.5
  v9.0 LTS   9.0.0.3
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE MP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP