IBM Support

IT01972: QUEUE MANAGER TRACE IS TURNED OFF FOR AN APPLICATION THREAD WITH MULTIPLE SHARED CONNECTIONS AFTER AN MQDISC CALL IS ISSUED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When tracing an application where multiple shared connections
    are used on a single thread, trace is ended for that thread
    immediately after an MQDISC call without considering the other
    active shared connections on the thread.
    
    The above issue can be recreated by writing a simple MQ client
    single threaded application which calls the MQI functions in the
    following order,
    1. Thread1, Connect_options.Options |= MQCNO_HANDLE_SHARE_BLOCK;
    2. Thread1, MQCONNX with Hcon1
    3. Thread1, MQCONNX with Hcon2
    4. Thread1, MQDISC with Hcon1
    5. Thread1, MQDISC with Hcon2
    
    The queue manager trace captured for the above activity will not
    have the second MQDISC captured since the tracing would have
    been turned off for the entire thread immediately after the
    first MQDISC.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ who wish to capture queue manager trace on
    applications which use multiple shared connections.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an application is using multiple shared connections
    (SHCONN) on a single thread, it is expected that all the MQI
    calls issued on each of the shared connection be traced when the
    queue manager tracing routine is turned on. Due to a bug in
    queue manager tracing code, the tracing was being turned off for
    the thread immediately after the first MQDISC call was issued.
    This resulted in MQI calls issued on the same thread not being
    traced even when there were other active shared connections
    available on the thread. This is not the correct behavior
    because each of the MQI calls made by an application thread
    should be traced until the tracing routine is turned off.
    

Problem conclusion

  • The MQ tracing routine is modified such that the trace doesn't
    get turned off immediately after an MQDISC call, when there are
    still active shared connections left on the application thread.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.6
    v7.5       7.5.0.5
    v8.0       8.0.0.1
    
    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

    IT01972

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-22

  • Closed date

    2014-06-30

  • Last modified date

    2014-06-30

  • 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

    5724H7241

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
24 September 2021