Instructions for installing the patch for the Builder client
Service level 4.00.01x
April 2001

Please read and print these instructions before installing the patch!

These patches are language specific. Please download the patch for your language only.

English (1.01 MB)
French (738 KB)
German (746 KB)

Applicable Versions
This patch applies to ShowCase Analyzer, Query, Query Lotus Add-Ins, Report Writer, Warehouse Manager Client, and Web Servlet version 4.0 and later. Apply this patch if you are using one or more of these applications. After the patch is applied, these products will be upgraded to STRATEGY 4.00.010 (4.00.013 for NLS patches).

Summary of problems fixed
This patch resolves the following issues:

Product affected: Analyzer

• Allow users to open views when a default printer is not configured on the PC. (F6341)
• The default port on the Analyzer Configuration dialog is set to 43419 to match the default server port. (F6425)
• Attribute dimensions were not rolling up correctly when not all members have an attribute applied. (F6604)
• Problems opening model and essbase views in translated languages because 'Measures' was inadvertently translated. (F6890) (NLS versions only)

• Dialog changed to allow more space to avoid truncated text on Result Options pull down menu. (F4494)
• Resolved invalid floating point exceptions caused when NULL values were involved in calculations and sorts in multidimensional queries saved to the server. (F6892)
• " Measures" is not translated when creating model views so they can be opened in Analyzer. (F6894)
• Resolved a problem whereby Query against an Essbase database would GPF when choosing the finish button, reentering the navigator, moving something to the rows section, and then selecting run. (F6908)

• Column headings will be displayed when a linked query returns no data. (F6385)

• Resolved a problem where a value of spaces in a derived field generated a zero as the output. (F6814)
• Report Writer has a re-entrency problem that occurs when reports are run via Enterprise Server (Schedule Report Server). The re-entrency problem was reproduced when a graph is linked to a crosstab, though there may be other cases as well. The fix was to make sure Report Writer delays processing Enterpise Server commands until it has completely finished the previous command. (F6808)
• Opening a multidimensional .dbq file from the ShowCase Server will generate an error message rather than hang Report Writer. (F6787)

• Global Variables that have the prompt attributes check box marked for "Skip Prompt if Variable has Value" will no longer prompt on subsequent queries, once the value has been set. (F5474)
• Alias names will be quoted if they contain variant characters. (F6866)
• Japanese Katakana characters will be allowed in the SQL statement as table and column qualifiers. Qualifiers with these characters will be quoted as required by SQL/400. DataViews and Query Batch can use these characters as table and column qualifiers and will behave normally. (F6705)

• Allow minimum memory size to be specified in ShowCase.cfg file. (F6542)

• Resolved a problem where "variables are not allowed" when attempting to import dbq's with prompts into WB (F6180)
• Resolved problem with non US systems trying to start auditing. (F5040)

• Resolved problem with non US systems trying to start auditing. (F5040)
• User's with *MANAGE application authority to Report Writer can now work with Enterprise Servers in Warehouse Manager Client. (F6881)

Patch Installation Instructions.

1. Download the patch executable file.
2. Copy the patch to your STRATEGY \Bin directory. This is the file that contains the executable files such as VISTA.EXE. (NOTE: Do not copy this file to your Backup folder)
3. Rename or delete the existing Backup folder that contains previous ShowCase patch applications
4. Double-click on patch executable file.

The patch program runs and automatically modifies, adds, renames, or deletes files as necessary to complete the patch.

The original file is saved in the BACKUP directory, which is automatically created on the drive from which the patch is run.

Undoing the Patch
If you want or need to get back to the original files (before the patch was applied), you will find them in the BACKUP directory, which is located on the drive that the patch is run from. The BACKUP directory contains a file called unpatch.bak. This file is a script file containing the commands necessary to automatically restore the original files. To restore the original files (from any operating system environment):

1. Locate the unpatch.bak
2. Rename the unpatch.bak to unpatch.bat
3. At an MS-DOS prompt, type the path to unpatch.bat (E.g., C:\ProgramFiles\STRATEGY\Desktop\Backup\unpatch.bat) and press Enter.

OR
On the desktop, click Start > Run, and browse for the patch to unpatch.bat. Click OK.

If you apply multiple PTFs over time without deleting the Backup directory, the BACKUP directory will contain multiple copies of unpatch files and the related original files from each backup. You may wish to periodically clean the BACKUP directory to recover disk space. To keep the most recent backup information, keep the latest unpatch.bak (or unpatch.bat if you already renamed it) file and the files listed in its text.