Release notes for IBM InfoSphere Classic Data Architect Version 11.3.25

© Copyright IBM® Corporation 2008, 2023. 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.25.

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

Contents

Installation notes
Fix Pack 25 Fixes
Fix Pack 24 Fixes
Fix Pack 23 Fixes
Fix Pack 22 Fixes
Fix Pack 21 Fixes
Fix Pack 20 Fixes
Fix Pack 19 Fixes
Fix Pack 18 Fixes
Fix Pack 17 Fixes
Fix Pack 16 Fixes
Fix Pack 15 Fixes
Fix Pack 14 Fixes
Fix Pack 13 Fixes
Fix Pack 12 Fixes
Fix Pack 9 Fixes
Fix Pack 8 Fixes
Fix Pack 7 Fixes
Fix Pack 6 Fixes
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.24 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.25 is installed.

Enhancement in Fix Pack 25

Fix Pack 25 contains the following fixes:
  • Fix to address the delay in listing large number of tables in CDA database connections
  • Configuration parameter updates.

Enhancement in Fix Pack 24

Fix Pack 24 contains the following fixes:
  • Heap Guard implementation.
    To avoid CDA from crashing or freezing while collecting diagnostics metrics the following heap guard has been implemented:
    1) At 80% heap memory usage, a warning will be displayed in the display bar to increase the diagnostic metrics polling frequency to avoid stopping diagnostic metrics collection at 90% heap.
    2) Above 90% heap memory usage, a warning will be displayed in the display bar that the diagnostic metrics collection is stopped to avoid application crash or freeze.
    You can change the diagnostics metrics options to increase the polling frequency or run the garbage collector to free up some memory and try again.
  • Configuration parameter updates.
  • Fix to disallow spaces in subscription name.
  • Exception clean ups.

Enhancement in Fix Pack 23

Fix Pack 23 contains the following fixes:
  • Fix to address the log4j v1.x vulnerability.
    CDA did not use log4j and was NOT IMPACTED by any of the log4j vulnerabilities. As CDA is built on eclipse, it inherited the log4j eclipse plugin along with the other eclipse plugins. Eclipse plugin Apache Jakarta log4j v1.2.15 has now been removed from CDA.
  • Installation Manager upgraded from out of support version v1.7.1 to the latest supported version v1.9.2.1.
    Installation Manager v1.9.2.1 included in the CDA package does contain a log4j jar and is said to be NOT IMPACTED by the log4j vulnerabilities. Please refer to the update here.

Enhancement in Fix Pack 22

Fix Pack 22 contains the following fixes:
  • CDA diagnostic metrics display not functioning as expected
  • Fix for abrupt freeze/disconnect while monitoring subscriptions
  • JDBC driver update to include new messages

Enhancement in Fix Pack 21

Fix Pack 21 contains the following fixes:
  • CDA was sending incorrect message length when attempting to reconnect
  • CDA Latency screen has gaps

Enhancement in Fix Pack 20

Fix Pack 20 contains the following fixes:
  • Help->About... updated with product and copyright information
  • CDA was appending an extra quotation mark while entering hex data in the nullable column
  • CDA enhancement to support reload functionality
  • When you connect to a server in Server Explorer, the connection will not expands to two levels.
  • Modified JDBC driver to allow data retrieval for character columns of size greater than 256 bytes

Enhancement in Fix Pack 19

Fix Pack 19 contains the following fixes:
  • CDA allows mapping of character data which is greater than 254 bytes
  • CDA does not allow updating description of subscription as server sends CECN0025E

Enhancement in Fix Pack 18

Fix Pack 18 contains the following fixes:
  • An enhancement to support connections over TLSv1.2. Ensure to uninstall prior version of CDA using Installation Manager and install this latest version

Enhancement in Fix Pack 17

Fix Pack 17 contains the following fixes:
  • An enhancement in APAR PH19586 along with CDA FP17 provides support for Multi-Factor Authentication (MFA)

Enhancement in Fix Pack 16

Fix Pack 16 contains the following fixes:
  • A fix for CDA uppercasing spill queue root name

Enhancement in Fix Pack 15

Fix Pack 15 contains the following fixes:
  • A fix for CDA not functioning when SAF exit was disabled

Enhancement in Fix Pack 14

Fix Pack 14 contains the following fixes:
  • A fix for CDA not returning all events in event log as expected

Enhancement in Fix Pack 13

Fix Pack 13 contains the following fixes:
  • A fix for CDA indefinitely trying to connect to server

Enhancement in Fix Pack 12

Fix Pack 12 contains the following enhancements and fixes:
  • An enhancement in APAR PH09143 along with CDA FP12 provides support for Spill queue
  • Modifications to the Validate Replication Mapping for VSAM subscriptions

Enhancement in Fix Pack 9

Fix Pack 9 contains the following enhancements and fixes:
  • When deleting list elements from a service, CDA now uses single quotation marks instead of double quotation marks in the generated MTO command to preserve case when the command is processed on the server.
  • In the Replication Mapping wizard, if the user chooses to generate a PSB, the generation occurs after the replication mappings are successfully added to the subscription. This behavior ensures that the PSB is generated correctly.

Enhancement in Fix Pack 8

Fix Pack 8 contains the following enhancements and fixes:
  • Support for mapping BIT(n) PL/I include file fields as Binary providing that the n value is a multiple of 8 and the field is non-varying.
  • When subscriptions are selected and you start or stop replication, the status is updated but the subscriptions remain selected.
  • When you drag and drop an IMS table from a server to a physical data model and edit the PSB name, the PSB name change is now saved.

Enhancement in Fix Pack 7

Fix Pack 7 contains the following enhancements:

Important: An enhancement in APAR PI84005 along with CDA FP7 provides support for SAF verification of password phrases.

  • Password phrase support was added to server connections in the Server Explorer. When a password value longer than 8 bytes is specified, it is treated as a password phrase. Password phrase support is limited to a maximum of 32 bytes. Password phrase support can be used to enable Multi-Factor Authentication (MFA).
  • When you connect to a server in Server Explorer, the connection expands to two levels to make it more visually apparent that the server is connected.

Enhancement in Fix Pack 6

Fix Pack 6 contains the following enhancement:

Important: You must apply V11.3 PTF UI48072 to the server prior to installing this fix pack.

  • Support of Adabas Version 8.2 mixed case field names. The Adabas DDL generator is modified to enclose all FIELDNAME identifiers in single quotation marks to preserve case. Identifiers that are enclosed in double quotation marks are always changed to uppercase.

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.