IBM Classic Data Architect version 9.1 Interim Fix 0005

(c) IBM Corporation 2007. All rights reserved.

About this fix

Problem 1: The Adabas wizard generates arrays with an invalid level of zero. The generated DDL is incorrect.

Symptom: The DDL generated has ENDLEVEL 0 for these arrays and BEGINLEVEL statements are missing.

Fix: The wizard now correctly indicates an array level of 1 or 2.

Repair: You do not need to remove and remap Adabas tables that contain invalid array levels of zero. The generate DDL process will repair the array definitions in the model.

Feature 1: This new feature allows the user to override the default behavior and generate indexes for NU fields. Use this feature only if you know that the NU field always contains data.

Default Behavior: The Adabas wizard does not automatically generate indexes for nullable fields (fields with NU attribute). Queries that search for an empty value by using a WHERE clause against a nullable field (such as WHERE COLUMN_AA='') can yield incorrect results. Classic Federation will use the index, pass it to Adabas to resolve, and retrieve no rows. If no index exists on the column, a table scan is triggered and the result set consists only of rows where the column has no value.

Implementation: The Adabas wizard option page has an additional checkbox where you can override the default behavior and generate indexes for NU fields. The default is to generate no index (unchecked).

Prerequisite

Before applying this interim fix, you must apply:

Important Reminder

After installing this interim fix, start Classic Data Architect with the -clean option so that the changes are picked up.