Install fixes for DB2/2 v1.2 (US) and DDCS/2 v2.2 (US) ====================================================== This README file contains information about DB2/2 v1.2 (US) and DDCS/2 v2.2 (US) install fixes that can be found in the file USIN47.ZIP. The file USIN47.ZIP contains all install fixes for DB2/2 v1.2 (US) and DDCS/2 v2.2 (US) since the GA of the products upto March 9, 1995. Pre-Requisites -------------- The fixes in USIN47.ZIP can be applied to the US versions of the install code for the following products : DB2/2 v1.2 (syslevel WR07000) Single-User and Client/Server packages DB2/2 v1.2 (syslevel WR07035) Single-User and Client/Server packages DDCS/2 v2.2 (syslevel WR07000) Single-User and Multi-User Gateway products and DDCS/2 v2.2 (syslevel WR07035) Single-User and Multi-User Gateway products These fixes supercede all install fixes for DB2/2 v1.2 and DDCS/2 v2.2 containing files dated prior to 03-09-95. This install fix pak can be applied over any previously applied install fixes with files dated before 03-09-95, e.g.: JR8226.ZIP - fixes for installing DB2/2 v1.2 and DDCS/2 v2.2 on OS/2 WARP v3.0) USIN35.ZIP - install fixes for DB2/2 v1.2 and DDCS/2 v2.2 upto shippping of Service Pak 7035. Applying the Fixes ------------------ USIN47.ZIP contains the following .ZIP files: INSTSING.ZIP ...fixes for DB2/2 v1.2 Single-User INSTSERV.ZIP ...fixes for DB2/2 v1.2 Client/Server INSTQMDF.ZIP ...fixes for Query Manager Distributed Feature for DB2/2 v1.2 INSTDCSM.ZIP ...fixes for DDCS/2 v2.2 Multi-User Gateway INSTDCSS.ZIP ...fixes for DDCS/2 v2.2 Single-User The files INSTSING.ZIP, INSTSERV.ZIP and INSTQMDF.ZIP contain different versions of the following files: DBCID2.EXE DBINST2.EXE DB2OP.PRF DB2DESK.PRF INSTDCSM.ZIP and INSTDCSS.ZIP contain separate versions of the following files: DBCID2.EXE DDCSINS2.EXE DB2OP.PRF DB2DESK.PRF Unzip the file USIN47.ZIP using PKUNZIP onto a temporary directory on your hard drive. (e.g. pkunzip USIN47.ZIP c:\insttemp) PKUNZIP.EXE can be found on the installation diskette 1 of either DB2/2 v1.2 or DDCS/2 v2.2. NOTE: Before applying the fixes, you may want to backup the install files that will be overwritten. To do so, copy the files corresponding to the ones in the appropriate INSTxxxx.ZIP from destination path to a backup directory. The destination path for the fixes is either the appropriate product installation diskette #1 or c:\os2\install if the product has already been installed (where c: is the boot drive). To apply the fixes to the product diskettes issue the following command from the temporary directory containig the INSTxxxx.ZIP files: pkunzip -o INSTxxxx.ZIP a: where, -INSTxxxx is the .ZIP file for the appropriate package (e.g. use INSTSING.ZIP for DB2/2 v1.2 Single-User package) -drive a: contains the installation diskette #1 for the package to which the fixes are to be applied. This overwrites the files on the installation disk #1 of the appropriate package with the files contained in the corresponding INSTxxxx.ZIP. If the product has already been installed, the fixes can be applied to the directory c:\os2\install (where c: is the boot drive). To apply the fixes to this path, follow the instructions for applying the fixes to product diskettes using the destination path c:\os2\install instead of drive a:. If you have the product on CD-ROM, you will first have to create product diskettes and then apply the fixes to the diskettes as described above. Another workaround for users who have the product on CD-ROM is to copy the entire contents of the required INSTALL directory to a temporary directory on your hard drive. (For DB2/2 you must also copy the sub- directory EPW and its contents.) For example: xcopy g:\INSTALL\DB22\*.* c:\db22temp /s /v where, G: is the CD-ROM drive. After copying the contents of the install directory on the CD-ROM to your hard drive, apply the fixes to the temporary directory and install the product from there. Applying the fixes to the temporary directory is similar to applying the fixes to product diskettes- use the path for the temporary directory as the destination instead of drive a:. For example: pkunzip -o INSTxxxx.ZIP c:\db22temp Descriptions of Fixes --------------------- APAR JR08226: Installation on WARP fails This fix solves a problem for installing DB2/2 v1.2 and DDCS/2 v2.2 on OS/2 WARP (v3.0). The DB2/2 version 1.2.0 and DDCS/2 v2.2.0 could only be installed on OS/2 2.0 and 2.1. This fix enables the installation of DB2/2 v1.2 and DDCS/2 v2.2 on an OS/2 release later than 2.1. APAR JR08172: SQLSYSTM/DB2SYSTM file not migrated after install. When installing DB2/2 v1.2 over a previous DB2/2 release the old configuration values were not migrated, instead the workstation was configured with default values. During a CID install, using the keyword DBUpdateType=2 could result in the installation of a different workstation type than the one previously installed. This fix ensures migration of old configutation values while installing DB2/2 v1.2 over a previous DB2/2 release. APAR JR08352 No FFST folders after installation Previously, the FFST folder may be removed during installation if CM/2 1.11 was already installed on the system. This problem has been fixed. Trailing blanks in response file cause error Leading or trailing blanks for the keyword DBWorkStationName in the CID response file caused validation error during installation. This problem has been fixed. Install fails when IBMLVL.INI file has a non-existant IBM_DB/PATH DB2/2 installation failed with the following errors if the IBMLVL.INI file had IBM_DB/PATH pointing to disk drive that did not exist: DBI0021E Invalid path or file name DBI0019E Unexpected Presentation Manager error This could occur after the following chain of events: - DB2/2 was installed (on drive x: for instance) - DB2/2 was then manually moved to another drive (i.e. without performing a re-install) - The old install drive (x:) was removed so it was no longer recognizable to OS/2 - An install or re-install of DB2/2 was initiated A fix has been implemented for this problem. CID install fails, yet install returns good CID return code Previously, if errors were encountered during a CID install the install program indicated a successful installation instead of returning a install failed error code. This problem has been fixed to display an install failed message if errors are encountered during a CID installation. DDCS install removes DB2 install files from \OS2\INSTALL Previously, DB2/2 install files were removed from the \OS2\INSTALL directory on the workstation's boot drive during DDCS/2 install. This forced DB2/2 users to run DBINST from original product diskettes to remove or re-install DB2/2. This problem has been fixed to prevent the removal of DB2/2 install files during DDCS/2 installation. Install fails on Warp with PCMCIA cards Previously, when installing on a machine with a PCMCIA slot, scrolling through all available drives for install sometimes resulted in a "Drive not Ready" error for the drive letter representing the PCMCIA drive. This problem has been fixed by only displaying drives that are writeable. Unformated, read-only or removable drives that are not ready are not displayed in the list of available drives. *********************************************************************** ** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1995. ** ** ALL RIGHTS RESERVED. ** ** ** ***********************************************************************