New Features in Enterprise Developer 7.0

Micro Focus COBOL Extension for Visual Studio Code

Back to Top

The new Micro Focus COBOL extension for Visual Studio Code is available on the Microsoft Visual Studio Marketplace. This provides edit, compile and debug support for Visual COBOL and Enterprise Developer users in Visual Studio Code.

Note: The new Micro Focus COBOL extension is not included with the Enterprise Developer installer.

.NET Core Support

Back to Top

Support has been added for creating, building and running .NET Core projects using the dotnet command. This new support is in addition to the ability to work with .NET Core projects in the IDE.

Assembler Support

Back to Top

This release includes the following enhancements:

  • Support for Assembler data table generation on UNIX and Linux - a new command-line executable, MFMODGEN, is available on these operating systems to generate an Assembler data table (.MOD file) from an Assembler source file.

    This feature is the only Assembler functionality currently supported on UNIX systems. The rest of the Micro Focus Assembler functionality is supported for 32-bit Windows only.

CICS Support

Back to Top

CICS support in development has the following new features:

  • A 64-bit BMS Compiler on Windows and UNIX - the command-line utility, MFBMSCL, is now available in 64-bit format on Windows as part of Enterprise Developer and on UNIX as part of Micro Focus Enterprise Developer Unix Components.

CICS support in deployment has the following new features:

CICS support inside Visual Studio:

  • The support for viewing CICS (PCT, PPT and FCT) resources inside Visual Studio is now a full support and no longer a Technical Preview.

COBOL Language

Back to Top

The following enhancements have been made to the Micro Focus COBOL language:

  • .NET COBOL data type to hold strings of utf-8 characters - support is now available in .NET COBOL for the PIC U data type. This was already available for native COBOL, to support its introduction by IBM in Enterprise COBOL version 6.3.
  • The DYNAMIC LENGTH clause, which enables a data item to vary in length at run time, is supported for native COBOL code. Again, this is in response to its introduction by IBM in Enterprise COBOL version 6.3.
  • The following date-format-checking intrinsic functions have been added: TEST-DATE-YYYYMMDD and TEST-DAY-YYYYDDD.

Code Analysis

Back to Top

This release includes the following enhancements:

  • Get Direct References command - you can use this command to see if changing a file will affect the other files in your project as well as the files in the whole application. In Visual Studio, you can access this command from the context menu for COBOL files in Solution Explorer or from the Analysis Server window.
  • The Data Flow Analysis is now available in both a tree and a graph view.
  • The Code Analysis functionality is now available for the Procedural Multi-Output Project (.NET Framework) type.

Code Set Support

Back to Top

The following enhancements have been made to the integrated code set translation support:

  • Arabic support for Enterprise Server applications is available.

    If you are building Arabic support into Enterprise Server applications, your terminal emulator must support the Arabic EBCDIC 420 code page.

    Support is added by building your applications and configuring your enterprise server regions with the MFCODESET variable set to the supported country code (0420). Your product's in-built code set translation utility performs translations between the ASCII 1256 Arabic code page on your enterprise server region, and a terminal emulator that supports the Arabic EBCDIC 420 code page (for example, IBM's Personal Communications emulator).

    There are some considerations when working with a bi-directional language such as Arabic; these are discussed in Arabic support considerations.

Compiler Directives

Back to Top

The following Compiler directives are new in this release:

  • PANVALET-INCLUDES-IN-COMMENTS - This directive controls whether ++INCLUDE statements in comments are actioned or not.
  • EXECSQL-FLAG - This directive defines whether syntax reporting should emulate that of the DB2 preprocessor, the DB2 coprocessor, or to allow all syntax variations of both.
  • RM-FILE-ERRORS - This directive generates run-time system errors for certain file conditions, even when a FILE STATUS clause is present; this is to emulate RM/COBOL behavior.

