IBM DB2 Universal Database* Version 6.1 for OS/2* FixPak WR21301 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 04/01/2002, | then you must contact IBM support instead of installing this FixPak, to | request an updated version of the interim fixes. 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, please move it there | before the DB2 FixPak installation. | | 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, V6.1 DB2 Connect Enterprise Edition, V6.1 DB2 Universal Database Enterprise Edition, V6.1 DB2 Universal Database Workgroup Edition, V6.1 DB2 Universal Database Personal Edition, V6.1 DB2 Software Developer's Kit, V6.1 DB2 Administration Cient, V6.1 DB2 Run-Time Client, V6.1 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.1.1 Prerequisites for APAR IX73249 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 2.5.4 Rerun db2classes.exe 3. Miscellaneous 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service 3.4 Java Method Signature in PARAMETER STYLE JAVA procedures and functions 3.5 Stored Procedures with PROGRAM TYPE MAIN 3.6 MIN_DEC_DIV_3 Database Configuration Parameter 3.7 Release Notes Changes * 3.8 Loss of Control Center Functionality 3.9 Building Java Applets and Applications For additional information please see the following files: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT * In addition to the release notes changes specified in this section, there is now an additional release note file, Release2.txt, located in the same path as this readme. =========================================================================== 2. Installation Notes 2.1 Pre-requisites Before installing this FixPak you must have DB2 UDB v6.1 installed. To determine if the required pre-requistes are installed, do the following: -Double-click on the 'Installation Utility' icon in the 'DB2 for OS/2' folder. -Select 'View', 'Installed Products'. -Select the appropriate DB2 product. -Select 'Details', 'Product Status'. The version should be 06.01.00 2.1.1 Prerequisites for APAR IX73249 Incorrect Output for DB2 LIST DCS APPLICATIONS SHOW DETAIL The MVS APAR PQ11645 must be applied in conjunction with DB2 Connect APAR IX73249 in order to provide the meaningful correlation token display on both the LIST DCS APPLICATIONS and the DB2 MVS DSP THD commands. 2.2 Prior to Installation You must stop all database activity before applying this FixPak. Stop all applications and 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). This will be remedied in the future. 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 DB2UDBEE.CMD DB2 Universal Database Enterprise Edition DB2UDBWE.CMD DB2 Universal Database Workgroup Edition DB2UDBPE.CMD DB2 Universal Database Personal Edition DB2SDK.CMD DB2 Software Developer's Kit DB2ADMCL.CMD DB2 Administration Client DB2RTCL.CMD DB2 Run-Time Client 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. If is a DB2 v1.x database, do not bind db2cli.lst. Instead, use the db2cliv1.lst or specifically bind db2clics.bnd, db2cliur.bnd, db2clirr.bnd, and db2cliv1.bnd individually. 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 2.5.4 Rerun db2classes.exe on the web server Rerun db2classes.exe on the web server If the Control Center was served as an applet using the V6.1 GA of DB2 UDB on Win32 platforms, after installing the fixpak you must re-run db2classes.exe on the web server. 3. Miscellaneous 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, use the Product and Service Technical Library on the World Wide Web at: http://www.software.ibm.com/data/db2/library 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 by either: (1) FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66. 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. db22v61, db2aixv61, etc.). (2) Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page at: http://www.software.ibm.com/data/db2/db2tech/index.html (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-237-5511 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. 3.4 Java Method Signature in PARAMETER STYLE JAVA procedures and functions If specified after the Java method name in the EXTERNAL NAME clause of the CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature must correspond to the default Java type mapping for the sql signature specified after the procedure or function name. For example, the default Java mapping of the SQL type INTEGER is 'int', not 'java.lang.Integer'. If the signatures do not match, and exception will be raised when the procedure or function is invoked. 3.5 Stored Procedures with PROGRAM TYPE MAIN To ensure family compatibility, PROGRAM TYPE MAIN stored procedures have been changed to pass in the procedure name as the first argument (ie, argv[0]). Existing PROGRAM TYPE MAIN stored procedures can be changed to use this feature by incrementing the indices used to access the argv[] argument array. Alternatively, the original behaviour of PROGRAM TYPE MAIN for Version 6.1 can be restored by turning on the registry variable DB2_RESTORE_PTMAIN_BEHAVIOUR 3.6 MIN_DEC_DIV_3 Database Configuration Parameter The addition of the MIN_DEC_DIV_3 database configuration parameter is provided as a quick way to enable a change to computation of the scale for decimal division in SQL. It is possible that this may not continue as this exact same database configuration parameter in the future. Default=NO. Values: YES, NO. This db cfg parameter changes the resulting scale of a decimal arithmetic operation involving division. If the value is NO, the scale is calculated as 31-p+s-s' (see SQL Reference, Chapter 3, "Decimal Arithmetic in SQL"). If set to YES, the scale is calculated as MAX(3, 31-p+s-s'). This causes the result of decimal division to always have a scale of at least 3 (precision is always 31). Attention: Changing this db cfg parameter may cause changes to applications for existing databases. This can occur when the resulting scale for decimal division would be impacted by changing this db cfg parameter. Here are some possible scenarios that may impact applications. A view that was defined in an environment with one setting could fail with SQLCODE -344 when referenced after the db cfg parameter was changed to the other setting if the resulting scale of one of the view columns is changed. The message SQL0344N refers to recursive common table expressions, however, if the object name (first token) is a view, then you will need to drop the view and create it again to avoid the error. A static package will not change behaviour until the package is rebound, either implicitly or explicitly. For example, after changing from NO to YES, the additional scale digits may not be included in the results until rebind occurs. For any static packages that may experience this change, an explicit rebind command can be used to force a rebind. A check contraint involving a decimal division may restrict some values that were previously accepted by the check constraint. Such rows now violate the constraint but will not be detected until the one of the columns involved in the check constraint row is updated or SET INTEGRITY with IMMEDIATE CHECKED is processed. To force checking of such a constraint, ALTER TABLE to DROP the check constraint and then ALTER TABLE to ADD the constraint again. If any of these scenarios are possible on a database server with existing databases, the implications of changing the MIN_DEC_DIV_3 setting should be carefully considered. Also Note: there are no new message text for this parameter in the v6 or v71 timeframe. This implies the following two limitations: 1) The command "GET DB CFG FOR " will not display the MIN_DEC_DIV_3 setting. The best way to determine the current setting is to observe the side-effect of a decimal division result. For example, if the following db2 statement: VALUES (DEC(1,31,0)/DEC(1,31,5)) Returns sqlcode sql0419n, then the database does not have MIN_DEC_DIV_3 support or it is set to OFF. But if the statement returns "1.000", then MIN_DEC_DIV_3 is ON. 2) The command "? UPDATE DB CFG" displays a list of "config-keywords". MIN_DEC_DIV_3 does not appear in the list. 3.7 Release Notes Changes In section 5.3 of the DB2 Universal Database Version 6.1 Release Notes, "Building Java Applets and Applications", in the paragraph beginning with "On Windows platforms, the JDBC applet server, the db2jd listener, can be...", the sentence: "This is not very convenient when you want it to start automatically. DB2 now provides a new db2set environment variable, DBJD_PORT_NUMBER. By setting this variable to a port number of your choice, every time db2jd is started without a port number passed in from the command line, this port number will be used." contains an error. Change the name of the environment variable DBJD_PORT_NUMBER to DB2JD_PORT_NUMBER. 3.8 Loss of Control Center Functionality There should be no problems introduced against downlevel Control Center clients by applying this fixpak to a DB2 server. However, the next refresh of DB2, version 7.2, will break downlevel Control Center clients - the CC will lose nearly all functionality. Downlevel in this case refers to any version 6 client prior to fixpak 6, and any version 7 client prior to fixpak 2. Version 5 clients are not affected. The suggested fix is to upgrade any affected clients. Version 6 clients must be upgraded to fixpak 6 or later, and version 7 clients must be upgraded to fixpak 2 or later. 3.9 Building Java Applets and Applications If you are using IBM JDK 1.1.8 on supported platforms to build SQLJ programs, a JDK build date of November 24, 1999 (or later) is required. Otherwise you may get JNI panic errors during compilation. If you are using IBM JDK 1.2.2 on supported platforms to build SQLJ programs, a JDK build date of April 17, 2000 (or later) is required. Otherwise, you may get Invalid Java type errors during compilation. --------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** ALL RIGHTS RESERVED. ** ***************************************************************************