IBM DB2 Universal Database* Version 7.1 for OS/2* FixPak WR21312 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 2002/11/10, | then you must contact IBM support to request an updated version of the | interim fixes instead of installing this FixPak. By doing this, you are | assured that your system is in a consistent state and no interim fixes | are lost. | | Before installing this DB2 for OS/2 FixPak, please ensure that the line | in your CONFIG.SYS file which initializes the HPFS file system is at the | beginning of the file (if HPFS is being used). You can identify this line | by looking for one similar to the following: | | IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:CDE | | If it is not at the beginning of your CONFIG.SYS file, please move it there | before the DB2 FixPak installation. | | Interim fixpaks are not fully supported in the sense that they are not | fully tested and are for temporary use only. The purpose of an interim | is to provide a required fix for a customer in the case where the problem | has a serious enough impact that a customer does not wish to wait for an | official fixpak. Because of this, interim source code is only guaranteed | to be available for debugging purposes until such time as it is superceded | by an official fixpak. Many problems can be analyzed without the source | code specific to an interim build level. Service will provide whatever | assistance it can up to the point where that code is needed for further | progress. In almost all cases it is recommended, and in some cases | required, that a customer upgrade to an official fixpak in order for | problem diagnosis to continue | | Throughout this document X: is used to refer to the cdrom drive into | which the FixPak CD is placed and C:\SQLLIB is where the DB2 products | are installed. +-------------------------------------------------------------------------+ This README file contains information for the following products and components: OS/2 Specific ------------- DB2 Connect Personal Edition, V7.1 DB2 Connect Enterprise Edition, V7.1 DB2 UDB Enterprise Edition, V7.1 DB2 UDB Workgroup Edition, V7.1 DB2 UDB Personal Edition, V7.1 DB2 Application Development Client, V7.1 DB2 Administration Cient, V7.1 DB2 Run-Time Client, V7.1 DB2 Warehouse Manager, V7.1 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.2 Prior to Installation 2.3 Installation Instructions 2.4 Unattended Installation Instructions 2.5 After Installation 2.5.1 Rebinding to non-DRDA DB2 databases 2.5.2 Rebinding to DRDA databases 2.5.3 Rebinding Specific Packages 3. Service 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service For additional information please see the following files: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Installation Notes 2.1 Pre-requisites Before installing this FixPak you must have DB2 UDB V7.1 installed. To determine if the required prerequisites are installed, do the following: -Double-click on the 'Installation Utility' icon in the 'IBM DB2' folder. -Select 'View', 'Installed Products'. -Select the appropriate DB2 product. -Select 'Details', 'Product Status'. The version should be 07.01.00 2.2 Prior to Installation You must stop all database activity before applying this FixPak. To do this, issue the commands: db2stop db2admin stop 2.3 Installation Instructions To start the FixPak install, type X:\DB2\\INSTALL\INSTALL where is the appropriate language directory. You will be presented with a list of products currently installed. Select a product and then select UPDATE from the Action pull-down menu. You must install the FixPak for every product listed (it is not necessary to re-boot after each one, even if the completion message says so, it is sufficient to re-boot after all products have been updated). If you use ODBC applications, re-run the ODBC Installer after re-booting, by double-clicking on the icon. IMPORTANT: Do not select the "Save a backup version?" checkbox. This will not properly backup the changes and restoring from the backup may damage the installed DB2 UDB product(s). 2.4 Unattended Installation Instructions The FixPak install program (INSTALL.EXE) supports unattended installation via a response file. The syntax for this feature is documented in the Quick Beginnings book. A response file (DB2FIXPK.RSP) is provided for your convenience. It can be used without modification. o Each product must be updated separately. o Every DB2 UDB product that is installed on the system must be updated with this FixPak at the same time. You cannot mix service levels between the products. o A /P:"product name" command line parameter is required. The following sample command files are provided with the FixPak for your convenience: DB2CONPE.CMD DB2 Connect Personal Edition DB2CONEE.CMD DB2 Connect Enterprise Edition DB2ENTR.CMD DB2 Universal Database Enterprise Edition DB2WORK.CMD DB2 Universal Database Workgroup Edition DB2PERS.CMD DB2 Universal Database Personal Edition DB2SDK.CMD DB2 Application Development Client DB2ADMCL.CMD DB2 Administration Client DB2RTCL.CMD DB2 Run-Time Client DB2UDBWM.CMD DB2 Database Warehouse Manager 2.5 After Installation Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to rebind your utilities against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of rebinding, outlined below, only needs to be performed once per database. 2.5.1 Rebinding to non-DRDA DB2 databases After applying fixes, you must do the following: db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC db2 terminate Where is the name of a database to which the utilities should be bound. Examine the DB2PATH environment variable to determine the correct path. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. 2.5.2 Rebinding to DRDA databases If you are using DB2 Connect to access host databases, you will also need to bind the new bind files. As above, connect to the host database, and then bind the utilities as follows: HOST COMMAND ===== =================================================================== MVS BIND C:\SQLLIB\BND\@ddcsmvs.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC VM BIND C:\SQLLIB\BND\@ddcsvm.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC VSE BIND C:\SQLLIB\BND\@ddcsvse.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC OS400 BIND C:\SQLLIB\BND\@ddcs400.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC 2.5.3 Rebinding Specific Packages If you wish to bind only the specific .bnd files to the database, issue the following command for each database (where is the name of the bind file, and is the name of your database). db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate 3. Service 3.1 Product and Service Technical Library For a complete and up-to-date source of DB2 information, including information on issues discovered after this readme was published, please go to the following web site: DB2 Product and Service Technical Library: http://www.ibm.com/software/data/db2/library DB2 Universal Database and DB2 Connect Online Support: http://www.ibm.com/software/data/db2/udb/winos2unix/support DB2 Universal Database and DB2 Connect Online Support - Technical Library: http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/techlib.d2w/report 3.2 Customer Support To speak to an IBM representative regarding assistance with this product, please call 1-800-237-5511. Customer support is also provided via Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. (1) CompuServe - To access the forums on CompuServe, execute GO IBMDB2. - If you don't have access to CompuServe, call 1-800-848-8199 for membership information in Canada or the US. (2) Usenet Newsgroup: comp.databases.ibm-db2 - This Internet Newsgroup is a general forum for discussing questions and/or problems encountered using the DB2 family of products. (3) (IBMLink) Talklink OS/2 BBS - To access the forums on IBMLink, go to the OS2BBS section. - If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the US. 3.3 Corrective Service Corrective service can be downloaded electronically from by either: (1) FTP to anonymous server ftp.software.ibm.com. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (e.g. english-us, spanish, german, etc.), and %P is the product name/version (eg. db2os2v71, etc.). (2) Use a Web browser to connect to the DB2 UDB and DB2 Connect Online Support Page at: http://www.ibm.com/software/data/db2/udb/winos2unix/support (3) On CompuServe, execute GO IBMDB2. Then go to the appropriate library to find the FixPak. (4) On IBM PCC BBS (in US), call (919) 517-0001 (in Raleigh, North Carolina) and then type "db2" on the main menu to find the FixPaks. If you do not have access to any of the above locations, please call 1-800-992-4777 to request these FixPaks be sent to you in the mail. For countries other than US and Canada, please contact your local DB2 Customer Service number for assistance in obtaining them. --------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2002. ** ALL RIGHTS RESERVED. ** ***************************************************************************