The following Compiler directive option has been deprecated:

  • ILCLR(2) - this is as a result of deprecating support for versions 3.0 and 3.5 of the .NET Framework. Applications that have this option set will produce an E level message when compiled in this release of Enterprise Developer.

Containers Support

Back to Top

Support for containers in Visual Studio has the following enhancements:

  • You can now add a Dockerfile to native Micro Focus Unit Testing projects in Visual Studio and run the tests in a container.
  • Projects with Docker support now include an additional Containers property page. From it you can:
    • Specify any build, debug and run arguments for the image that will override the arguments specified in the project's dockerfile.
    • See all command-line arguments that will be applied when you build the image.
    • See the arguments that will apply when you run the container, or debug an application running in a container.
  • The Add COBOL Docker Support dialog box now shows all available images, and supports images provided with a Patch Update release of this product suite.

    The versions of the Runtime Image and the Built Tools Image must match therefore the dialog box only shows the Built Tools Image that match the one for the runtime. For example, if you use a Patch Update 1 Build Tools image, the dialog box only shows the relevant Patch Update 1 Runtime image.

    The dialog box shows only the images that match the major release version (or a Patch Update of it) of your installed product. They must target the same platform (x64 or x86) as well. If you want to specify images from different major product versions, you need to edit the Dockerfile manually.

Database Access - HCOSS Manage Connections Tool

Back to Top

This release includes:

  • Enhanced usability features around connection error diagnosis and SQL Server connection/installed ODBC driver selections.
Attention: This feature is in Early Adopter Program (EAP) release status. We intend to provide the finalized feature in a future release. Please contact Micro Focus Customer Care if you require further clarification.

Database Access - MBDT Utilities

Back to Top

This release introduces:

  • The SQLTUL utility, which is equivalent to the z/OS DB2 DSNTIAUL program.
    Attention: This feature is in Early Adopter Program (EAP) release status. We intend to provide the finalized feature in a future release. Please contact Micro Focus Customer Care if you require further clarification.

Database Access - OpenESQL

Back to Top

This release provides the following enhancement:

  • New OpenESQL TRACELEVEL=5 option - native OpenESQL applications can now trace ODBC calls to the database vendor’s ODBC driver, recording the start and stop times of each call’s execution. OpenESQL tracing can now provide more detail on where an SQL application is spending execution time, in the OpenESQL layer or the underlying ODBC driver layer.

Data File Tools

Back to Top

This release includes the following enhancements in the Data File Editor:

  • New Data Explorer for working with data sets - a new Data Explorer enables you to connect to either an ESCWA service or directly to an enterprise server region to access a catalog when working with data sets in the editor.
  • Multiple record selection- you can select multiple records and, where appropriate, can perform certain actions on more than one record at once.
  • Cut, copy, and paste functionality - traditional cut, copy, and paste functionality (including the standard Ctrl+X, Ctrl+C, and Ctrl+V shortcuts) is now available throughout the editor.
  • New filter creation - a new process for creating filters has been introduced. A filter consists of one or more sets of conditions, and the resulting filter can include or exclude those records selected. The previous filter process is still available, but has been marked as deprecated.
  • Remote filtering - functionality has gone into Fileshare Server which allows filtering to occur server side when opening data sets on remote enterprise server regions. The filter process results in only those filtered records being downloaded to the data file editor client.
  • Find/replace functionality - you can search records in a data file to identify specific strings, and then if required, replace them.

Enterprise Server

Back to Top

