A fix is available
APAR status
Closed as program error.
Error description
Message dsnt376i for timeout occurred correctly, however the subsequent dsnt408i showed rc00c90088 for deadlock incorrectly. eg DSNT376I -DS53 PLAN=G80865 WITH CORRELATION-ID=0032G80865 CONNECTION-ID=IMS3 LUW-ID=JPxxxxxx.xxxxx.C929CB139F78=156896 THREAD-INFO=FSTCUSR:*:*:* IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=DSNTEP91 WITH CORRELATION-ID=G70M501T CONNECTION-ID=BATCH LUW-ID=JPxxxxxx.xxxxx.C929CB11D016=20427 THREAD-INFO=D5034:*:*:* ON MEMBER DSN5 DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT ->> REASON 00C90088, TYPE OF RESOURCE 00000801, AND RESOURCE NAME Gxxxxxx.G808652.19241B32102EF692 DSNT418I SQLSTATE = 40001 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNXEAAL SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = -130 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 users when running a package. * **************************************************************** * PROBLEM DESCRIPTION: When running a package, customer could * * receive inconsistent messages between * * timeout and deadlock: * * * * - DSNT376I message for timeout. * * - DSNT408I message with SQLCODE = -911, * * and REASON 00C90088, issued by CSECT * * DSNXEAAL for deadlock. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running a package, DB2 could hit a timeout, for example, a DB2 object is changed and all the packages accessing that object could be quiesced until the change to the object is committed. If within a timeout period, the job is not committed, running such a package could return a timeout with -911. Due to a DB2 error, the customer could receive reason code 00C90088 instead of 00C9008E.
Problem conclusion
DB2 code has been changed to issue the correct reason code 00C9008E when package execution fails with time-out. After this apar changes, batch attachments to DB2 will receive a -911 for time outs and deadlocks. Recovery coordinators as CICS and IMS should receive -913 for time outs and deadlocks. Additional keywords: RC00C90088, RC00C9008E, MSGDSNT376I, SQLCODE911, SQLCODE913
Temporary fix
Comments
APAR Information
APAR number
PM61739
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-03
Closed date
2012-06-26
Last modified date
2012-08-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK79823 UK79824
Modules/Macros
DSNGEFLC DSNGEPDL DSNGEPLC DSNXEAAL
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 August 2012