Data Interpretation System 2.1.1 Service README This document provides instructions for downloading, applying, and removing fix levels for Data Interpretation System (DIS) 2.1.1 Server and Workstation components. A complete listing of the problems fixed in this fix level is located at the end of these instructions. Overview Fix levels for DIS 2.1.1 Server and Workstation components are contained in self-extracting ZIP files. All fix levels 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 while DIS is running. After you finish the application process, you will need to restart the DIS services for the fixes to take affect. Downloading Fix Levels You can download fix levels for DIS 2.1.1 from an FTP site or by accessing the DIS Web page. Before you download a fix level: 1. In an OS/2 window, create a directory to hold the extracted contents of the ZIP file. For example, you can type mkdir tmpfix to create a new directory. 2. After you create the new directory, make it the current directory. To download fix levels from an FTP site: 1. In an OS/2 window, type ftp ftp.software.ibm. 2. Type the FTP user name: anonymous. 3. Type the FTP password: your internet address. 4. Type the directory path: cd com/ps/products/dis/fixes. 5. Type bi to set the transfer mode to binary. 6. Type prompt to turn off FTP prompt messages. 7. Type get [filename]. The DIS 2.1.1 fix level is downloaded to your workstation. To download fix levels via the World Wide Web: 1. Point your Web browser to ftp.software.ibm.com/ps/products/dis. 2. Click on the info directory. 3. Click on the text directory. 4. Now click on the XXXfix.txt file that you are interested in applying to your network. The file will download to your Workstation. This file will contain instructions and PR information for that fix level. 5. Get back to the dis directory and click on the fixes directory. 6. Click on the fix level you need. Please ensure that the drive you are downloading to has ample space as stated in the Overview. When IDS fix levels become available, these same instructions will apply, and the fix levels will be available in the ids directory. (ftp.software.ibm.com/ps/products/ids) 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: 1. Extract the files in the ZIP file by typing its FTP filename. For example, type 66fix. A new directory named fix is created in your current directory. 2. Type cd fix to change to the fix directory. 3. If DIS services are not already running, click on the DIS icon on the OS/2 desktop. Wait for the services to start completely. 4. In the OS/2 window, type upgrade. You might be prompted for the directory where the DIS 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. 5. 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. The program is finished running when the entire upgrade code is transferred to the DIS filesystem. After the new code is transferred, you must reset all workstations and services for the updates to take affect. To do this: 1. Log on to the DIS Desktop. 2. Open the SA Tool. 3. In the SA Tool, select Network Command from the Service Type menu. 4. Click on the Connect to Service button. 5. Type your password when prompted. You are now in the Network Commandsw menu. 6. 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. DIS 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 6B5 is 6B5UNDO.EXE. When you apply a fix level undo, your system will return to the DIS 2.1.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 The following fix level is available for DIS 2.1.1: 6C6 Listing of problems that are now fixed by the 6C6 fix level: 37700- A black box prints on a Plot if @variables are used & the title frame text is larger than the frame. 37884- Cannot download a Spreadsheet (WK1) to the 4th level of a directory using PCDir. 37903- The WriteSQL transformer is not transferring character values, instead a user would see ' ' . 37910- Two problems were found: 1) Opening a Reporter icon from customer results in a reset. 2) This same Reporter when sent to a printer, the report looks fine but all the column headings are garbled. 37919- The Data Entry SQL is missing the table name so the Data Entry ends with an error. 37938- The error message "Unable to open Spreadsheet" displays when a SS (Spreadsheet) with a lengthy formula that does not exceed the 400 character limitation, but when "tokenized", would cause the formula strings to exceed that limitation. 37943- Capsule Run Log not displaying the time of a Capsule run when desktop preference is set to display Date Only. A user would be required to change their desktop preference to display Date and Time, which is incorrect. 37950- Print services not able to start on Pentiums. 37959- In a Query the F9 key fails to cancel DB2 host query. The F9 function works in the APPC Gateway, but the cancel request never reaches the host. 37965- A Reference Capsule executed using this particular setup: SS->Out->Capsule->SS, causes a reset. Manually copying data from one SS to another SS also causes a reset. 37970- When using a Query to insert data into a DB, fails when the decimal precision is greater than 15. 37971- Create column function in the Query sends the internal name of a column to the DB server. It should use the sqlname as it is designed to do. 37978- A SS in a capsule transferring no data to another SS with a region name defined in the arrow options, results in a reset. Example: SS1->SS2->SS3->. There are no regions defined in any of the SSs. SS1 connected to SS2 has a region name defined in the connecting arrow. SS2 connected to SS3 has no region names defined (All Data) in the connecting arrow. 37979- Primary File Server (PFS), will not start service after first shutdown from initial installation of 3rd drive volume. The CATRANS.EXE file caused a memory leak prohibiting other service processes of the PFS to continue after initialization completes. The memory leak also slows down the PFS's performance and may eventually disconnect or stop dependent services. 37989- The 'All' default in the controls window of the Replace transformer does not work. 37990- A problem was found where the SQL entry tool fails when the source document name is longer than 30 characters. 37992- WriteSQL transformer missing and truncating column names. It was found that the WriteSQL transformer has a limitation in the Insert field in the transformers main window. Limitation is set to 255 chars. User's are instructed to use the Insert parameter in the Controls of the transformer-this has a 456 char limitation. 37994- SQL entry receives an error message with the &label function. Problem seems to occur when a previously parsed label is encountered again after a goto statement. 38008- The Computed date column within a Query has a Metaphor date resolution set to Month but displays results as MDY(12/1/96), when it should display the results as MY(12/96). 38009- Constraining in the header or column header areas of the reporter on a dimension key does not constrain the fact key as it did in DIS 1.3.X. 38015- A reset occurs when a SS, which contains a formula that results in an error, is transferred to the PC Directory. 38017- Date values not accepted by Data Entry, even though the date value displays as a choice in the browser list. Error message displayed: "DTEN:001-0116 Error'April 24, 1993' is not a valid value. 38023- When a capsule is executed using this particular setup: SS->Out->Capsule->SS, a reset occurs if the first SS has a cell ' =ERROR'. 38024- When an SQL entry tool receives no data, and the user selects on the scroll bar, a reset occurs. 38025- Calculations including a blank cell received incorrect results. i.e. if (A1="",A1+100,"") this gave a result of blank in a SS, which is incorrect. Correct result should be 100. 38034- Copying columns from one SS to another SS causes a reset. 38037- Script command fails when executed from the file server console. 38043- A formula within a SS that results in 'Error' does not copy over to a new cell. 38048- Replicating on copied blank cells in a SS causes a reset. 38053- Some migrated capsules cause a reset to occur when attempting to open. 38079- Text document imported to RTF then to Lotus Notes, looses tab formats. The document changes and the tabs are no longer in the right places. 40137- The Custom Browse feature in the Data Entry does not work. 40151- When using the &Date() with &Constraint function in the SQL Entry tool, in this order, corrupts the SQL and produces incorrect SQL. 40162- Desktop preferences set for 2 decimal places and the Fact table is constrained for a dollar amount of 99999.99, the sql returned is ############. 41007- An incomplete write to the Asset Manager increases time out and drops packet size. 41048- Updating and copying existing Forms Design tool results in all changes being lost. (Summary: Open, update, close, copy, open, update, close, open. All updates are gone.) 41097- A capsule with a Reporter connected to a Text icon results in a reset. The reset only occurs on Reporter's with added text fields included in it's report. 41177- When opening a Data Entry that accesses an empty PESQL document, results in a reset. 41214- Reporter SQL built does not include constraints on the inlist resulting in an SQLCODE156 error. 41224- An incomplete write to the Asset Management DB will hang the Asset Manager.