IBM
DB2 OLAP Server for AS/400 1.1
Fixpack
13a
Instructions
for installing the patch for the Warehouse Builder client component
Service
Level 3.01.070
May
2001
Please read and print these
instructions before installing the patch!
Patch download instructions
These patches are language
specific. Please download the patch for your language only.
English
(5.07 MB)
French
(3.02 MB)
German
(3.20 MB)
Spanish
(2.97 MB)
Patch
Installation Instructions
-
Download the patch for your
language
-
Copy the patch to your STRATEGY
\Bin directory. This is the folder that contains the executable files such
as VISTA.EXE. (NOTE: Do not copy this file to your Backup folder)
-
Rename or delete the existing Backup folder that contains
previous ShowCase patch applications
-
Double-click on the patch executable
A Welcome dialog box appears,
and the software searches for the files to update. Note: The patch can
only search the drive to which it is copied.
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):
-
Locate the unpatch.bak.
-
Rename the unpatch.bak to unpatch.bat.
-
At an MS-DOS prompt, type the
path to unpatch.bat and press Enter.
OR
On the desktop, click Start
> Run, and browse for the patch to unpatch.bat. Click OK.
Your application is automatically
restored to its pre-patch configuration.
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.
Summary of problems
fixed
This patch will resolve
the following:
-
Alias names will be quoted
if they contain variant characters. (F6866)
-
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)
-
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)
In addition, this patch incorporates
all previous Client 3.01x patches to resolve the following issues:
-
Will support an expression
with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant.
"(F3743)
-
The conditions involving AND
and OR will not be lost on converting to join conditions. "(F5816)
-
"Column not found in datasource"
will not be issued when importing AS/400 query objects that contains lower
case letters."(F5971)
-
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. "(F3655)
-
Will support an expression
with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant.
"(F3743)
-
Correct information is displayed
in condition dialog when regional settings are changed. Also corrected
for the columns dialogs and assistants, and since the international separators
are added when building the SQL they don't need to be added a second time
when entering the SQL statement dialog. "(F4899)
-
When using the SQL function
CHAR, Query and Report Writer would display the error message "Function
and argument data types do not match" when a String Literal or a Query
Date Variable (without anything else in the function) was the argument
to the CHAR function. The SQL spec allows Strings, Dates, and Numbers as
the argument to the function CHAR. Query and Report Writer will now allow
all of these arguments to the CHAR function. "(F5172)
-
The correct default data type
will be displayed in the "Save As Data" dialog for Text. "(F4124)
-
1. Fixed retrieving distinct
table references from the from clause aliases. We were initially retrieving
duplicate table references when more than one alias had the same table
reference. Cause problems with change link.
2. During change link we
were only considering the first subquery to retrieve the invalid tables
- unions and multiple subqueries would cause problems. Added a loop to
look at all subqueries.
3. Make linkage mapkey
was not generating the correct key - causing memory leaks as we had the
same key being generated and we made multiple new objects and did not delete
all of them. Now creating distinct linkage keys by getting the owner and
table name if the system names are empty. "(F4511)
-
Prompted variables will keep
the apostrophes when default to current variable is selected and correct
data will be retrieved. "(F4686)
-
Japanese characters will be
displayed in the splash screen. "(F4996)
-
DBCS characters can now be
used in both the Names and Descriptions on the columns dialog. "(F5003)
-
Added a check to use the windows
regional settings system date format to resolve a problem whereby in a
German Query/German Windows environment date conditions involving 01/01/0001
could not be added. " (F4633)
-
The quoted '(' and ',' in case
statements should not be changed now and correct results should be retrieved.
" (F4500)
-
Make the version information
consistent between the Splash and the About dialog boxes. (F4067)
-
The sequence associated with
a definition was not being added. The order was taken from the order that
appeared in the list of available definitions. Added the correct sequence
value to the definition when the customer selects OK on the Add Definitions
to Set dialog. " (F4223)
-
No longer receive a GPF due
to the font setting of the sample data grid on Japanese and Chinese versions
of Windows. " (F4363)
-
Warehouse Builder was not updating
the sequence of a set of definitions. This is because our routine to perform
the updates was failing. The failure occurred because the information that
details the sequence of the definitions was missing. " (F4202)
-
Track all changes to the Control
Tables related to a Definition object and updates this information regardless
of whether the Table itself is being created or altered. (F3751)
-
Change the method to save definition
changes. We now use the same code as File > Save to make sure that all
Control Table entries get changed on an update of Target Library or Table.
(F4011)
Back
to Patch Description