|
Problem IC66720
|
Status: Closed |
IF COMMAND EDITOR IS OPENED DIRECTLY USING DB2CE.CMD, THERE ARE NO LOCAL FILE SYSTEMS LISTED WHEN YOU TRY AND OPEN A FILE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When you open the Command Editor directly with the 'db2ce.cmd'
command and then try to open a file, there are no file systems
listed to choose from in the "Look in" drop down area.
The problem occurs when we try to open a file from Command
Editor and there is no DAS is installed with the current DB2
product. This is because we use the DAS to load the local
system. This issue can effect Clients, DB2 Connect PE, and
Server Products that do not have a DAS.
Fix:
In the fix, the code is changed to not use the DAS to load the
Local System while opening a file from Command Editor. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Command Editor users where there is no DAS - affects *
* DB2Clients, Connect PE and Server products where there is *
* noDAS. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When you open the Command Editor directly with *
* the'db2ce.cmd' command and then try to open a file, there *
* areno file systems listed to choose from in the "Look in" *
* dropdown area.The problem occurs when trying to open a file *
* from CommandEditor and there is no DAS is installed with the *
* current DB2product. This is because the DAS is used to load *
* the localsystem. This issue can effect Clients, DB2 Connect *
* PE, andServer Products that do not have a DAS. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 v9.7 FP3, or if a Server product, create a DAS. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
First fixed in DB2 v9.7 FP3 |
| Workaround |
Even though a local DAS does not exist, it is possible to get
the Local System option to display by cataloging a local admin
node. The node will show up in the Control Center list, but
will be pointing to a DAS that does not exist. The Local System
option will be enabled as a result.
Run a command such as:
DB2 CATALOG ADMIN LOCAL NODE LOCALADM |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69862
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2010
30.09.2010
07.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
