|
Problem IC79886
|
Status: Closed |
THE DB2CONNECTACTIVATE UTILITY WILL NO LONGER REQUIRE THE "DATABASE" TO BE ENTERED IN SPECIFIC CASE. |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
Currently if the value entered for "database" is a location it
is necessary to specify the value in all uppercase characters.
This fix will remove this requirement and alter the
DB2ConnectActivate utility's behavior so that it folds the value
for database name into uppercase characters automatically. |
| Problem Summary: |
Users Affected: DB2ConnectActivate users whose clients connect
to locations rather than single databases on Z/OS Systems.
Problem Description:
Currently if the value entered for "database" is a location it
is necessary to specify the value in all uppercase characters.
This fix will remove this requirement and alter the
DB2ConnectActivate utility's behavior so that it folds the value
for database name into uppercase characters automatically.
Problem Summary:
Currently if the value entered for "database" is a location it
is necessary to specify the value in all uppercase characters.
This fix will remove this requirement and alter the
DB2ConnectActivate utility's behavior so that it folds the value
for database name into uppercase characters automatically. |
| Local Fix: |
Ensure you use all uppercase characters when entering the
database name in the DB2ConnectActivate utility when the
destination is a Z/OS location. |
| available fix packs: |
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 was first fixed in JCC Driver 3.64.82 and 4.14.88
shipped with DB2 Version 9.7 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.11.2011
15.06.2012
15.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
