IV34166: WEBSPHERE MQ QUEUE MANAGER ON AIX ISSUES MESSAGES AMQ6188 AND AMQ7622 AFTER SETTING UP JDBCDB2 OR JDBCORA SWITCH LOAD FILES

WebSphere MQ V7.5 Fix Pack 7.5.0.2
Fix Pack 7.1.0.3 for WebSphere MQ V7.1
WebSphere MQ V7.0 Fix Pack 7.0.1.11
WebSphere MQ v7.5.0.2 Hypervisor for RHEL

APAR status

• Closed as program error.

Error description

• After building jdbcdb2 or jdbcora switch load files and
  configuring a XAResourceManager stanza for the queue manager,
  the following is seen in the error log when starting the queue
  manager:
  
  AMQ6188: The system could not dynamically load the shared
  library '/var/mqm/exits64/jdbcdb2' as the entry point to
  the library, symbol 'MQStart', could not be located within
  the library.  The queue manager will continue without this
  library.
  AMQ7122: WebSphere MQ could not load the XA switch load file
  for resource manager 'MYQM'.
  
  The switch load file (jdbcdb2 or jdbcora) had been built
  without the MQStart entry point, because /tmp was full, and
  the "xlc" linker needed to use space in /tmp.
  

Local fix

• Copy the file xaswit.exp from the WebSphere MQ samp/xatm
  subdirectory to the WebSphere MQ java/lib/jdbc subdirectory.
  If you did not install the WebSphere MQ samples, create a text
  file called xaswit.exp in the java/lib/jdbc subdirectory and
  add to it a single line reading:
  .
  MQStart
  .
    Then modify the Makefile in the java/lib/jdbc subdirectory
  by adding the flag "-bE:xaswit.exp" (without quotation marks)
  to the end of the LINK_OPTIONS value.  Rebuild the jdbcdb2 or
  jdbcora file using the modified Makefile and the queue manager
  should be able to load it without any errors.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users configuring their queue manager to coordinate global
  units of work using Java applications.
  
  Platforms affected:
  AIX
  
  ****************************************************************
  PROBLEM SUMMARY:
  In order to allow the WebSphere MQ classes for Java to perform
  JTA/JDBC coordination, you must compile the jdbcdb2 or jdbcora
  switch load files using the Makefile in the WebSphere MQ
  java/lib/jdbc and java/lib64/jdbc subdirectories.
  
  The Makefile causes the AIX C compiler command "xlc" to run,
  to link together the supplied .o file and the database shared
  libraries.
  
  However, it was found that, when /tmp is full, the "xlc"
  command produced output that did not have the MQStart entry
  point that is necessary to make the library usable by
  WebSphere MQ. Although this problem can be worked around, it
  is difficult to spot that it has happened.
  

Problem conclusion

• To try to avoid the problem, a new exports file has been added
  to the product, and a change has been made to the "xlc" command
  run from the Makefiles in the java/lib/jdbc and java/lib64/jdbc
  subdirectories.  The "xlc" command now reads the new exports
  file to ensure that the correct entry points are added by the
  linker.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.1.11
  v7.1       7.1.0.3
  v7.5       7.5.0.2
  v8.0       8.0.0.6
  
  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

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R700 PSY

     UP