DB2 FOR LUW / DB2FORLUW / 970 - DB2

While establishing a connection from a client that is DB2 
Version 9.1 Fix Pack 5 or earlier, 
or DB2 Version 9.5 Fix Pack 2 or earlier, via an intermediate 
DB2 instance that is DB2 Version 9.7 Fix Pack 4, 
to a database server that is a recent DB2 version such as DB2 
Version 9 or later on z/OS, you might get the following error: 
 
SQL30021N  Execution failed because of a Distributed Protocol 
Error that will affect the successful execution of subsequent 
commands and SQL statements:    Manager "0x1440" at Level "9" 
not supported.  SQLSTATE=58010 
 
The error does not happen when the client is the IBM Data Server 
Driver for JDBC and SQLJ with Type 4 connectivity. 
 
The error does not happen when the intermediate DB2 instance is 
DB2 Version 9.7 Fix Pack 3a or earlier. 
 
It is on the intermediate DB2 instance that you apply the APAR 
fix to resolve this problem. 
 
The error only happens if the database server is of a version 
that can accept a higher DRDA (Distributed Relational Database 
Architecture) Security Manager level than the database client 
version can accept. 
The error happens because the intermediate DB2 instance 
incorrectly informs the database server to use a Security 
Manager level that is higher than that which the database client 
can accept. 
The DRDA data that the intermediate DB2 instance sends to the 
host includes EXCSAT (Exchange Server Attributes) with MGRLVLLS 
(Manager Level List) with SECMGR (Security Manager) as 9, even 
though the client cannot accept Security Manager level 9. 
If the database server is a version that is high enough to 
accept Security Level 9, the database server then replies with 
Security Manager level 9, and the client returns an error 
because it cannot accept that Security Manager level. 
 
The APAR fix makes the intermediate DB2 instance always send to 
the database server DRDA data with SECMGR (Security Manager) of 
the same level as the client has sent to the intermediate DB2 
instance.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the intermediate DB2 instance to Version 9.7 Fix     * 
* Pack 5 or later.                                             * 
****************************************************************

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 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
 

Problem was first fixed in Version 9.7 Fix Pack 5. 
The fix should be applied on the intermediate DB2 instance.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC83443 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.05.2011
01.11.2011
09.05.2012

9.7.,
9.7.FP5