PM92437: WMQ 7.1.0: MQCMIT AND MQQUEUEMANAGER.DISCONNECT() FOR MQ JAVA UNDER CICS GET MQJE001: COMPLETION CODE '2', REASON '2298'

APAR status

• Closed as duplicate of another APAR.

Error description

• A CICS MQ Java application calls MQQueueManager.disconnect().
  The dfhjvmerr file has this error:
  
  com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason
  '2298'.
          at
  com.ibm.mq.StoredManagedConnection.connectionClosed(StoredManage
  dConnection.java:364)
          at
  com.ibm.mq.MQManagedConnectionJ11.fireConnectionClosedEvent(MQMa
  nagedConnectionJ11.java:807)
          at
  com.ibm.mq.MQQueueManager.disconnect(MQQueueManager.java:1636)
         at
  com.ibm.mq.MQQueueManager.disconnect(MQQueueManager.java:1595)
          at
  ...
  
  As part of disconnect processing,
  StoredManagedConnection.connectionClosed() calls MQCMIT. The
  MQCMIT call gets UnsatisfiedLinkError because the native method
  com/ibm/mq/jmqi/local/internal/base/Native.MQCMIT doesn't exist
  in the CICS native library.  This is converted to reason code
  2298 MQRC_FUNCTION_NOT_SUPPORTED. Back in the connectionClosed
  method, this reason code isn't considered acceptible so it is
  rethrown to the application. The disconnect call fails with
  com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason
  '2298'.
  
  The same call with WMQ 7.0.1 results in reason code 2012
  ( MQRC_ENVIORNMENT_ERROR ).
  
  Additional Symptom(s) Search Keyword(s):
  MQJE001 RC2298 000008FA CICS Transaction Server TS
  

Local fix

• For a CICS application, you can remove MQQueueManager.disconnect
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Problem summary:
  
  A CICS Java application uses the MQ classes for Java to access
  MQ V7.1.0.
  
  If the application issues a disconnect call on the
  MQQueueManager object, then an MQException is produced with
  reason code MQRC_FUNCTION_NOT_SUPPORTED (2298).
  
  com.ibm.mq.MQException: MQJE001: Completion Code '2',
     Reason '2298'.
      at com.ibm.mq.StoredManagedConnection.
       connectionClosed(StoredManagedConnection.java:365)
      at com.ibm.mq.MQManagedConnectionJ11.
       fireConnectionClosedEvent(MQManagedConnectionJ11.java:807)
      at com.ibm.mq.MQQueueManager.
       disconnect(MQQueueManager.java:1636)
  
  The issue is caused by MQCMIT and MQBACK calls returning the
  unexpected reason code MQRC_FUNCTION_NOT_SUPPORTED when called
  in CICS.
  MQQueueManager.disconnect() does not expect this reason code,
  and so it does not correctly handle the exception.
  
  Problem resolution:
  
  The MQ native library has been altered to return the
  appropriate reason code (2012 - MQRC_ENVIRONMENT_ERROR) when
  MQCMIT or MQBACK are called in a CICS environment.
  MQQueueManager.disconnect() is able to handle this reason code,
  allowing the call to complete without error.
  
  
  This fix changes the native libraries in the Java component
  of MQ, and will be included in a FixPack APAR.
  
  
  The fix is targeted for delivery in the following PTFs:
  
  Version Maintenance Level
  v7.1 7.1.0.5 (PM96881 on z/OS)
  
  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
  

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

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels