Welcome to DB2* for OS/2* v2.1.2 Official Fixpak WR08200 +-- Note: ----------------------------------------------------------------+ | | After installation is complete, you will need to re-bind the DB2 | utilities against all of your databases. Refer to section 2.2 for | details. | | If installing on OS/2 V2, there is a requirement for OS/2 FixPak 108 or | later, containing APAR PJ23417, to be installed. For OS/2 V3, FixPak 24 | or later, containing APAR PJ22651, is required. No FixPak is required | for OS/2 V4. | | For those customers using NetFinity software (check for NFDASD.FLT in | Config.SYS), NetFinity must be updated to include APAR IX61919. | | If you have received interim fixes from IBM support after 09/26/98, | then you should contact IBM support after the FixPak installation, 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. | +-------------------------------------------------------------------------+ For installation instructions please see section 2.1 This README file contains information for the following products and components: OS/2-Specific ------------- IBM DB2 for OS/2 Server (DB2 for OS/2) IBM DB2 for OS/2 Single-User (DB2 for OS/2) IBM DB2 Software Developer's Kit for OS/2 IBM DB2 Client Application Enabler for OS/2 IBM DB2 Administrator's Toolkit for OS/2 IBM Distributed Database Connection Services* Single-User for OS/2 (DDCS Single-User for OS/2) IBM Distributed Database Connection Services Multi-User Gateway for OS/2 (DDCS Multi-User Gateway for OS/2) --------------------------------------------------------------------------- 1. Contents for FixPak 2. Installation Notes 2.1 Information for Installing this FixPak 2.1.1 Pre-Requisites 2.1.2 Installation Instructions 2.1.3 CID Installation Instructions 2.1.4 Enabling and Disabling JDK 1.1 JDBC Support 2.1.5 DB2 Support for ADSM Version 3 Clients 2.2 Rebinding bind files - IMPORTANT 2.2.1 Rebinding to DB2 common server databases 2.2.2 Rebinding to DRDA databases 2.2.3 Rebinding Specific Packages 3. Miscellaneous 3.1 DB2 Family Newsletter 3.2 Customer Support 3.3 Corrective Service For additional information please see the following files: README.TXT APAR.LST ========================================================================== 2. Installation Notes 2.1 Information for Installing this FixPak 2.1.1 Pre-Requisites This FixPak requires one of the following to already be installed on the machine: IBM DB2 v2.1.2 for OS/2 Server IBM DB2 v2.1.2 for OS/2 Single-User IBM DB2 SDK v2.1.2 for OS/2 IBM DB2 CAE v2.1.2 for OS/2 IBM DB2 Administrator's Toolkit v2.1.2 for OS/2 IBM DDCS Single-User v2.3.2 for OS/2 IBM DDCS Multi-User Gateway v2.3.2 for OS/2 2.1.2 Installation Instructions Note: You must stop all database activity before applying this FixPak. To start the FixPak install, type INSTALL on a command line. 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/DDCS product(s). This will be remedied in the future. 2.1.3 CID Install Instructions The FixPak install program (INSTALL.EXE) uses the same syntax and response file keywords as DB2 for OS/2, DDCS for OS/2, SDK for OS/2, and CAE for OS/2. Refer to the installation guide for a description of these keywords. o Each product must be updated separately. o Every product (DB2 for OS/2, DDCS for OS/2, SDK for OS/2, and CAE for OS/2) 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. See the following sample command files on the first FixPak diskette for the exact product titles: DB2SVR.CMD IBM DB2 for OS/2 - Server DB2SU.CMD IBM DB2 for OS/2 - Single-User DB2SDK.CMD IBM DB2 Software Developer's Kit for OS/2 DB2CAE.CMD IBM DB2 Client Application Enabler for OS/2 DDCSMU.CMD IBM DDCS for OS/2 - Multi-User DDCSSU.CMD IBM DDCS for OS/2 - Single-User DB2ADMIN.CMD IBM DB2 Administrator's Toolkit for OS/2 o To aid in this, there is a tool called DB2RESP.EXE. This tool generates the response files to be used during CID installations. 2.1.4 Enabling and Disabling JDK 1.1 JDBC Support Both JDK 1.0 JDBC and JDK 1.1 JDBC drivers are supported, but only one can be active at a given time. By default, the JDK 1.0 JDBC driver is active. To enable support for the JDK 1.1 JDBC driver, do the following after this FixPak has been installed: 1. cd sqllib\jdk11 2. run db2jdk11 To switch back to the JDK 1.0 JDBC driver: 1. cd sqllib\jdk10 2. run db2jdk10 2.1.5 DB2 Support for ADSM Version 3 Clients DB2 | DB2 Server |Planned | DB2 Service| ADSM Service Level Release | Platform |Availability* | Level | ========+============+==============+============+======================= DB2 UDB | AIX 4.1.x |June 30, 1998 | PTF: | ADSM Client V313 V5.0 | | | U457227 | (U454538) | | | | (with AIX41313G patch) --------+------------+--------------+------------+----------------------- DB2 UDB | AIX 4.2.x |June 30, 1998 | PTF: | ADSM Client V313 V5.0 | AIX 4.3.x | | U457227 | (U454539) | | | | (with AIX42313G patch) --------+------------+--------------+------------+----------------------- DB2 UDB | All Other |Sept 30, 1998 | To Be | To Be Determined V5.0 | | | Determined | --------+------------+--------------+------------+----------------------- DB2 | AIX 4.1.x |July 31, 1998 | PTF: | ADSM Client V313 V2.1.2 | | | U458628 | (U454538) | | | | (with AIX41313G patch) --------+------------+--------------+------------+----------------------- DB2 | AIX 4.2.x |July 31, 1998 | PTF: | ADSM Client V313 V2.1.2 | AIX 4.3.x | | U458628 | (U454539) | | | | (with AIX42313G patch) --------+------------+--------------+------------+----------------------- DB2 DB | AIX 4.1.x |July 31, 1998 | PTF: | ADSM Client V313 Server | | | U458629 | (U454538) V4.1.2 | | | | (with AIX41313G patch) --------+------------+--------------+------------+----------------------- DB2 DB | AIX 4.2.x |July 31, 1998 | PTF: | ADSM Client V313 Server | AIX 4.3.x | | U458629 | (U454539) V4.1.2 | | | | (with AIX42313G patch) --------+------------+--------------+------------+----------------------- DB2 | OS/2 |Oct 30, 1998 | To Be | To Be Determined V2.1.2 | | | Determined | --------+------------+--------------+------------+----------------------- DB2 | All Other |None | N/A | N/A V2.1.2 | | | | --------+------------+--------------+------------+----------------------- DB2 PE | AIX |None | N/A | N/A V1.2 | | | | * Note: The planned availability dates for the required DB2 fix packs are subject to change. 2.2 Rebinding bind files - IMPORTANT Due to the new bind (.BND) files that have been shipped with this FixPak, you will need to rebind your DB2 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.2.1 Rebinding to DB2 common server databases After applying fixes, you must do the following: - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND \@db2ubind.lst BLOCKING ALL GRANT PUBLIC db2 BIND \@db2cli.lst BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND \@db2ubind.lst BLOCKING ALL GRANT PUBLIC BIND \@db2cli.lst BLOCKING ALL GRANT PUBLIC TERMINATE Where is the name of a database to which the utilities should be bound, and where is the full path name of the directory where the bind files are located, such as \sqllib\bnd. 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.2.2 Rebinding to DRDA databases If you are using DDCS to connect to host databases, you will also need to bind the new bind files to the host. As above, use the DB2 Command Line Processor to connect to the host database, and then bind the utilities as follows: HOST COMMAND ======= =================================================== MVS BIND \@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VM BIND \@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VSE BIND \@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE OS400 BIND \@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE Please refer to Chapter 4 "Binding Applications and Utilities" of the DDCS User's Guide for a list of what bind files are used for your specific client operating system. If a bind file changes but your clients do not use that bind file, you do not need to re-bind it. 2.2.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). - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND \ BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND \ BLOCKING ALL GRANT PUBLIC TERMINATE 3. Miscellaneous 3.1 DB2 Family Newsletter For the latest information about the DB2 family of products, you may subscribe to the "DB2 Family Newsletter" (English only). Simply send your request in a FAX to 1-905-316-4733, and include the following information: Name Company name Full mailing address Telephone number DB2 products you currently use 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 They can be downloaded electronically from the following locations: (1) CompuServe - Execute GO IBMDB2 - then go to the DB2/OS2 library to find the DB2/OS2 FixPak - or go to the CLIENTS library to find the SDK/Win FixPak. (2) Internet - FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66 - then go to ps/products/db2/fixes// where is (eg. english-us, spanish, german, etc.) is the product name/version (eg. db22v21, db2winv21, etc.) - Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page. (http://www.software.ibm.com/data/db2/db2tech/index.html) (3) IBM PCC BBS (in US) - Call (919) 517-0001 (in Raleigh, North Carolina) - Then type "db2" on the main menu to find the FixPaks The above are the primary locations where these FixPaks are uploaded. They may also be available on other Bulletin Boards (such as the Talklink OS/2 BBS in the US). 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 look at your local IBM OS/2 BBS or call 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 1998. ** ALL RIGHTS RESERVED. ** ***********************************************************************