home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66720 Status: Geschlossen

IF COMMAND EDITOR IS OPENED DIRECTLY USING DB2CE.CMD, THERE ARE NO LOCAL
FILE SYSTEMS LISTED WHEN YOU TRY AND OPEN A FILE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
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-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69862 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.03.2010
30.09.2010
07.01.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3,
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList