DB2 FOR LUW / DB2FORLUW / 950 - DB2

DRDA RESYNC request can drive a database connection without 
group/user authorization ID. 
Then later when WLM (Workload Manager) perform workload 
assignment, it will detect 
that no privilege to use for any of the workload 
(as no user id is specified), and it reports a -4707 error 
As for example,  this can happen against a DB2 z/OS  resync 
request to DB2 LUW and the DB2 zOS log will get an error. 
 
The fix is done at DB2 LUW WLM side to skip privilege check when 
it uses RESYNC. 
 
The DB2 zOS  side log will show messages similar to following : 
 
14.56.01 S0021304  DSNV401I  -DP37 DISPLAY THREAD REPORT FOLLOWS 
- 
14.56.01 S0021304  DSNV406I  -DP37 INDOUBT THREADS -  641 
 
641 COORDINATOR STATUS RESET URID AUTHID 
 
641 DP3G COMMITTED 212DAD430D31 LUPBPRD 
 
   641              V467-HAS LUWID <>.<>.C68E8937E346.59F7=53880 
 
   641              V450-HAS PARTICIPANT INDOUBT AT 
 
   641               CLMPRDP1-::FFFF:<ip-address>..50000 
 
   641             DISPLAY INDOUBT REPORT COMPLETE

**************************************************************** 
* USERS AFFECTED:                                              * 
* Any user using DRDA connection                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a DRDA connection is tried without a group or             * 
* authorization id then it can receive SQL4707 error from DB2  * 
* LUW.                                                         * 
*                                                              * 
* An example of similar connection could be, some DB2 zOS      * 
* application is trying to connect to a DB2 LUW database.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users can upgrade to DB2 9.5 fix pack 9 or higher to avoid   * 
* this defect.                                                 * 
****************************************************************

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

First Fixed in DB2 Version 9.5 fix pack 9

keiner bekannt / siehe Local-Fix

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

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

25.07.2011
14.03.2012
14.03.2012

9.0.,
9.5.,
9.5.FP9