This release includes the following enhancements:

  • Multiple Network Interface support - there is improved support for multiple network interfaces in some components, including better awareness of network interfaces and control over networking. This is a partial implementation and will be enhanced in future releases.
  • Extended IPv6 support - support is available in Micro Focus Directory Server (MFDS) and in the Micro Focus Communications Server (MFCS) listener for multiple IPv6 addresses.

    In release 6.0, you could only configure MFDS and MFCS listeners to listen on a single IPv6 address. In release 7.0, by default, MFDS and MFCS now listen on all configured IPv4 and IPv6 addresses, and can also be configured to listen on a combination of specific addresses.

  • HTTP improvements:
    • Additional security measures for HTTP, such as security-related headers.
    • Chunking support for large HTTP messages makes it possible to retrieve very large files from Enterprise Server regions.
    • Enhancements to CICS Web Interface and CICS Web Services.
  • Application Diagnostic Reporting for Enterprise Server - Application diagnostic reporting collects and packages a number of reports, trace, and log files into a single report file. See Application Diagnostic Reporting for Enterprise Server for more information.
  • Enterprise Server now supports automatic reconnection to the standby Queue manager in an Multi-Instance Queue Manager. See Reconnecting to an MQ Server in a Multi-instance Queue Manager and Enterprise Server XA Reconnect for more information.
  • The casmgr process has been optimized to improve the use of initiators when dispatching jobs across a PAC. In addition, improvements have been made to the way it manages the queue of jobs waiting to be dispatched.
  • Information has been added describing the best practice and the recommended approach you should adopt when performing a Patch Update to your PAC environment. See Performing a Product Upgrade to a PAC Environment for more information.
  • New operating modes, upgrade and quiesce, have been introduced for Performance and Availability Clusters (PACs). These operating modes can be used to facilitate the installation of product updates that introduce incompatibilities between PSOR data structures. You can check for incompatibilities using the new caspac utility option CheckCompat. An upgrade mode can be set when starting the first enterprise server region in a new PAC using the new casstart utility start-type option u. This upgrade mode will prevent participating enterprise server regions from processing batch workloads as part of its normal operation, and any EXEC CICS START requests will be rejected. See casstart and caspac in your product Help for more information.

    When enough enterprise server regions have been switched over to the new PAC, the old PAC can be set to operate in the quiesce mode. This prevents further batch workload and EXEC CICS START from being processed.

    The new PAC can now be switched to running mode so that batch workload and EXEC CICS START are enabled for processing again.

    Note: Before setting the new PAC mode to running, you must switch enough enterprise server regions to the new PAC to enable it to service the expected workload.

Enterprise Server Common Web Administration (ESCWA)

Back to Top

