Intelligent Decision Server 1.0.1 and 1.0.0 Service README This document provides instructions for applying and removing fix levels for Intelligent Decision Server (IDS) Server and Workstation components. These fix levels can be applied to both IDS 1.0.1 and IDS 1.0.0 servers. Overview Fix levels for IDS Servers and Workstation components are contained in self-extracting ZIP files. All fix levels of a particular type are cumulative; they contain every fix from previous levels as well as new ones. You will need 10 megabytes of free hard disk space for each ZIP file and an additional 10-20 megabytes of free space for the extracted files. You must apply these fixes from an IDS OS/2 workstation while IDS is running. After you finish the application process, you will need to restart the IDS services for the fixes to take affect. Also, ensure all temporary fixes have been removed, this pertains to any dlls that were added to the 'nodeovly' directory or using the /s parameter. Please contact the Technical Support Engineer that supplied the temporary fix to verify that this needs to be done. Should you have any problems in applying a fix level please contact Technical Support, 1-800-992-4777. Applying Fix Levels Each fix level is downloaded in a ZIP file that extracts itself into a set of files and directories that are used to upgrade your current system. To apply an update: Download the desired ZIP files. Each one should be downloaded into a separate directory. Extract the files in the ZIP file by typing its filename. For example, type "go74lfix". A new directory named "fix" is created in your current directory. If IDS services are not already running, click on the IDS icon on the OS/2 desktop. Wait for the services to start completely. Type "cd fix" to change to the fix directory. In the OS/2 window, type "upgrade". You might be prompted for the directory where the IDS software is installed on your workstation. The fix application compares the timestamps of all files within its domain with files present on the Primary File Server. Messages are displayed for each file, stating that your version is either newer than, or older than, or matches, the upgrade file. Type the system password when you are prompted to do so. If you have not updated this password, type "original". Messages are displayed informing you that the files are being replaced. NOTE: If you enter the wrong password, the upgrade will not occur and you will need to restart at the previous step, type "upgrade". If you downloaded more than one type of fix level, go to the next "fix" directory and repeat the steps. After the new code is transferred, you must reset all workstations and services for the updates to take affect. To do this: Log on to the IDS Desktop. Open the SA Tool. In the SA Tool, select "Network Command" from the "Service Type" menu. Click on the "Connect to Service" button. Type your password when prompted. You are now in the "Network Commands" menu. Click on the "Reset All Workstations and Services" button. The workstation you are using will reset and all services will recycle. Monitor all network services to ensure that they reset. For some fix levels, a DB2 bind may be required. Check the details under "Available Fix Levels" below. If a bind is required, follow these steps on your OS/2 database gateway: a. Ensure that the OS/2 database gateway has been restarted after the fixpack was applied. b. Connect to the target database you are using. Ex1. db2 connect to TARGETDB Ex2. db2 connect to TARGETDB user USERID using PASSWORD c. Do the DB2 BIND. There are some syntax differences for DB2 on different platforms. Please reference the DB2 Manuals. i) Example for DB2/MVS or DB2/400: db2 bind c:\$IDS_HOME\exe\m4esd.bnd action replace blocking all collection USERID grant public isolation NC Note: You use "add" instead of "replace" when you are doing the BIND for the first time. ii) Example for DB2/2 or DB2/UNIX: db2 bind c:\$IDS_HOME\exe\m4esd.bnd blocking all grant public isolation d. Do DISBIND on the local database. Change directory to \$IDS_HOME\exe then do the DISBIND. Ex. disbind sample cs Note: The sample is the local database name. IDS is now upgraded to the new fix level. Undoing Fix Levels For each fix level, there is a corresponding undo level available in a self-extracting ZIP file. For example, the undo level for "go74lfix.exe" is go74lund.exe. When you apply a fix level undo, your system will return to the IDS 1.0.0 base level. (When you apply a fix level undo for the Windows workstation, those files will return to the IDS 1.0.1 base level.) You can then apply any of the other available cumulative fix levels to move your system to the desired level. The steps for applying a level undo are the same as the steps for applying a fix level. You will need 30 megabytes of free hard disk space to download and extract a level undo. Available fix levels Each fix level and corresponding undo is located in a directory with the same name as the fix level. Within each directory, the README.TXT file lists the problems that are fixed in that level. (IDS 1.0.1 Windows Workstation fix levels can also be applied to an IDS 1.0.0 server.) NOTE: If you have Windows workstations, then you should install both the OS/2 and Windows fix levels at the same time. If you do not have Windows Workstations, then you do not need to install the Windows Workstation fix levels. For IDS 1.0.1 or 1.0.0 OS/2 Servers and Workstations: go74L, go786 NOTE: DB2 bind is required after installing "go786" NOTE: If you have Unix database gateways, and you install "go786", you must also install "gd786" from the ...\v101\dbgw directory. For IDS 1.0.1 Windows Workstation: gw74e, gw786