Release notes for IBM InfoSphere Classic Data Architect Version 11.3.5

© Copyright IBM® Corporation 2008, 2017. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

The following information describes installation instructions, new features, and the fixes in Classic Data Architect (CDA) Version 11.3.5.

** Note: This fix pack applies to the GAed version of 11.3.1.

Contents

Installation notes
Fix Pack 5 Fixes
Fix Pack 4 Fixes
Fix Pack 3 Fixes
Fix Pack 2 Fixes

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 Local installation notes.
  1. If CDA V11.3.1 - V11.3.4 is running, exit the application.
  2. Run IBM Installation Manager. From the All Programs menu, select IBM Installation Manager > IBM Installation Manager.
  3. Select Update.
  4. Select CDA V11.3 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 asked to permit the update to run. Permit the update.
  5. After the update is installed, start CDA V11.3
  6. From the Help menu select the About... option and you should see that version 11.3.5 is installed.

Enhancements and fixes in Fix Pack 5

Fix Pack 5 contains the following enhancements and fixes:

Important: It is highly recommended that you back up your workspace prior to installing Fix Pack 5 as you would when migrating to a new release.

  • The Columns tab in the Properties view for tables in both the Data Project Explorer and Data Source Explorer views was displaying duplicate column tables. This is resolved with an underlying model change.
  • Support is added for pre-11.3.5 physical data models in 11.3.5. This fix was required because of the underlying model change that was needed to resolve duplicate column tables.

Enhancements and fixes in Fix Pack 4

Fix Pack 4 contains the following enhancements and fixes:
  • Updated configuration parameter descriptions for DLIUSEBATCHONLY and DLIMAXOPENTIME to reflect the enhanced DL/I batch support.
  • The option to "Use local time" was added to the Adabas preference page and Adabas create table wizard. When checked, this option adds "&L" to the end of the time format string. This tells the Classic Federation server that T fields are stored in local time and should not be adjusted from GMT to local time.
  • The Adabas create table wizard was not populating the predict dictionary with the predict dictionary preference.
  • When loading an IMS table from the server that was defined with a PCB name, CDA looped and generated many duplicate names. This error resulted in the PCB Selection tab in the Property view displaying duplicate names. If you generated DDL from the table, the DDL erroneously also contained many duplicate PCB names.
  • The Refresh button on the Replication Mapping view refreshed only selected replication mappings instead of the entire view.
  • When connecting to a server in the Console Explorer view, CDA was not handling XML that came back with an error code and error message from the server. This error could result in constant looping when CDA is trying to get data that the server can not provide because it encountered a problem. CDA now reports the error code and message and then disconnects from the server. The user should look up the error code and determine what is wrong with the server.

Enhancements and fixes in Fix Pack 3

Fix Pack 3 contains the following enhancements and fixes:
  • VSAM apply exit support.
  • Updated configuration parameter descriptions.
  • Edit connection with rename support in the Console Explorer.
  • Exporting diagnostic metrics no longer appends "Console" in native language to the server name because the metrics parser can not process characters.
  • When you are connecting to a server in Console Explorer, the user ID is always uppercased to avoid problems with lowercase in other languages that results in XML that can not be parsed.
  • CDA now caches XML at the start of diagnostic collection. When exporting, it gets the latest configuration and metadata information from the server if the server is still running. If not, it uses cached data. Previously, exporting diagnostic metrics when the servers had been brought down resulted in a zip file with empty XML files because CDA could not get the needed information from the server.
  • Many issues with the Diagnostic view not refreshing properly when connecting and disconnecting servers have been fixed.
  • An error with IMS advanced properties is fixed.
  • A hang issue in both IMS and VSAM replication when clicking OK on the Modify Subscription dialog is fixed.
  • Additional checks are added to avoid null pointer errors when traversing or updating subscriptions in views.

Enhancements and fixes in Fix Pack 2

Fix Pack 2 contains the following enhancements and fixes:
  • Support for specifying a scheduled end time when ending replication for IMS-to-IMS or VSAM-to-VSAM subscriptions.
  • Updated cacjdbc21.jar for PMR 69505,695,760.
  • When exporting diagnostic metrics, the serverconnections.txt entries are fixed so that they now match zip file names when NL characters are used in the server connection names.