DB2 FOR LUW / DB2FORLUW / 980 - DB2

When a multi-threaded DB2 for z/OS application attempts to 
connect to a DB2 LUW V9.5 server, not all threads connect 
successfully. Some threads get the error sqlcode -30020 with 
reason code 124C. 
 
Below messages are written at the db2diag.log file. 
------ 
2010-01-07-10.36.31.726000+540 E1583909H718       LEVEL: Error 
PID     : 1976                 TID  : 3360        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000 
APPHDL  : 0-60240              APPID: 
JPINKA01.FDS43.C55A0ED92D36 
EDUID   : 3360                 EDUNAME: db2agent () 
FUNCTION: DB2 UDB, DRDA Application Server, sqljsParseConnect, 
probe:10 
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected. 
The 
diagnostic 
          data returned is (SRVDGN): "FUNCTION ID = 0183 , PROBE 
POINT = 0010 , 
          TRACE POINT = 0010 , SUBCODE1 = 804B008A, SUBCODE2 = 
00001055, 
          SUBCODE3 = 00000009, ERROR MSG = AGENT: DDM command 
not valid until 
          RDB is accessed". 
. 
2010-01-07-10.36.31.757000+540 I1584629H612       LEVEL: Error 
PID     : 1976                 TID  : 3360        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000 
APPHDL  : 0-60240              APPID: 
JPINKA01.FDS43.C55A0ED92D36 
EDUID   : 3360                 EDUNAME: db2agent () 
FUNCTION: DB2 UDB, DRDA Application Server, sqljsParseConnect, 
probe:10 
MESSAGE : ZRC=0x804B008A=-2142568310=SQLJS_INVRQST 
          "INVALID SQL REQUEST FOR CURRENT STATE" 
DATA #1 : DDM Object, PD_TYPE_DDM_OBJECT, 12 bytes 
 
   data length : 5 
   codepoint   : 0x1055 ( SYNCCTL ) 
   length      : 9 ( COMPLETE ) 
-----

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.8 FP3 or Subsequent Fix Pack                * 
****************************************************************

DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

Problem First Fixed in DB2 Version 9.8 Fix Pack 3

keiner bekannt / siehe Local-Fix

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

18.02.2010
10.12.2012
10.12.2012

9.8.FP3