This release offers the following improvements:

  • MFDS User Interface functionality replacement - ESCWA now replaces the MFDS inside the IDE as the engine that provides access to and management of regions. ESCWA provides all the functionality that was previously available from MFDS. This release includes the following enhancements:
    • Delete all regions.
    • Session list.
    • Renew listening addresses.
  • ESMAC User Interface functionality replacement - the following ESMAC features have been implemented in ESCWA:
    • Resource Filtering. See CICS Resources for more information.
    • Millisecond support. See Threshold, Monitor, and Active PCT for more information.
    • Control the scope for all changes to timeouts, trace flags, and memory strategy when applied to regions in a PAC. See ES Control for more information.
    • Enable Application Diagnostic reporting. See ES Control and Application Diagnostic Reporting for Enterprise Server for more information.
    • Submission of local jobs from the JES Control page when CASRDO44_NEWSUB=OFF has been specified. See JES Control for more information.
    • View and reply to pending ACCEPT FROM CONSOLE statements. See Pending Replies for more information.
    • The messages after a JCL job has been submitted are now correctly JSON formatted. This page now works in ESCWA when MFJUXIT is enabled.
  • Import, export, and copy regions - you can now use the UI to export and import regions in various formats, including use JSON. You can:
    • Copy regions between Directory Servers
    • Import and export regions in JSON, XML or in the .dat legacy format. The legacy format can be converted to a modern format.
  • Mainframe Access (MFA) administration - ESCWA provides a modern Web UI and does not require you to use a separate terminal application. Features include:
    • Log in or off from MFA.
    • Change your MFA password.
    • View MFA server tasks.
    • Retrieve the XDBOUT log (Web UI).
    • Retrieve the JES spool files by DD Name (API).
    • Set the MFA and JES tracing level.
    • View the active MFA users.
    • Invalidate active user sessions.
    • View mainframe/MFA statistics.

    See Mainframe in the Enterprise Server Common Web Administration chapter for more information.

    The MFA API library has been exposed to enable you to test and use the requests that are provided. See MFA Interactive API Library for more information.

  • CICS resource support - the following resources are supported:
    • Resource Name List (RNL) CICS resource.
    • Thresholds CICS resource.
    • Extended Architecture Table (XAT) CICS resource.
  • Scale-Out and PAC administration - you can now:
    • Monitor Redis Sentinel and Cluster instances when used for Scale-Out Repositories.
    • Specify that all changes to timeouts, trace flags, and memory strategy can be applied to one of three options:
      • Only the local region.
      • All members of a PAC except the regions where local changes have been made.
      • All members of a PAC.

      You can configure this in ESCWA with the Apply Scope field on the ES CONTROL page. Alternatively, you can use the casutl utility with the /w option. See casutl for more information.

  • Multi-Network Interface Card support - ESCWA now enables you to configure Communications Servers and Listeners to listen on multiple IPv4 and IPv6 addresses. Previously, they were limited to listen on either all IPv4 addresses, or a single IPv4 or IPv6 address. Now a combination of any of the following can be used:
    • One or more specific IPv4 addresses.
    • One or more specific IPv6 addresses.
    • All IPv4 addresses.
    • All IPv6 addresses.
  • A new filter field resFilter has been added to the following ESCWA and ESMAC resource listing modules:
    • Every resource in By Type
    • Every resource in By Start L
    • Resource lists under Groups
    • Every active resource type except Locks

    This parameter will filter the list of resources displayed by ESCWA and ESMAC. In addition, a new environment variable ES_RDO_MAX_RESOURCES has been added that enables you to specify a limit to the number of records displayed. For JSON requests, the list being truncated is indicated by the addition of the JSON property "truncated": true.

Enterprise Server for .NET

Back to Top

This release includes the following enhancements:

  • CICS time calculations - ABSTIME, EIBDATE, EIBTIME, FORMAT TIME, and CONVERT TIME have been improved.
  • CICS condition handling has been improved.
  • A new option, console message maximum, enables you to specify how many console messages are retained. Previously, this value was fixed at 10000.

Enterprise Server Security

Back to Top

This release includes the following enhancements:

  • MLDAP ESM caching - the MLDAP ESM Module now implements LDAP search-result caching. This is controlled by the existing Security Manager cache settings, so that many installations will have this activated automatically. See the product Help for details.
  • Vault Hashicorp support - support is available for using a Hashicorp KV2 vault server as a local or remote vault.

IMS Support

Back to Top

This release includes the following enhancements:

  • An IMS Automated Operator Interface (AOI) - allows an application program to send IMS commands to, and receive responses from IMS Transaction Manager using the DL/I CMD and CGMS functions. This support includes:
    • Enterprise Developer and Enterprise Server support IMS DL/I functions CMD and GCMD across all language interfaces. These functions are used to send IMS commands and receive responses.
    • Commands can be sent from applications compiled either ASCII or EBCDIC.
    • Commands sent using AOI are limited to those supported in Enterprise Developer and Enterprise Server.
    • You can install an exit program that enables programming support for commands not directly supported by Enterprise Developer and Enterprise Server.
    • The IMSAO.CBL and IMSAO.JCL sample files, located in %PUBLIC%\Documents\Micro Focus\Enterprise Developer\Samples\Mainframe\IMS\Classic\Examples, are provided to demonstrate the use of AOI.
    • The AOEXIT.CBL program, located in the same place as the other AOI sample files, is an example of an installed exit routine for processing of AOI commands. Instructions for this interface are described in the program source.
  • The JES aliasing feature can be used with IMS DLI and BMP applications run from JCL.[11]
  • APARM handling has been updated to use EBCDIC APARMs obtained from EBCDIC applications. In addition, the APARM positional parameter for DLI has been changed from 19 to 20 to be consistent with the IBM IMS documentation. The APARM positional parameter for BMP applications remains at 19. [22]
  • The ES_IMS_APARM_DLI environment variable has been added to enable the APARM handing behavior of previous releases. See ES_IMS_APARM_DLI for details. [22]
  • The IMS editor in Visual Studio now offers Renumber and Unnumber commands for PSB files.

