Welcome to DB2* for the SINIX** Operating Environment Version 2.1.2 U458632 +--- NOTE! ----------------------------------------------------------+ | | Set the font to monospace for better viewing of this README. | | If you have received interim fixes from IBM support after 98/06/27, | 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. | +--------------------------------------------------------------------+ This README file contains information for the following products and components: IBM DB2 for SINIX Server (DB2 for SINIX) IBM DB2 Client Application Enabler for SINIX IBM DB2 Software Developer's Kit for SINIX IBM Distributed Database Connection Services* Multi-User Gateway for SINIX (DDCS for SINIX) ------------------------------------------------------------------------ 1. Contents for FixPak 2. Before You Install 2.1 Required Patch Level for DB2 for SINIX 2.2 Disk Requirements 2.3 Product Location for DB2 for SINIX 2.4 Upgrading Considerations 2.5 Rebinding bind files - IMPORTANT 2.5.1 Rebinding to DB2 common server databases 2.5.2 Rebinding to DB2 DRDA databases 2.5.3 Rebinding Specific Packages 2.6 Nodelock License Key File 2.7 Locales Supported 2.8 APAR IX69806 Information 3. Miscellaneous 3.1 DB2 Family Newsletter 3.2 Customer Support 3.3 Corrective Service Additional information that you may require can be found in the "DB2 Release Notes" or "DDCS Release Notes". Read this information by viewing or printing the "README" or DDCSREAD.TXT" files. One or both of these files are located in the "/opt/IBMdb2/V2.1/Readme/%L" directory. ======================================================================== 2 Before You Install 2.1 Required Patch Level for DB2 for SINIX When running DB2 for SINIX on SINIX-Y Version 5.42, you must install the patch V5.42A10 or later. 2.2 Disk Requirements The following table shows the amount of space you need to install DB2 products: Disk space Product required (in MB) ======= ================ DB2 CAE 16 DB2 SERVER 42 DB2 SDK 21 DB2 DDCS 40 CAE+SERVER+SDK+DDCS 47 English PostScript docs 21 German PostScript docs 13 2.3 Product Location for DB2 for SINIX The base directory for all DB2 for SINIX products and packages must be the same. The default base directory is "/opt". 2.4 Upgrading Considerations If you have a current DB2 V2.1.x installed on your system and wish to upgrade to version 2.1.2, you must follow these steps: A. Remove all existing versions of DB2 products. (An older version of the product may conflict with this version.) Use the pkgrm command to remove any of the DB2 for SINIX software products. Before removing a package using the pkgrm command, all its dependent packages must be removed first. You must remove packages in the following order: 1. db2ps%L 2. db2csrte 3. db2sdkcob 4. db2sdkmsc 5. db2sdkcli 6. db2sdkc 7. db2ddcs 8. db2misc 9. db2rte 10. db2clp 11. db2conv 12. db2msgDe 13. db2cliv21 To determine all the DB2 for SINIX packages installed on your system, enter the following command: pkginfo | grep -i db2 B. Remove the links that may have been previously created by "db2ln" by using the "db2rmln" command as follows: /opt/IBMdb2/V2.1/cfg/db2rmln To delete the DB2 products, login as root and type /usr/bin/pkgrm either with or without arguments. You can enter names of the packages as arguments to the "pkgrm" command. However, you must enter the package names in the order described in step 3. For example, if installed, you can remove the packages db2psen, db2inen, db2csrte, db2csipx, db2csdrda, and db2cssna using the following command: /usr/sbin/pkgrm db2psen db2inen db2csdrda db2cssna db2csipx db2csrte If you enter pkgrm without arguments, a menu will be displayed to guide you through the procedure. To remove all the DB2 for Solaris products that are installed on your system, do the following: a) Type: pkgrm b) Type the package number of the package you want to remove. c) Select yes to remove the package. C. Install DB2 Version 2.1.2 using the procedure described in the Installation and Operation Guide. D. For each instance on the machine run the command: /opt/IBMdb2/V2.1/instance/db2iupdt instance (where instance is the name of the instance. You can get a list of all the instances on the machine by issuing the /opt/IBMdb2/V2.1/instance/db2ilist command) 2.5 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.5.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.5.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.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). - 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 2.6 Nodelock License Key File The location of the nodelock file is incorrect in the printed manuals. The nodelock license key file can be found as: /usr/netls/nodelock 2.7 Locales Supported DB2 supports the following locales: De_DE.88591, En_US.ASCII, En_GB.88591, POSIX, and C. Other ASCII (codepage 646) locales and codepage 6937 locales are not supported. 2.8 APAR IX69806 Information In order to use the fix for APAR IX69806, the keyword "PATCH2=7" (without the quotes) needs to be added to DB2CLI.INI under the data source section. Note that this APAR needs to be applied to handle graphic data type correctly in double byte environments when using certain applications. 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-CALL-AIX (1-800-225-5249). 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 location: (1) 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, db2aixv21, 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) If you do not have access to any of the above locations, please call 1-800-CALL-AIX (1-800-225-5249) 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. ** ***********************************************************************