hotfix_22318 ============ 1) The identifier for this special build is 22318 It has been delivered through PMR 89990 branch 49R The fix is built on top of version 9.5 fixpak 0 build SQL09050. This build can be applied only on the above level of code. This build will be supported for 90 days after the release of the official fixpack containing the APAR(s). Please note that IBM recommends that you put this change through your standard quality and assurance testing procedures. 2) Your new db2level will be similar to: DB21085I Instance "DB2" uses "64" bits and DB2 code release "SQL09050" with level identifier "03010107". Informational tokens are "DB2 v9.5.000.3485", "special_22318", "NT6495_22318",and Fix Pack "0". Product is installed at "D:\sqllib" with DB2 Copy Name "db2build". Hotfix Readme ============= What is a Hotfix? A Hotfix is simply a self-extracting zip file that contains the modified files necessary to fix a customer's problem. When a Hotfix is executed, it extracts itself and then automatically starts installation by running 'hotfix.exe' How does a Hotfix work? After extracting itself, the Hotfix does two things. First it backs up the files from the SQLLIB folder that it will be replacing. It accomplishes this by renaming the files to .hfb# For example, every Hotfix replaces the file 'db2install.dll', so the Hotfix will rename this file to db2install.dll.hfb0 When this is complete, the Hotfix will copy the new files into their corrsponding locations in the SQLLIB folder. Properly backing up the modified files is the major purpose of a Hotfix. Now that the modified files have been backed up, future Fixpak releases can be properly installed. When installing a new Fixpak, the Fixpak installation will be able to recognize any special builds installed on the system by the backed up files. The Fixpak will then uninstall all Hotfixes that are currently on the system before installing the new Fixpak. The Fixpak will accomplish this by restoring all of the backed up files in the SQLLIB folder, which will bring all of the modified files back to their original release level. Once this is completed, the Fixpak will then install itself. How do I install a Hotfix? To install a Hotfix, make sure all DB2 processes are stopped. You can use the Task Manager to kill all of the running DB2 processes, or click on the Service icon in the Control Panel, and use it to stop all of the running processes. After all DB2 processes are stopped, simply double-click on the Hotfix file, or run hotfix.exe Please note that Hotfixes are not Fixpak images. This means that unlike a Fixpak, a Hotfix can only be installed on top of a specific release. For example, if the Hotfix is built on top of Fixpak 2, you can ONLY install the Hotfix on top of Fixpak 2. If the customer attempts to install a Hotfix on an improper release, the SQLLIB will become corrupted. What are the command options for a Hotfix? Please run the hotfix from any folder outside of the SQLLIB folder. Errors may occur if a hotfix is installed from this folder. The following are the command line options to use with a Hotfix: "Hotfix -l" - Displays a list of hotfixes (HotFixIDs) that are currently installed on the system "Hotfix -f" - Kills all DB2 processes "Hotfix -u HotFixID" - Uninstalls the specified Hotfix The HotfixID parameter is the value shown when running "Hotfix -l" "Hotfix -u all" - Uninstalls all hotfixes "Hotfix -h" - Displays help