Enhancements are available in the following areas:
Improvements have been made in the following areas:
This release includes the following new functionality:
The maximum console size of a COBOL application has increased. It can now be 255 lines by 255 columns, configurable using the screen_lines and screen_cols run-time tunables.
The following enhancements are available:
Support is provided in Enterprise Developer for accessing the Application Analysis Server which is part of the Micro Focus Enterprise Analyzer and Micro Focus COBOL Analyzer products.
If you have one of these products installed, you can connect to the Application Analysis Server from Server Explorer and access the Enterprise Analyzer web client. Enterprise Analyzer web client provides quick searches for repository objects, detailed code searches, diagrams, reports, and data item impact analysis and other features such as viewing and editing of business rules (separate license required).
Support is now available for extracting program logic from COBOL code and moving it to a new program. The following commands are available from the editor context menu:
In Eclipse, you can now refactor your code using the Extract to Section command available from the Refactor menu.
The following Compiler directives are new in this release:
The following Compiler directives have new options:
Support has been added to enable you to work with containers from the IDE. In particular you can now create a Dockerfile for a COBOL project, and build, debug and run a COBOL project in a container, all from the IDE.
Support has been added to enable the use of tools that are compatible with the Open Container Initiative (OCI) on platforms where they are supported. This is currently available on Red Hat Enterprise Linux 8.
Support for the following has been added to this release:
Support for the following has been added to this release:
The following enhancements have been made to the Data File Editor:
This following enhancements are available:
This release supports easier deployment of native COBOL applications from an Eclipse project. A new page in the project's properties, Micro Focus > Build Configuration > Deploy, enables you to specify a deploy folder and which files will be deployed. Building the project deploys certain executables and supporting files to this folder. In addition, you can archive and deploy the files on application servers, cloud storage such as AWS buckets and access the application files with AWS services, and so on.
The following enhancements are available:
The following enhancements are available:
This release provides the following enhancements:
The Micro Focus Secrets Vault provides centralized storage for sensitive information such as passwords, with some protection against accidental disclosure or discovery by unauthorized users. Prior to this release, the only supported storage mechanism was a conventional file containing encrypted data. In this release, the permissions on the storage file and on the Secrets configuration file are set more restrictively to help protect the secrets.
The X.509 digital certificates used to identify servers when making TLS (SSL) connections permit the use of fully-qualified domain names with wildcards for some parts of the name. This enables administrators to use a single certificate issued to, for example, *.mycorp.com for any number of servers with fully-qualified names like www.mycorp.com, server1.mycorp.com, and so on. These wildcard-bearing certificates are now supported by client programs using Micro Focus communication technology when validating a server's certificate.
In the Access Control Lists used for resource access control with LDAP-based security in Enterprise Server, the ".**" wildcard sequence now behaves more similarly to mainframe RACF. A number of additional options for wildcard processing are also available.
On Linux platforms, Enterprise Server now includes an External Security Manager module which integrates with the Pluggable Authentication Modules (PAM) operating system feature. The PAM ESM module can be used to authenticate Enterprise Server users with the same mechanism used for Linux users, or with any other mechanism available through PAM.
The standard for using X.509 digital certificates to authenticate servers when making TLS (SSL) connections is known as PKIX, for Public Key Infrastructure (X.509). It is defined by a series of IETF RFC documents, currently RFC 5280 and others. In previous releases, the certificate validation performed by this product did not conform to PKIX in a number of ways, most notably in using DNS address-to-name resolution in an attempt to match a certificate to a host. With this release, clients using Micro Focus Common Client technology, such as COBOL web service proxy programs, CAS utility programs, and customer applications that use the CICS Web Services Interface feature, will by default, use stricter procedures for validating certificates which more closely conform to PKIX. This improves TLS security and interoperability.
In this release the third-party components used for parsing XML data have been updated, or have had bug fixes integrated into the version used by Micro Focus, to address published security vulnerabilities. Also, XML external-entity support has been disabled except where it is required by a particular product feature; this prevents XML External Entity (XXE) attacks on customer systems by attackers who can trick a customer application into parsing a malicious XML document.
This release offers the following new features and improvements:
Fileshare password files can now be stored in the Vault Facility, ensuring that sensitive user credentials are encrypted. Firstly, create the password file in the usual way, and then upload it, with a path of microfocus/fh, using the mfsecretsadmin utility.
To ensure the Fileshare server uses the file stored in the vault, start the server with the /uv option.
Improvements are available in the following areas:
This enables support for administrative tasks such as database and transaction log archiving. It also enables the creation of new transaction logs when roll forward recovery is enabled.
This enables BTS output to be viewed when debugging a batch IMS application. Previously the job step had to complete before the trace was visible. This also enables you to view the trace output in an active SSTM job. Previously the MPR had to be stopped to make trace output visible.
To assist you with writing an exit, a template file, USERDB.CBL, and an explanatory text file, USERDB.TXT, are available with your IMS classic samples.
Improvements are available in the following areas:
The following features have been added to the JCL support:
The following library routines are new:
The following library routine contains new functionality:
Support for Db2 and Microsoft Azure databases has been added to the Micro Focus Database File Handler (MFDBFH). This support is equivalent to that of the existing databases.
The following features have been added for all databases:
The following enhancements have been made to the Micro Focus Unit Testing Framework:
On Windows, the Enterprise Developer setup file now installs the Microsoft Build Tools and the Windows SDK packages, as these are dependencies for a number of features and operations of the product.
You can use the Microsoft Build Tools and Windows SDK configuration utility to view the package versions in use in your COBOL environment. You can also use this utility to set the environment to use other versions of these packages that you have installed.
This release includes the following improvements:
Enhancements are available in the following areas:
Improvements in the compiler make it easier to migrate existing applications to new platforms. Support is available for:
Improved functionality for customers using Open PL/I to develop z/OS applications is available:
Support is available for the following features:
When stepping off the end of a PL/I ON-unit, the debugger attempts to determine the next debuggable statement, and then pause execution. This allows you to continue stepping through the program upon completion of the ON-unit. Stepping through a PL/I GOTO statement from an ON-unit continues to be supported as well.
In this release, the variable's address and size are now being stored away for watch instead of the procedure name and variable name. This allows the address/size to be monitored from the time it is established until you cancel the watch. By doing this, the debugger is stopped as soon as it recognizes a change of value - regardless of where it is in the user program.
Since the watch is active until you cancel it, it is possible to be watching an address/size which is no longer allocated or active depending on the flow of the user program. In this situation, execution will be stopped if/when the memory space is reused for some other reason.
The following enhancement is available:
The following functionality is new in this release: