A fix is available
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 8 * * Release 0 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 V800 Infocenter ================ The infocenter for V800 will be updated for this new message: IBM MQ > Reference > Diagnostic Messages > Messages and reason codes for z/OS > Messages > DB2 manager messages (CSQ5...) CCSQ5038I 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. 000Y 001Y 002Y 003Y 004Y 005Y CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU CSQF5DIC CSQF5DIE CSQF5DIF CSQF5DIK CSQF5DIU CSQ5MONR
Temporary fix
Comments
APAR Information
APAR number
PI43873
Reported component name
WMQ Z/OS 8
Reported component ID
5655W9700
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-26
Closed date
2015-09-14
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:
UI29614 UI29615 UI29616 UI29617 UI29618 UI29619
Modules/Macros
CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU CSQF5DIC CSQF5DIE CSQF5DIF CSQF5DIK CSQF5DIU CSQ5MONR
Fix information
Fixed component name
WMQ Z/OS 8
Fixed component ID
5655W9700
Applicable component levels
R000 PSY UI29614
UP15/10/07 P F510
R001 PSY UI29615
UP15/10/07 P F510
R002 PSY UI29616
UP15/10/07 P F510
R003 PSY UI29617
UP15/10/07 P F510
R004 PSY UI29618
UP15/10/07 P F510
R005 PSY UI29619
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.
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0"}]
Document Information
Modified date:
14 December 2020