IBM(R) DB2 Table Editor, Version 4 Release 3, FixPak 3 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected known problems 2.0 PREREQUISITES 2.1 Hardware Requirements 2.2 Software Requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 Updates to Shared Dynamic Link Libraries 3.2 Configuration for Unattended Installation 3.3 Installing the DB2 Table Editor Control Center Plug-in 3.3.1 Installing the DB2 Table Editor Control Center Plug-in on DB2 V7 3.3.2 Installing the DB2 Table Editor Control Center Plug-in on DB2 V8 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 RESTRICTIONS 6.0 CORRECTIONS TO DOCUMENTATION 7.0 HOW TO GET HELP 8.0 NOTICES 8.1 Notices of other companies 8.2 Use of evaluation program 8.3 Trademarks and service marks __________________________________________________________________ 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Table Editor, Version 4 Release 3, FixPak 3 that contains the latest fixes for DB2 Table Editor V4.3. This FixPak is a complete replacement of the product without the License Use Management (LUM) key. IBM DB2 Table Editor has been tested and validated with all supported releases of DB2 Universal Database(TM) through Version 8 Release 1 for Multiplatforms. Subsequent releases might require additional maintenance. This is the most current README file as of 4/25/2003. 1.1 Evaluation code If you are using evaluation code, the evaluation code enables you to try this product for a period of 60 days. After 60-days, you must purchase a license to continue to use the product. When you purchase the product. When you purchase the product, the license is enforced based upon the platform to which you are connecting using IBM DB2 Table Editor. For more information on Licensing see "Licensing" in the DB2 Table Editor User's Guide. Read the NOTICES Section 8.1, USE OF EVALUATION CODE, and the License Agreement provided with your evaluation copy of the program. 1.2 CORRECTED KNOWN PROBLEMS - In DB2 Table Editor Java player, tables containing primary keys can now be updated. - In the Edit Table window, when the Owner field is blank, the search button is disabled until a value is typed in the Owner field. - In Options window, you can no longer use the same character in both the 'Enter null values as' field and the 'Enter default values as' fields. - DB2 Table editor no longer reports columns with indices as Primary tables. - When one DB2 Table Editor user sets 'Enter null values as' to [space], the following message appears when another user attempts to change or delete the row: 'This row has either been changed or deleted by another user and cannot be deleted.' - When the decimal delimiter is set to comma, if you attempt to insert or update to a column with a value such as 19,29, DB2 no longer stores the value as 19.00 - After resizing a form containing a combo box in Windows User, the combo Box will now open properly - In Decimal columns with the thousands separator present, if you insert a duplicate row into a table in the Table Layout, you no longer get a "Internal Application error" message and the row will be updated properly. - In the DB2 Table Editor Developer component, the scroll function (with arrow keys) in the Button Action Attributes window is now enabled - The 'or' connector in Filter window is now working properly. - The error message that occurred when opening a FSE form in DB2 Table Editor Developer has been corrected. - When the Japanese regional option is specified, TIME columns will no longer display the AM/PM symbol regardless of the setting. - Full Screen Edit forms are now saved with .fse file extension in the DB2 Table Editor module. These forms can be saved locally and can only be opened again with the DB2 Table Editor module. - Encrypted columns can now be decrypted by using a decryption password in the DB2 Table Editor module. - Formulas can now be applied in the form layout in the DB2 Table Editor module. To obtain a list of fixes that were included in previous FixPaks, refer to APARs: PQ68972, PQ68971, SA95979, PQ68970, PQ68969, PQ68973, PQ68975, PQ65775, PQ65780, SA95764, PQ65778, PQ65779, PQ65781, and PQ65525. 2.0 PREREQUISITES 2.1 Hardware Requirements Hardware requirements are those needed to run the Windows software as described in 2.2 Software Requirements. DB2 Table Editor has the following requirements: - Approximately 16 MB of free disk space on a Windows machine - A minimum of 32 MB memory. Additional memory improves performance. 2.2 Software Requirements DB2 Table Editor runs on the following operating systems: - Microsoft(R) Windows 95 - Microsoft Windows 98 - Microsoft Windows NT(R) 4.0 - Microsoft Windows 2000 - Microsoft Windows XP 3.0 INSTALLATION INSTRUCTIONS To install DB2 Table Editor: 1. Download the FixPak from the Web: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html Download the file to a temporary directory on the system where the DB2 Table Editor is installed. 2. Browse to the Disk1 directory and double-click setup.exe. The DB2 Table Editor install starts. 3. Follow the steps in the DB2 Table Editor Install wizard. For specific information on items in the install wizard, click the Help button to access the online help. 4. When the installation is complete, start the DB2 Table Editor Console and create a server definition file for each server that you want to access using DB2 Table Editor. For more information on creating a server definition file, see the DB2 Table Editor User's Guide. Note: You must set up server definition files for the servers that you want to access using DB2 Table Editor before you can access these servers using DB2 Table Editor Developer, Windows User, or Java Player. Use the DB2 Table Editor Console to setup server definition files. 5. Bind the DB2 Table Editor packages. 3.1 UPDATES TO SHARED DYNAMIC LINK LIBRARIES DB2 Table Editor installs the Visual C Runtime library (MSVCRT.DLL v4.21.7303) and Microsoft(R) Foundation Classes library (MFC42.DLL v5.00.7303) to the Windows(R) System directory. If you are running on Windows NT(R) 4.0, DB2 Table Editor will additionally install the Microsoft 3D Windows Control Library (CTL3D32.DLL v2.31.000). 3.2 CONFIGURATION FOR UNATTENDED INSTALLATION An unattended installation allows you to select the installation options for your DB2 Table Editor users before beginning the installation process. By using this method you can designate all of the options for multiple installations rather than having to select the same options repeatedly for each individual installation. Use the following steps to enable unattended installation. STEP ONE - Edit setup.ini Using a text editor such as Notepad, edit setup.ini. This file, on Disk 1 of the installation diskettes, controls the installation process and determines the settings used for the installation. The settings you can control are described below. Specify the settings that you want in setup.ini. _____________________________________________________________________________ [Options] Setting Effect AutoInstall= 0,1 Specify 1 to perform an unattended installation. All other settings in setup.ini are ignored if this setting is not 1. FileServerInstall= 0,1 Specifies whether DB2 Table Editor is already installed on a file server. If the settings is 0, all DB2 Table Editor files are installed to the directory specified in the InstallPath variable. If the settings is 1, DB2 Table Editor must be previously installed into the directory specified in the InstallPath variable. To enable a file server installation, you also must set SetupType=2. SetupType= 0,1,2 Specifies the type of installation to perform. 0 indicates a typical installation, 1 indicates a compact installation, 2 indicates a custom installation. If you select 2, you must indicate which components to install. Note: Option 2, the custom installation, is strongly recommended. Most users do not require the Console or Developer. InstallPath= Specifies the directory to receive the DB2 Table Editor installation (if FileServerInstall=0) or the file server directory that already contains the installation (if FileServerInstall=1). ProgramGroup= Specifies the name of the program group to create (under Program Manager) or the program folder to create (for the Windows 95(R), Windows 98(R), and Windows NT(R) 4.0 Start Menu). _____________________________________________________________________________ [Components] Setting Effect Admin 0,1 Specifies whether to install DB2 Table Editor Console. If FileServerInstall=1, files are not copied to the local machine, but program group icons are still created. Always set this option to 0 for user installations. Developer 0,1 Specifies whether to install DB2 Table Editor Developer. If FileServerInstall=1, files are not copied to the local machine, but program group icons are still created. Always set this option to 0 for user installations. _____________________________________________________________________________ Setup.ini example This setup.ini file specifies an unattended installation. A typical installation is performed, copying files to the C:\Programs\DB2 Table Editor directory, and creating a program group or program folder named DB2 Table Editor. [Options] AutoInstall=1 FileServerInstall=0 SetupType=0 InstallPath=C:\Programs\DB2 Table Editor ProgramGroup=DB2 Table Editor STEP TWO - Save setup.ini After you edit and save setup.ini, copy it to Disk 1 of the DB2 Table Editor installation diskettes. STEP THREE - Run DB2 Table Editor Setup Run the installation from the source diskettes or server. The installation proceeds automatically. 3.3 INSTALLING THE DB2 TABLE EDITOR CONTROL CENTER PLUG-IN The DB2 Table Editor Control Center Plug-in is an extension to the DB2 Control Center. For more information about the Control Center, refer to the IBM DB2 Administration Guide. The DB2 Table Editor Control Center plug-in adds DB2 Table Editor menu items to the table pop-up menu and adds a tool bar button to start DB2 Table Editor as an add in tool from the DB2 Universal Database Control Center. 3.3.1 INSTALLING THE DB2 TABLE EDITOR CONTROL CENTER PLUG-IN on DB2 V7 1. Copy the following files and directories to the SQLLIB\cc directory: - db2forms.jar - One or more of the following license files. – dbehost.lic – dbe400.lic - dbework.lic You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. - HtmlHelp Directory (Including all sub folders) By default this directory is SQLLIB\cc. The Control Center requires that these files be located in the Java classpath so that they can be loaded when the Control Center is started. 2. Copy db2plug.v7zip into SQLLIB\cc directory. There are two version of db2plug.zip: db2plug.v7zip and db2plug.v8zip. db2plug.v7zip works with DB2 version 7. 3. Rename db2plug.v7zip to: db2plug.zip NOTE: If there is already another version of db2plug.zip in SQLLIB\cc, you must combine the contents of the existing db2plug.zip and the DB2 Table Editor db2plug.zip. For Example, if you are using the Zip utility, use the following command: zip -r0 db2plug.zip com\rocketsoftware\myplugin\*.class Where the plug-in package name is: com.companyname.myplugin 4. Locate the db2cc file in the SQLLIB\bin. If you are using Windows, the file is named db2cc.bat. If you are using the Unix or Linux, the file is named db2cc. 5. Update db2cc to include both db2plug.zip and db2forms.jar. The file names must follow a -c option. With newer releases of DB2, you must add the -c option. If you are using an older version of DB2 which has the -c option specified in db2cc, you can append the values to the end of the existing -c option. The following is an example of db2cc after you have added the files: IF "%1" == "wait" GOTO WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -o:"-mx128m -ms32m" -a:"%1 %2 %3 %4 %5 %6 %7 %8" GOTO END :WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -w:-o:"-mx128m -ms32m" -a:"%2 %3 %4 %5 %6 %7 %8 %9" GOTO END :end 6. If you are running the DB2 Control Center as a Java applet, complete the following steps: a. Copy the db2forms.jar file where the tag points to in db2cc.htm. b. Update db2cc.htm to include db2plug.zip and db2forms.jar in the archive list. You can now start Table Editor from within Control Center by selecting a DB2 Table Editor menu item from the Table popup menu or the new tool bar button. 3.3.2 INSTALLING THE DB2 TABLE EDITOR CONTROL CENTER PLUG-IN on DB2 V8 1. Copy the following files and directories to the SQLLIB\tools directory: - db2forms.jar - One or more of the following license files. – dbehost.lic – dbe400.lic – dbework.lic You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. - HtmlHelp Directory (Including all sub folders) By default this directory is SQLLIB\tools. The Control Center requires that these files be located in the Java classpath so that they can be loaded when the Control Center is started. 2. Copy db2plug.v8zip, into SQLLIB\tools directory. 3. Rename db2plug.v8zip to: db2plug.zip Note: If there is already another version of db2plug.zip in SQLLIB\tools, you must combine the contents of the existing db2plug.zip and the DB2 Table Editor db2plug.zip. For Example, if you are using the Zip utility, use the following command: zip -r0 db2plug.zip com\rocketsoftware\ccplugin\*.* Where the plug-in package name is: com.rocketsoftware.ccplugin 4. If you are running the Control Center as a Java applet, complete the following steps: a. Copy the db2forms.jar file where the tag points to in db2cc.htm. b. Update db2cc.htm to include db2plug.zip and db2forms.jar in the archive list. You can now start Table Editor from within Control Center by selecting a DB2 Table Editor menu item from the Table popup menu or the new tool bar button. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use DB2 Table Editor, refer to DB2 Table Editor for Multiplatforms User's Guide. If you received your copy of DB2 Table Editor electronically,locate the User's Guide here: http://www.ibm.com/software/data/db2imstools/library.html If you are installing this image from a CD-ROM, the documentation is located in /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. 5.0 RESTRICTIONS The following are the restrictions to the DB2 Table Editor functionality in Version 4.3 FixPak 3: - Long names are only supported when connecting to a new DB2 (Workstation V7 or later or iSeries V5R1 or later) database when no earlier version of DB2 Table Editor and no version of QMF is being used to access the database. - ODBC connectivity can only be used to connect to Informix Databases. - In order to run the DB2 Table Editor Java Player against a DB2 V8 database, you must use Java 2. - LOBs cannot be inserted when you are using a shared or an exclusive lock. - When accessing the DB2 Table Editor functionality through DB2 Web Query, on AIX, you can only update a primary key once per DB2 Web Query session. - DB2 Web Query V1.3 Fixpak 3 or higher is required when using Netscape Navigator to access the DB2 Table Editor functionality through DB2 Web Query. - When working with Informix databases, only CHARACTER data can be inserted into FOR bit data, LONGVARCHAR columns. - When working with Informix databases, primary key columns are treated like regular columns. - LOB controls are not available when connecting to an Informix server, when using the DB2 Table Editor Java player, or when using the DB2 Table Editor Control Center Plugin. - As stated in the DB2 Universal Database Release notes (for Multiplatforms): "For version 8 clients to work with version 7 servers, you need to configure and enable the use of DRDA(R) application server capability on the version 7 server. For information on how to do this, refer to the [DB2 Universal Database] version 7 Installation and Configuration Supplement. When accessing version 7 servers from version 8 clients, there is no support available for Some data types: * Large object (LOB) data types * User-defined distinct types * DATALINK data types" You cannot use CLI connectivity to connect using a DB2 Universal Database Version 8 client (for Multiplatforms)to a DB2 Version 7 database. - When defining an Informix server using the DB2 Table Editor Console component, a catalog server must be used. - Binary data cannot be read when reading data from an Informix server. Text files are supported. - In Java implementations of DB2 Table Editor (as an applet), the applet will hang if you attempt to open multiple applets at once if J2SDK 1.4.0 is installed. If you are using Microsoft Internet Explorer with the SUN Java JVM V1.4, you must upgrade to V 1.4.1_02. - If you have thousands separator and you use the 'Find' command you need to check 'match whole word only box' in order to find what you are searching for. - In order to insert 100 or more rows at a time you must change the following values in your Server Definition (SDF) file. NumDynamicSectionsForCall=100 NumDynamicSectionsWithHold=100 NumDynamicSectionsWithoutHold=100 In the example above the value of 100 indicates the number of rows that can be inserted at a time. Change this number to the number of rows that you want to insert. The maximum allowable value here is 999. - In the DB2 Table Editor Console, all creator names must be 8 characters or shorter. 6 .0 CORRECTIONS TO DOCUMENTATION To obtain the latest refresh of DB2 Table Editor publications refer to: http://www.ibm.com/software/data/db2imstools/library.html In the Concepts section of the Online help, the section on ODBC Data Sources should read as follows: ODBC Data Sources DB2 Table Editor references ODBC data sources by their Data Set Name (DSN). Most data sources can be accessed by DB2 Table Editor as long as the particular ODBC data source drivers are available. A user ID and password are required to make the connection if it is required by the ODBC data source. The following data sources have been tested using an ODBC connection: -Informix 7.0 HOW TO GET HELP For a complete and up-to-date source of DB2 Table Editor information, including information on issues discovered after this readme was published, go the to following websites: DB2 Table Editor Online Support: http://www.ibm.com/software/data/db2imstools/support.html If you are not able to find your answer searching the listed URLs, call 1-800-IBM-SERV to speak to an IBM representative for assistance. In the DB2 Table Editor install help, the following note should be added to step one in: - To run the DB2 Table Editor Java Player application via an applet: - To run an individual DB2 Table Editor form via an applet: "Note: If you connecting to a DB2 V8 database, the applet code section should be as follows: " 8.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is as your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. 8.1 Notices of other companies XMLParser.Java, AELfred, Version 1.1: AElfred, Version 1.1 Microstar's Java-Based XML Parser Copyright (c) 1997, 1998 by Microstar Software Ltd. Home page: http://www.microstar.com/XML/ Licensing Terms: "AElfred is free for both commercial and non-commercial use and redistribution, provided that Microstar's copyright and disclaimer are retained intact. You are free to modify AElfred for your own use and to redistribute AElfred with your modifications, provided that the modifications are clearly docuented." Disclaimer: "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of merchantability or fitness for a particular purpose. Please use it AT YOUR OWN RISK." WFC XMLParser (C++) "I'm just a simple little NT programmer. Most of the work I do is remote controlling equipment in real time. I started out using Windows 30. Then came Windows 3,1 and then NT. I started using NT but unfortunately, Microsoft didn't. I started using MFC but unfortunately, Microsoft didn't (and still doesn't) put any real support for NT into MFC so I wrote a bunch of C++ classes to make my life easier. Like all class libraries, mine grew. Now I'm giving it away. I call it Win32 Foundation Classes." 8.2 Use of evaluation program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement for a complete explanation of the terms that apply. 8.3 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: AIX DB2 DB2 Universal Database IBM Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2001, 2002; Copyright Rocket Software, Inc., 2001.2002. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.