DB2 - Problembeschreibung
| Problem IC68003 | Status: Geschlossen |
DB2 INSTALLATION COPIES DB2JCC_LICENSE_CUSIZ.JAR AS DB2JCC_LICENSE_CU.JAR OVERWRITING EXISTING DB2JCC_LICENSE_CU.JAR | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problembeschreibung: | |
DB2 installation copies db2jcc_license_cusiz.jar as
sqllib\java\db2jcc_license_cu.jar overwriting existing
sqllib\java\db2jcc_license_cu.jar if db2jcc_license_cusiz.jar
exists in the db2\license directory in the installation
directory.
This may cause unexpected results such as, being able to connect
to remote mainframe systems eventhough a file with name
db2jcc_license_cusiz.jar is not in the CLASSPATH.
Reproduction steps:
1.- Before installation starts:
Copy db2jcc_license_cusiz.jar license file to db2\license
directory under the installable image directory.
2.- Run setup.exe and perform the installation.
3.- The following is observed after installation:
- a file db2jcc_license_cu.jar exists in path:
<db2 directory>\SQLLIB\java
- environment variable CLASSPATH contains
<db2 directory>\SQLLIB\java\db2jcc_license_cu.jar
- CLASSPATH does NOT contain db2jcc_license_cusiz.jar
4.- Test:
Result:
A test JAVA program that connects to a remote db2 mainframe
database using IBM JDBC Type 4 Driver succeed.
Expected result:
An error was expected indicating that connection can not
succeed because there is no valid license
(db2jcc_license_cusiz.jar) to connect to the DB2 on the
mainframe. | |
| Problem-Zusammenfassung: | |
| Local-Fix: | |
Do not copy the db2jcc_license_cusiz.jar file to the db2\license folder in step 1. That way the test on Step 4 will fail until you add the db2jcc_license_cusiz.jar license file to the CLASSPATH. | |
| Lösung | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Kommentar | |
This APAR is a duplicate of IC66619 | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.04.2010 19.09.2011 19.09.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |