IBM Support

IT21135: Client trigger monitor runmqtmc on AIX starts application with empty or invalid LIBPATH

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • With the MQ client trigger monitor (runmqtmc) on AIX, after
    applying MQ Version 8.0.0.5 and starting an application the
    LIBPATH is empty in the started application.
    
    This only affects the user if runmqtmc is connected over a
    client channel using SSL/TLS functionality.
    
    The same issue would affect any other application that behaves
    like runmqtmc in this case: that is, it connects to the queue
    manager using SSL/TLS functionality, then starts a second
    application that relies on the value of LIBPATH.
    

Local fix

  • - Change the application to set LIBPATH how it needs it, or
    - Change the APPLICID attribute of the process definition in MQ
    so that it starts your application program via a shell script
    that first corrects the LIBPATH.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    An empty LIBPATH might not cause any issues for your triggered
    application.  But if your triggered application relies on the
    contents of LIBPATH, this issue might result in your application
    loading similar-named libraries from the wrong location.
    
    The issue affects an application that is started by the
    client-bound trigger monitor (runmqtmc) running on an AIX system
    when runmqtmc is connected over a client channel using non-empty
    SSLCIPH.  That is, SSL/TLS function is being used by runmqtmc.
    
    The problem was introduced via changes made in 8.0.0.5.
    
    
    Platforms affected:
    AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Before loading the GSKit libraries that provide the SSL/TLS
    connection, MQ code was setting the LIBPATH in an incorrect way.
    

Problem conclusion

  • The MQ code has been corrected to set the LIBPATH in the correct
    way.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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 number

    IT21135

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-03

  • Closed date

    2017-07-17

  • Last modified date

    2017-07-24

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 July 2017