JCL Support

Back to Top

This release includes the following enhancement:

  • New Spool and Catalog windows - the Spool and Catalog windows have been updated and are now based on ESCWA functionality. You can view and modify the details of a job and a catalog, create new items, all in one page of the window.

Library Routines

Back to Top

The following library routines are new:

  • CBL_GET_ERROR_INFO - enables error processing routines to establish the location of the error that occurred to cause the error processing routine to execute. This is available on a restricted range of platforms.


Back to Top

AutoPass licensing technology

In this release, Micro Focus brings in the power of the in-house Micro Focus AutoPass licensing technology alongside Sentinel RMS. AutoPass has the following additional benefits compared to Sentinel RMS:

  • Usage logging which enables you to monitor the product usage. You need to install the AutoPass License Server in order to do this.
  • Ongoing support for all platforms that this product is available for.

Features include:

  • Installing this release installs both the AutoPass Daemon and the Sentinel RMS License Manager. Both of them are available in the Micro Focus License Administration tool.
  • You can have both AutoPass and Sentinel RMS licenses installed on the same machine. Optionally, you can switch off the licensing technology you do not use.
  • If you are an existing user of a Visual COBOL or an Enterprise Developer product, you only need an AutoPass license if you want to utilize usage logging or if you want to use your product on a platform on which Sentinel RMS is not supported.
  • If you are a new user of the Micro Focus COBOL products, you will normally be issued an AutoPass license.
  • Micro Focus will continue to provide Sentinel RMS in future releases of this product.
  • AutoPass licenses should be installed into the existing Micro Focus License Administration tool, and not in the AutoPass License Server.
Important: The SafeNet Sentinel licensing system has been deprecated and will be not available in this product starting with the next major release after release 9.0.

The SafeNet Sentinel licenses will not be supported after release 9.0 and you need to use AutoPass licenses if you use these releases.

You can replace your SafeNet Sentinel licenses with AutoPass licenses starting with release 8.0. Contact Micro Focus Customer Care for further information.

Installing licenses at the command line

On Windows, Micro Focus License Administration is now also available as a command-line utility.

For more about AutoPass and usage logging, and about Micro Focus License Administration, see Managing Licenses.

Mainframe Access (MFA)

Back to Top

This release includes the following enhancements:

  • Improved file download and upload speeds - offers over seven times faster speeds for compressed files larger than 64K, and almost four times faster speeds for uncompressed files over 64K. This requires that you update both the Mainframe Access client and server, if you are using an older version of them.
  • Endevor transaction performance improvements - transactions with Endevor have been improved and are now around two times faster.
  • Support for MFDAS load and unload - load and unload-specific load library members are now available from the MFDAS command line. This enables you to interact remotely with Load libraries from the MFDAS command line.
  • SCLM export protection - you can now configure the MFA components to respect the SCLM managed flags. In this way, you can prevent outside source control changes to your managed datasets.

The Micro Focus Database File Handler

Back to Top

