Release notes for IMS Enterprise Suite Explorer for Development Version 3.2.1.17
IMS Enterprise Suite Explorer for Development (IMS Explorer) Version 3.2.1.17 is available. Read this document to find important installation information. You can also learn about product updates, compatibility issues, limitations, and known problems.
Contents
Description of release 3.2.1.17
The 3.2.1.17 release includes a new version of JDK.
Description of release 3.2.1.16
The 3.2.1.16 release includes a new version of JDK.
Description of release 3.2.1.15
The 3.2.1.15 release includes the following fixes:
- A COBOL copybook with 'SIGN IS LEADINGSEPARATE CHARACTER' was not merged correctly into a transaction message. This issue is addressed.
- A newer version of Java Development Kit (JDK) is included.
Description of release 3.2.1.14
The 3.2.1.14 release includes the following fixes:
- Connections to query the IMS catalog sometimes succeeded but sometimes failed with a NullPointerException due to a timing issue. This issue is addressed.
- A new version of Java Development Kit (JDK) is included.
Description of release 3.2.1.13
The 3.2.1.13 release includes a new version of JDK.
Description of release 3.2.1.12
The 3.2.1.12 release includes the following fix:
- The SQL parser incorrectly showed SQL syntax errors when the SELECT statement includes a JOIN operator.
Description of release 3.2.1.11
Fixes for the following issues are included in the 3.2.1.11 release:
- The secondary index syntax in the generated DLIDatabaseView is incorrect when the XDFLD alias is different from the XDFLD name
- In the Data Source Explorer view, PARENT decoration is incorrectly set to null when the TABLE (SENSEG) alias is different from the TABLE name.
- Submitting IMS DDL statements failed with the following error: "-198: The operand of a statement contains all blanks or is an empty string." due to an incorrect version of IMS Universal JDBC driver that was included.
Description of release 3.2.1.10
The following enhancements and fixes are included in the 3.2.1.10 release:
- For mobile service creation, the label for the Transaction execution timeout field is changed to IMS Connect socket timeout to more accurately reflect the meaning of this property. Its value is used to determine the time the socket should remain open to wait for a reply from IMS Connect.
- When a DBD is mapped with a COBOL copybook that contains numeric-edited data fields, an "INVALID DISPLAY FIELD" error occurred. This issue is resolved and numeric-edited data fields are now processed as fields of data type CHAR.
- IMS Explorer is unable to access tables or segments under the IMS catalog PCB DFSCAT00 when connecting using the catalog PSB DFSCP001, and an AIB return code and reason code of 0104/0248 is received. This issue has been resolved.
Description of release 3.2.1.9
IMS Explorer Version 3.2.1.9 includes internal updates only.
Description of release 3.2.1.8
The following enhancements and fixes are included in the 3.2.1.8 release of IMS Explorer:
- Transport Layer Security (TLS) v1.2 protocol is now supported for connections to the z/OS® Connect EE server. When you create a z/OS Connect EE server connection, you can now select the TLS protocol to use from the SSL Protocol list.
- The embedded IMS Universal JDBC driver has been updated to correct a problem where DBD segments were not displayed correctly in the Data Source Explorer view.
Description of release 3.2.1.7
The following enhancements and fixes are included in the 3.2.1.7 release of IMS Explorer:
- You can now submit modifications to existing database definitions directly to IMS systems that
support DDL and the IMS management of ACBs.
Use the Edit Database, Edit Segment, and Edit Data Set wizards to load and modify existing definitions, convert them to DDL ALTER statements, and then submit them directly to IMS. Some changes can be activated automatically, while others are stored in the staging data set of the IMS catalog for later activation by the IMS IMPORT DEFN SOURCE(CATALOG) command. Some changes might also require you to unload and reload the database in the IMS environment.
The new support for submitting DDL ALTER statements adds to the existing IMS Explorer support for submitting DDL directly to IMS, which already included support for submitting CREATE and DROP statements for databases, segments (tables), data sets (table spaces), and program views.
Description of release 3.2.1.6
The following enhancements and fixes are included in the 3.2.1.6 release of IMS Explorer:
- For IMS mobile transaction services, IMS Explorer Version 3.2.1.6 adds another advanced data conversion options for specifying whether to enforce the minimum number of array occurrence in the input data structure as defined in the copybook.
- The assignment of an incorrect byte value to the PL/I BIT and BIT array data types when PL/I data structure are imported has been corrected. Now, the length is converted from bit to byte before IMS Explorer sets the field length and sets the data type as BINARY.
Description of release 3.2.1.5
IMS Explorer Version 3.2.1.5 includes internal updates only.
Description of release 3.2.1.4
IMS Explorer Version 3.2.1.4 includes the
following updates:
- A new Edit Data Set Attributes wizard makes it easier to change the modifiable attributes of an existing full-function database data set or a Fast Path DEDB area data set.
- When connecting to an IMS database, you can use the generated Java™ class file in a local IMS Explorer project as the metadata source by selecting the new Use DLIDatabaseView checkbox.
- You can now easily publish consolidated DBD and application field metadata to a compressed folder on your local system by using the new Export Local Database Metadata wizard.
- For each z/OS Connect EE server connection, you can now download all services and their requisite transaction message metadata to your project workspace. Downloaded files can be examined without having to connect to the server, or stored into your source control management system. For more information, see Downloading service definitions.
- Some user interface labels have changed for the IMS Mobile
perspective. The IMS Mobile feature (imsmobile-2.0
feature) that was previously known as the IMS Mobile Feature
Pack for z/OS Connect EE in IMS Enterprise Suite is now included as part of IBM®
z/OS Connect Enterprise Edition V2.0.5 (APAR PI70432) or later as the IMS service provider.
- The term IMS gateway server is replaced by z/OS Connect EE server.
- The IMS Gateway Navigator view is renamed to IMS Service Navigator.
Important: The IMS mobile perspective in this
version is compatible with the IMS service provider that is
included in z/OS Connect EE V2.0.5 or later, but not backward
compatible with IMS Mobile Feature Pack for z/OS Connect EE in IMS
Enterprise Suite. IMS Mobile Feature Pack in IMS Enterprise
Suite is replaced by the IMS service provider in z/OS Connect EE. Existing IMS Mobile Feature Pack customers should keep the installed version of IMS Explorer until upgrading to z/OS Connect
EE V2.0.5 (APAR PI70432) or later. To start taking advantage of the other new functions in this
release, you can install IMS Explorer V3.2.1.4 in a different
directory.
Description of release 3.2.1.3
IMS Explorer Version 3.2.1.3 includes internal updates only.
Description of release 3.2.1.2
IMS Explorer Version 3.2.1.2 adds two new wizards, Edit Segment Attributes and Edit Database Attributes, that support editing modifiable attributes of segments and databases. Changes are saved as macro instructions for the DBD Generation utility.
IMS Explorer Version 3.2.1.2 provides the support for IMS Mobile Feature Pack for z/OS Connect EE V3.2.1.2. Older versions of IMS Mobile Feature Pack for z/OS Connect EE V3.2.1.2 are not compatible.
The added support includes the following enhancements to the wizard for creating an IMS mobile service:
- Support for the new IMS mobile service registry
- Service definitions are stored in the new IMS mobile service registry framework in IMS Mobile Feature Pack for z/OS Connect EE V3.2.1.2 to facilitate service promotion.
- Support for advanced mobile data conversion
- You can now trim leading or trailing white spaces, exclude special, non-printable characters, or suppress low values or empty tags from the JSON response messages. For input messages, support is added for initializing fields.
- Support for overriding an IMS destination name
- You can now create a few interaction profiles and reuse the profiles to across multiple z/OS Connect EE services regardless of the IMS destination that the profile was originally defined for.
- Support for overriding a transaction code
- You can now define one set of transaction message formats for a given program, but access the program through a REST service by using potentially multiple transaction code values at run time.
For more information about advanced mobile data conversion options, see Service-level data conversion customization.
For more information about the new IMS mobile service registry, see IMS mobile service registry.
Other updates
- This release addresses a COBOL data conversion issue in the IMS Mobile Transaction Service wizard when the REDEFINES clause contains an OCCURS statement.
- For each IMS mobile service, only one connection profile can be selected. For existing service definitions with multiple connection profiles, the first connection profile in the definition is preserved upon upgrading to V3.2.1.2.
Description of release 3.2.1.1
IMS Explorer Version 3.2.1.1 updates the version of Java and adds several fixes to the features previously released in Version 3.2.1.
Description of release 3.2.1
IMS Explorer Version 3.2.1 includes the
following new features:
- Support for RESTful API creation in IBM z/OS Connect Enterprise Edition
- IBM z/OS Connect Enterprise Edition uses service archive (SAR) files to create a z/OS-based RESTful API. A SAR file contains the information that is needed by a z/OS Connect EE service provider to install and provide the service and to enable the service as a JSON asset. Use IMS Explorer to generate SAR files from your z/OS Connect EE services. See Generating a service archive file for z/OS Connect EE.
- DDL generation support with IMS 14
- Allows you to generate DDL from an existing DBD with IMS 14 on your host system. You can generate DDL by right-clicking on a DBD or Segment and selecting Generate DDL. You can edit the generated DDL and submit the new statements to IMS. See Creating DBDs and PSBs from IMS resources by using DDL.
- Submit field changes to IMS with IMS 14
- Allows you to submit database field changes directly to IMS with IMS 14 on your host system. You can submit changes by right-clicking on a DBD or Segment and selecting Submit Changes to IMS. IMS Explorer sends DDL ALTER TABLE statements to IMS though the JDBC driver. See Applying changes to an IMS system.
- Unique user ID and password for each connection profile for IMS mobile services
- Before this release, all connection profiles that are associated with an IMS gateway server instance use the same user ID for authentication with IMS. That user ID is determined from the subject of the request if the subject length is 8 bytes or less. If the length is more than 8 bytes, the technical ID is used. The support for a unique user ID and password for each connection profile eases server configuration and allows for finer audit granularity for mobile workloads. In the IMS connection profile wizard, in addition to the profile name, the host, and the port number, you can specify a SAF user name and the associated SAF password. This user name and password are passed to IMS Connect for SAF authentication. See:
Compatibility issues with earlier releases
IMS Explorer Version 3.2.1.17 is not compatible with releases of IMS Explorer earlier than Version 3.2.1.1. You must uninstall any versions prior to IMS Explorer Version 3.2.1.1 before you install IMS Explorer Version 3.2.1.17.
System requirements
For information about hardware and software compatibility, see the detailed system requirements documents at Supported platforms and Software requirements.
Installing IMS Explorer Version 3.2.1.17
For step-by-step installation instructions, see these topics in IBM Knowledge Center:
- To install IMS Explorer for the first time: Installing IMS Explorer
Limitations and known problems
- Limitations and known problems
- See Restrictions for IMS Explorer.