Release notes for IBM InfoSphere Classic Data Architect Version 9.5.7

Installation notes

If you are using IBM Installation Manager to install directly from the default CDA update site, continue with the instructions below. Otherwise, if you want to obtain the update to install from a local drive, follow the instructions in http://public.dhe.ibm.com/software/websphere/cda/95/957/docs/readme/install_local_95.html.

If CDA V9.5 is running, exit the application.
Run IBM Installation Manager. From the All Programs menu, select IBM Installation Manager >IBM Installation Manager.
Select Update Packages.
Select CDA V9.5 and click Next.
- You might get a message that an update is required for IBM Installation Manager. If so, install the update.
- If you have a firewall, you might be prompted and asked to permit the update to run. Permit the update.
After the update is installed, start CDA V9.5.
From the Help menu select the About... option and you should see that version 9.5.7 is installed.

Fixes in Fix Pack 7

This Fix Pack addresses the following problem:

When mapping an IDMS table and selecting an element that is part of a group which is part of an OCCURS array, the element was not mapped with an array subscript.

Fixes in Fix Pack 6

This Fix Pack addresses the following problem:

The JDBC driver did not always accurately return result sets from stored procedure calls. This was manifested as a bug in the Adabas table mapping wizard which uses a stored procedure behind the scenes to discover Adabas file information. The incorrect result set resulted in an incorrect mapping of CHAR for all Adabas fields instead of the correct SQL data type. Possible impact to the IDMS discovery wizard though no problems have been reported thus far. This fix covers all issues related to stored procedure result sets returned by the driver.

** REQUIREMENT ** You must edit existing connections in the Database Explorer to access the new driver. Right click on the connection. Select Edit Connection and change the Class location to the following location: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\plugins\com.ibm.datatools.dbdefinition.db2.cac.classic_1.1.1.v201204230718\driver\cacjdbc21.jar

Fixes in Fix Pack 5

This Fix Pack addresses the following problems:

When parsing a DBD containing an EXIT=(* clause, the parser was improperly treating the '*' as the beginning of a comment.
When adding a WHERE clause to a view by using one of the table mapping wizards, a negative size was not allowed in the expression for a numeric field.
When adding a WHERE clause to a view by using one of the table mapping wizards, if the user selected an 88 field containing multiple VALUEs, extra parentheses were added.

New in Fix Pack 4

This Fix Pack includes the following enhancements:

New Mapping Preferences that allow you to optionally map LONG VARCHAR as VARCHAR or LONG VARGRAPHIC as VARGRAPHIC. The default is the current behavior which is to map them as LONG data types.

Fixes in Fix Pack 4

This Fix Pack addresses the following problems:

When a DBD name was enclosed in parentheses, the DBD parser was not stripping them off the parentheses as it should have.
The DBD parser was not correctly parsing lines that contained a mixture of syntax and comments.

Fixes in Fix Pack 3

Fix Pack 3 addresses the following problem:

The COBOL compiler contained within CDA was incorrectly truncating DBCS data names to 10 characters when importing copybook.

Fixes in Fix Pack 2

Fix Pack 2 addresses the following problem:

Fix Pack 1 introduced possible regression within the Database Explorer view on the JDBC connection panel to a Classic Server. In some cases, only the code page 5026 exists in the dropdown.

New in Fix Pack 1

Fix Pack 1 includes the following enhancements:

New Copybook Preference that allows you to map PIC 9(1) COMP through PIC 9(4) COMP as DECIMAL(5,0) instead of SMALLINT and PIC 9(5) COMP through PIC 9(9) as DECIMAL(10,0) instead of INTEGER.
Adabas read and write password support is added to the Properties view for Adabas table definitions.
Parsing fails when a PL/1 include file does not contain a DCL 1 level statement. When this occurs, CDA now adds DCL 1 to the beginning of the file which enables parsing.

Fixes in Fix Pack 1

Fix Pack 1 addresses the following problems:

IMS™ subsystem was not being populated in the Properties view for a table on the data server which resulted in a missing "SUBSYSTEM" clause when DDL was generated.
When a COBOL copybook contained an OCCURS definition without sub-elements, CDA marked it as unmappable when it should have been mappable.
COBOL copybook defined with PIC SVP9(15) COMP-3 erroneously generated DECIMAL(15,16) instead of DECIMAL(16,16). CDA is modified to handle "P" value in the picture clause.
When a CA-IDMS schema contained OCCURS DEPENDING ON or REDEFINES and the column was listed on the following line instead of the same line, parsing failed.
When importing Classic reference files, if the user typed a list and attempted to enter a comma, the comma was being erased forcing the user to use the Browse button to enter multiple files.
When editing the "NULL IS" attribute in the properties view, X'ABC' should be treated as x'ABC' to avoid a DDL submission error.

Release notes for IBM InfoSphere™ Classic Data Architect Version 9.5.7

Contents