Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87891 Status: Closed

XA AES CONNECTION TO DB2 Z/OS SERVER GETS SQL30082N RC=17

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
XA connection against DB2 z/os v9.1 CM 
mode server with Advanced Encrpytion (AES) fail with. 
SQL30082N rc=17. The issue can happen when client forces 
reconnect through Syncpoint manager ( SPM). 
 
Impacted release:v9.7.4,v9.7.5,v9.7.6 DB2 Connect Server
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Connect Server                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1.2 or higher fixpack.                        * 
****************************************************************
Local Fix:
catalogging  tcpip loop back or setting registry variable 
DB2CONNECT_IN_APP_PROCESS=NO (then restart instance)
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to v10.1.2 or higher fixpack.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
02.01.2013
02.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList