This release provides enhancements in the following areas:
This product includes OpenSSL version 1.1.1c.
With the release of Enterprise Developer 2.2 Update 1, the Compare and Synchronization Monitor has been updated to version 2.
Version 2 is greatly improved in terms of performance, especially during initial checkout of partitioned data sets or when synchronizing a large number of members. Also, the user interface has been improved, and some of the functions available in the old version have now changed or become obsolete.
You can now use the context menu for the servers in Server Explorer to enable the display of the Enterprise Server log information in .
This release provides support that enables WebSphere MQ applications to communicate with IMS applications in an Enterprise Server region.
Recovery of Fileshare data files has been enhanced.
Rollback recovery is a faster process that aims to fix the files from their failed state.
This process cannot be used in all scenarios, but a new user exit has also been introduced that allows you to programmatically control which files you wish to recover with this process.
Hot backups are also a new introduction, which allow you to perform a backup without having to shut down Fileshare.
Previously, MGMTCLAS was supported by simply saving it on the catalog record when a dataset was allocated in JCL using the MGMTCLAS parameter on the DD statement. Starting with this release, you can use batch jobs to define MGMT classes and to specify the EXPIRE AFTER time (in days).
This release includes the following enhancements to the managed COBOL syntax:
PL/I support within the IDE now includes the following enhancements:
The PL/I Compiler and Runtime now support the following new built-in functions:
This provides an improved functionality and a greater language compatibility when you migrate applications from a z/OS environment.
You no longer need to modify application code that uses %OPTION in order for it to compile successfully.
This enables the use of PL/I macros that generate code using these built-in functions.
%INCLUDE MYPDS(MYMEMBER);This provides an improved language compatibility with the application code without the need to modify the original underlying source code.
Open PL/I now supports the declaration and usage of variables of type AREA up to 2Gb in size. This provides you with improved functionality and greater language compatibility when migrating applications from a z/OS environment as there is no need to modify the code in order to deal with a maximum area size of 32Kb.
The PL/I Compiler and runtime now provide a DISPLAY() REPLY() syntax that is no longer dependent upon the use of the SYSIN and SYSOUT DD’s and that no longer causes behavioral differences if stream IO to SYSIN/SYSOUT is intermingled with programs using DISPLAY() REPLY().
Using a new Compiler directive –bitsltr to compile programs that have logic that is dependent on big-endian bitstring ordering enables you to utilize the code unchanged on Open PL/I little-endian platforms (such as Windows, Red Hat Linux, SUSE Linux). This enables you to migrate applications that make an assumption about bit ordering on the underlying operating system or hardware and to run them unchanged.
Compiling a PL/I program with the –initcall directive causes the specified program to be invoked prior to any user logic. This enables you to customize your environments and do things such as tracking which routines have been invoked, detect memory corruption prior to routine startup, establish database connectivity.
A PLIDUMP which was generated using the “F” option will now attempt to list all known information about files which have been accessed during the execution of the program and includes information about the last IO operation, key values, and a dump of buffers, if available. This enables you to identify more easily the cause of file-related failures and what file operations were in progress at the time of failure.
The following terminfo files have been added:
There have been a number of additions and fixes to existing terminfo files; refer to the Terminfo Database and Terminal Devices section of the documentation for full details.
There have also been a number of terminfo files that have been removed; refer to the Backward Compatibility section for a complete list.
This release provides the following new functionality: