IBM Support

PI39773: MQ QSG PROCESSING HUNG WHEN DB2 ACTIVE LOGS FILL-UP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 subsystem used with MQ QSG encountered tape allocation
    issues that resulted in active log full situation. There were
    no meaningful error messages issued on MQ joblogs indicating
    this problem in DB2
    The following messages issued to DB2 joblog:
    - DSNJ002I xxx FULL ACTIVE LOG DATA SET
     - DSNJ111E xxx OUT OF SPACE IN ACTIVE LOG DATA SETS
    This caused MQ subsystems to hang and many channel connections
    timeouts
    On MQ CHIN log:
    CSQX599E xxx CSQXRESP Channel MQP3.ESTA ended
    CSQX259E xxx CSQXRESP Connection timed out,
             channel xxxxx.
             connection (xxxxxxxx..)
             queue manager (????) TRPTYPE=TCP
     The APAR will investigate the queue manager monitoring process
    to detect when a server TCB is 'hanging' in DB2 (e.g. due to the
    logging problem).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Queue manager member of a QSG becomes   *
    *                      unresponsive because DB2 is not         *
    *                      responding to MQ requests.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    MQ does not detect that DB2 is not responding or taking long
    time to process MQ requests. MQ does not issue warning messages
    reporting this condition.
    

Problem conclusion

  • MQ has been enhanced to detect that DB2 is unresponsive and
    issues warning message CSQ5038I.
    
    ============== DOC Changes for V710 Infocenter ================
    The infocenter for V710 will be updated for this new message:
    
    WebSphere MQ
      > Reference
        > Messages
          > WebSphere MQ for z/OS messages, completion,
              and reason codes
            > Messages for WebSphere MQ for z/OS
              > DB2 manager messages (CSQ5...)
    
    CSQ5038I csect-name Service task service-task has been
    unresponsive since hh.mm.ss.nnnnnn, check for problems with DB2
    
    Explanation -
    The queue manager has detected a service task service-task
    that is taking too long to process a request that started
    at hh.mm.ss.nnnnnn.
    
    System action-
    Processing continues, but some functions might be unavailable.
    
    System programmer response-
    Investigate if there are any problems with DB2 or RRS that
    prevent them responding to MQ requests. For example, DB2 CTHREAD
    limit has been exceeded or DB2 is running slow because it is
    short of resources like CPU, I/O capacity or storage or DB2 is
    waiting for log space.
    100Y
    101Y
    102Y
    103Y
    104Y
    105Y
    CSQFMTXC
    CSQFMTXE
    CSQFMTXF
    CSQFMTXK
    CSQFMTXU
    CSQF5DIC
    CSQF5DIE
    CSQF5DIF
    CSQF5DIK
    CSQF5DIU
    CSQ5MONR
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI39773

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-23

  • Closed date

    2015-09-15

  • Last modified date

    2015-11-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI43873 UI29620 UI29621 UI29622 UI29623 UI29624 UI29625

Modules/Macros

  • CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU CSQF5DIC CSQF5DIE
    CSQF5DIF CSQF5DIK CSQF5DIU CSQ5MONR
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI29620

       UP15/10/07 P F510

  • R101 PSY UI29621

       UP15/10/07 P F510

  • R102 PSY UI29622

       UP15/10/07 P F510

  • R103 PSY UI29623

       UP15/10/07 P F510

  • R104 PSY UI29624

       UP15/10/07 P F510

  • R105 PSY UI29625

       UP15/10/07 P F510

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 November 2015