This release includes the following enhancements to the Micro Focus Database File Handler:

  • Oracle support: support has been added for use with Oracle databases (version 19c and later). Support is mostly equivalent to that of the existing databases, except that ODBC connectivity is not supported; connections must be made directly with the databases, using Oracle's OCI interface.
  • The dbfhview command line utility: a command line utility that generates database views from your Data File Editor structure files. These views allow you to view your data once it's stored in a datastore.
  • The mfdbcatc command line utility: a command line utility that helps you to relocate a disk-based catalog to a database. It can scan the current catalog, then generate a deployable response file that attempts to maintain the current structure of the catalog.
  • COBOL Run-Time System support for datastores: Library routines and variables that typically deal with files and folders on disk are now capable of also handling the SQL URLs required to reference file and folders in a datastore. Where appropriate, this is noted in the library routines documentation, and the topic 'The Datastore URL' gives full details of the SQL URL required.
  • Support has been added for Microsoft SQL Server and PostgreSQL users to host datastore, region and cross-region database resources in a single physical database. This support was already available for Db2 and Oracle users. See Using a Single Database for more details. [6]
  • Datastores, regions, and cross-regions being hosted within the same physical database can now share connections. This greatly reduces the number of connections an MFDBFH application would require at any one time. See Sharing Database Connections for more details. [6]

The Micro Focus Unit Testing Framework

Back to Top

The following enhancements have been made to the Micro Focus Unit Testing Framework:

  • The MFUPP preprocessor has been introduced to provide a seam between your program and a unit test. This seam lets you access the internals of a program under test, allowing you to create granular unit tests from paragraphs or sections. The MFUPP preprocessor also provides the ability to mock programs or stub programs out to create a unit test.

PL/I Support

Back to Top

Enhancements are available in the following areas:

PL/I debugger:

  • PL/I integrated debugger support has been added to the Visual Studio IDE, which provides a much improved user experience for PL/I developers. The CodeWatch debugger has been removed.
  • PL/I projects now support debug profiles, a feature of Visual Studio, where a debug profile stores a set of properties which specify how to start debugging the application. You can create and manage multiple debug profiles available on the Debug tab in the project's properties.
  • Much larger call stacks are now supported.

PL/I compiler compatibility:

  • New statements supported - DEFINE STRUCTURE, LOCATE.
  • Improved compatibility for the DEFAULT RANGE statement.
  • New built-in functions - AUTOMATIC, ENTRYADDR built-in function and pseudovariable, HEXDECODE, INLIST, ISLL, ISRL, REPLACE, and TIMESTAMP.
  • Support for the DIMACROSS attribute and for the PARM attribute on a declaration.

PL/I compiler functionality:

  • You now receive warnings when redundant WHEN clauses appear in a SELECT statement.
  • Improved compiler listings to show more attributes for parameters.
  • The PL/I error messages in the product Help are now in sync with the messages shown in the product.

PL/I EXEC Preprocessor:

  • Provides information about host variable references/modifications for the background parsing.
  • Support for DB2 style comments in EXEC SQL Statements.

PL/I Macro Preprocessor:

  • The SCAN option of the ANSWER statement is now supported.
  • Improved compatibility of COMPILEDATE and COMPILETIME built-in functions.

PL/I Run-Time System:

  • The behavior of PL/I ON FINISH now matches IBM's behavior.
  • Improved compatibility for the JSONPUTVALUE built-in function - it now supports multi-dimensional arrays within structures.
  • Improved compatibility for the XMLCHAR built-in function.
  • PLIDUMP now checks the allocated memory chains for corruptions.
  • PLIDUMP can now display much larger automatic variables and parameters without consuming excess memory and CPU resources.
  • Support for the L format PUT EDIT directed I-O.

Visual Studio Integration

Back to Top

This release includes enhancements in the following areas:


  • Code cleanup - Visual Studio now supports a variety of code cleanup options for COBOL which you can apply during formatting. These enable you to update any existing code, or enforce rules for new code for specific keywords or operators.
  • EditorConfig file support - you can now create .editorconfig files with the code style settings in the IDE, and share the file within your organization to ensure consistency of the code.
  • The Force uppercase command is now available for Assembler, BMS, and JCL files opened in Visual Studio.