|
Problem IC76020
|
Status: Closed |
SQL3280N ERROR CONNECTING VIA GATEWAY TO MAINFRAME CATALOGED IN LDAP |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
The DB2 client can throw SQL3280N error -"The attempt to connect
to a DRDA server failed", during connect to DB2 on zOS or
iSeries
catalogued in LDAP. This error is thrown because the DB2 client
sees the DCS directory information in LDAP and then checks for a
DB2 Connect license. This can occur even if the license key for
DB2 Connect Unlimited Edition (System z) has been activated on
the mainframe.
The code fix removes this DB2 connect license check . |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Data Server Client users connecting to DB2 for zOS cataloged *
* via LDAP. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Attempt to connect to DB2 for zOS or iSeries from a Data *
* Server Client fails with *
* SQL3280N error -"The attempt to connect to a DRDA server *
* failed", when the database is cataloged via LDAP *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP5 *
**************************************************************** |
| Local Fix: |
Catalog the database locally. |
| available fix packs: |
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
|
| Solution |
Problem fixed in DB2 v9.7 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.04.2011
19.01.2012
19.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
