DB2 CONNECT / DB2CONNCT / 970 - DB2

When a CLI application with extended diagnostics and 
arrayinputchain enabled runs a SQL query against a DB2 z/OS 
database server when the resource is busy (example: table is 
pending state or out of locks) returns just the SQL0904N error, 
with no REASON CODE AND RESOURCE NAME information. 
or 
When we retrieve the error message from CLI , it may look like 
below text without any reason code or resource name in the 
message. 
SQLGetDiagRec( pszSqlState="57011", pfNativeError=-904, 
pszErrorMsg="[IBM][CLI Driver][DB2] SQL0904N  Unsuccessful 
execution caused by an unavailable resource.  Reason code: "", 
type of resource: "", and resource name: "".  SQLSTATE=57011

**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI users when retrieving the error.                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.9                                 * 
****************************************************************

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

DB2 v9.7 FP9 contains the fix, with this new fix user will the 
error message with appropriate error tokens and reason.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC91794 IC93688 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

15.03.2013
17.12.2013
17.12.2013

9.7.9,
9.7.FP9