IBM Support

IT27773: Allow dynamic tracing of LDAP client library code shipped with IBM MQ

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

  • Allow dynamic tracing of LDAP client library code shipped with
    IBM MQ.
    
    Before this APAR an environment variable must be set before the
    queue manager is started, which causes LDAP trace to be "on"
    permanently until the queue manager is ended, so it is not
    possible to switch the LDAP trace on and off while the queue
    manager is running.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who are working on a problem with IBM support, and there
    is a need to capture a trace of the logic within the LDAP client
    library.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    It was not possible to switch the LDAP client trace on and off
    without also stopping/starting the queue manager.
    

Problem conclusion

  • After this fix, it is possible to switch the LDAP client trace
    on and off without also stopping/starting the queue manager.
    
    This command can be used to switch on the trace:
    
      strmqtrc -m QMNAME -t servicedata
    
    To enable this behaviour, it is also necessary to set an
    environment variable AMQ_LDAP_TRACE to a non-null value.  When
    this is done, and the LDAP functionality is used, some queue
    manager processes will create 0-length files under
    /var/mqm/trace.
    
    Later, when the trace is switched on via the strmqtrc command,
    some trace information will be written to these files.
    
    Later, when trace is switched off via the endmqtrc command,
    trace information will cease to be written to the files, but
    handles to the files will remain open until the queue manager
    ends.  On Unix platforms, note that filesystem space cannot be
    released completely simply by unlinking these files with the
    "rm" command.  This is a side-effect from the fact that the
    handles remain open.  Therefore, a queue manager end should be
    performed, whenever disk space in /var/mqm/trace must be
    released.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.14
    v9.0 LTS   9.0.0.9
    v9.1 CD    9.1.4
    v9.1 LTS   9.1.0.4
    
    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

    IT27773

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-15

  • Closed date

    2019-09-27

  • Last modified date

    2019-09-27

  • 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

[{"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:
27 September 2019