This release provides enhancements in the following areas:
Integration with Visual Studio 2015
Back to list
This release provides a new
Enterprise Developer flavor that takes advantage of the new features of Visual Studio 2015, including:
- Light Bulbs
- You can use the light bulb feature () to quickly implement interfaces or add the USING directive.
- Compatibility (Project Round-Tripping)
- Enterprise Developer supports the Visual Studio project round-tripping feature which enables you to work with COBOL projects in Visual Studio 2012, Visual Studio 2013 or in Visual Studio 2015 without the need to upgrade the project file.
- .NET Framework 4.6 Compatibility
- Provides support for creating managed COBOL applications that target version 4.6 of the .NET Framework.
- Microsoft Help Viewer 2.2
- Provides support for the
Micro Focus Help in Microsoft Help Viewer 2.2.
For more information see
Related Information at the end of this topic.
General IDE enhancements
Back to list
- Menu items - the following Micro Focus utilities were previously available under the
Tools > Micro Focus menu and have been moved as follows:
- ADO.NET Connection Editor - now accessed from
View > Micro Focus SQL Tools.
- MFA Compare and Synchronization Monitor - now available directly under the
Tools menu.
- MFA Server Access Configuration - now available directly under the
Tools menu.
- OpenESQL Assistant - now accessed from
View > Micro Focus SQL Tools.
- OpenESQL Configuration Utility - now accessed from
View > Micro Focus SQL Tools.
- Web Service Client - now accessed by creating a new project of type "Web Service Client Application from JSON/REST" - click
File > New > Project > COBOL > Native > Web Service Client Application from JSON/REST.
- Managed COBOL project properties - a new setting,
Expose group linkage items to managed code, is now available on the
COBOL tab in the properties of managed COBOL projects. Checking this sets the ILSMARTLINKAGE directive that specifies that group linkage items in your code are to be exposed as properties of a class. A related button,
Options, enables you to also specify whether to remove specific prefixes from the names of COBOL data items, whether to make the new classes serializable, expose Linkage Section items as nested classes of the program class or to limit the property generation to non-redefining elementary items.
- PL/I project properties - there is now a new page,
Assembler, in the project properties of PL/I Mainframe Subsystem Projects that enables you to set properties for configuring PL/I Assembler applications.
- Resetting the file properties - a new button,
Use Project Defaults, on the file property pages of COBOL files in native projects now enables you to reset the file properties of COBOL files in native COBOL projects.
For more information see
Related Information at the end of this topic.
Building applications
Back to list
Enterprise Developer now supports Visual Studio's parallel builds for COBOL projects. Parallel building enables you to build multiple projects faster on multi-CPU machines. Following this change, in order for your multi-project solutions to build in parallel successfully, ensure that the project dependencies and build order are set correctly for your solution using
Project > Project Dependencies. For more information about parallel building, see
Tips on Building COBOL in your product help and your product Release Notes.
Note: Parallel builds are not supported
with Mainframe Subsystem COBOL projects.
For more information see
Related Information at the end of this topic.
COBOL editor
Back to list
The COBOL editor includes the following enhancements and new features:
- Improved Intellisense writing assistance for COBOL in both native and managed COBOL:
- Context sensitive suggestions - IntelliSense only shows suggestions that are relevant for the position of the cursor in the code or for the type of project.
- Enhanced completion lists - lists include any relevant COBOL verbs, clauses and words, copybooks, code templates, data items and section and paragraph names.
- Intelligent assistance with completing statements - when you have entered a COBOL verb, IntelliSense shows suggestions for the relevant clauses and identifiers that you can use to complete the statement.
- Automatic completion for single items - IntelliSense automatically inserts single suggestions in the code.
- Qualifying non-unique names - IntelliSense qualifies data items whose names are not unique.
- Configuration preferences for IntelliSense - enable you to configure what suggestions appear in the completion lists, whether suggestions are added in insert or overwrite mode, and the case of the inserted words.
- Snippets - code snippets are now included in the IntelliSense suggestions.
- $IF-$ELSE-$END statement colorization - parts of a $IF Compiler-control statement that are not executed are now colored in grey.
- $REGION statement - support is provided for the $REGION Compiler-control statement. You can use $REGION - $END-REGION to surround blocks of code that you want to folded or expand in the editor.
- Copybook glyphs () in the left-hand margin on a copy line - indicate that a copybook can be expanded inline.
- Creating copybooks from selection of code - a new context menu command,
Extract to Copybook in the editor enables you to move a selection of COBOL code into a new copybook file. The file is added to the project and the code in the original program is replaced with a COPY statement that refers the new copybook.
- Expanded copybook view - provides indicators for read-only copybooks
- Outlining - outlining is now available on comment blocks, paragraphs and on $REGION and $IF statements.
- Task List comments - the COBOL editor now provides support for Visual Studio-style Task List comments in COBOL. Typing TODO, HACK or UNDONE in the code immediately after the declaration of the COBOL comment (*>, *>> or * in column 7) creates a task that appears in the
Task List window.
For more information see
Related Information at the end of this topic.
PL/I editor
Back to list
The PL/I editor has the following enhancements:
- Support for opening include files from within the editor
- Comment and uncomment toolbar buttons
- Initial support for IntelliSense
- Red squiggles
- Margins
For more information see
Related Information at the end of this topic.
CICS Web services (Technology Preview)
Back to list
Enterprise Server has been extended to provide a CICS Web Services capability compatible with the mainframe.
A new CICS Web Service wizard enables you to generate CICS Web service providers and requesters using either a CICS COBOL application or a WSDL file as input. This enables you to develop and test, including end-to-end testing, CICS Web Services for deployment to the mainframe.
For more information see
Related Information at the end of this topic.
Code analysis
Back to list
Enterprise Developer now offers more advanced code analysis features and enables you to run various analysis queries (rules and groups of rules called rule sets) against your code to ensure adherence to standards such as standards for coding or performance.
You can run analysis rules against programs in a project in the IDE at user request or you can run analysis rules at the end of a project's build.
For more information see
Related Information at the end of this topic.
Code coverage
Back to list
Enterprise Developer now provides support for code coverage of native COBOL applications directly from within the IDE where code coverage uses the Test Coverage functionality. You can produce code coverage reports for applications running in the COBOL run-time and for applications that run in
Enterprise Server.
To produce reports, you need to enable code coverage in a project's properties, compile your application and then run your application with code coverage to produce the relevant reports. For applications that require an
Enterprise Server instance, you start the enterprise server with code coverage.
For more information see
Related Information at the end of this topic.
Compiler directives
Back to list
The following Compiler directives are new in this release:
- EOF-1A
- Treats a 0x1a character in the source file as the end of file.
- NLS-CURRENCY-LENGTH
- Specifies the number of bytes to allocate for the currency symbol in a PIC field.
- NULL-ESCAPE
- Treats a 0x00 character in the source file as an escape character for other non-printable characters in the source code.
The following Compiler directives contain new parameters in this release:
- DBSPACE
- The new parameter 'MIXED' extends the DBSPACE directive to be able to evaluate data items in programs that contain a mix of single-byte and double-byte strings.
For more information see
Related Information at the end of this topic.
Converting additional directives to project's properties
Back to list
The
Update Project Properties utility allows you to convert additional directives in your project to project properties. This option is presented on opening a project. You can select to not show this dialog again by unchecking
Check Additional Directives for project properties in
Tools > Options > Micro Focus > General.
For more information see
Related Information at the end of this topic.
Data File Structure command line utility
Back to list
The Data File Structure Command Line (DFSTRCL) utility is a DOS-based command line utility that enables you to create record layout (.str) files from COBOL debug information (.idy) files. You can use the utility to process a single
.idy file or batch process up to 100
.idy files.
For more information see
Related Information at the end of this topic.
Data File Tools (Technology Preview)
Back to list
Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability; however, this feature is not intended for production use and it is not supported as such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA level and if it is, then the functionality provided might differ considerably from this technology preview.
The Data File Tools (Technology Preview) is a new standalone text editor in which you can create and edit data files. By nature of it being a 'technology preview' product, it does not currently include all the functionality that was available in the previous version of Data File Tools - now referred to as Classic Data File Tools. If you require any of the functionality not provided in this version, you can still use the classic version by accessing it in the usual way.
To run Data File Tools (Technology Preview), type
mfdatatools2 from
Enterprise Developer's command prompt
or a terminal.
To use the new editor directly from the Visual Studio IDE, clear the
Use classic data file tools check box, available from
. When cleared, the Data File Tools (Technology Preview) version is used, when possible. When this editor does not support the action you are attempting to complete, Classic Data File Tools is used instead. This check box is selected by default.
For more information see
Related Information at the end of this topic.
Database Access
Back to list
This release provides the following enhancements to database access:
- COBSQL
- This release provides:
- Selection and configuration of the Oracle Pro*COBOL preprocessor for compiling COBSQL applications in project properties on the
SQL tab.
- Support for COBOL directives SOURCEFORMAT=TERMINAL and SOURCEFORMAT=VARIABLE for Pro*COBOL applications.
- HCO for DB2 LUW
- This release provides:
- GUI versions of data migration tooling
- A new tool that enables you to bind or rebind all packages. See
BindAll Packages Tool for details.
- Support for MFHCO mode across all platforms by default via the new HCO (NOHCO) DB2 compiler directive option. See the
HCO DB2 compiler directive option topic for details.
- A new DB2 compiler directive option, OPTPER (NOOPTPER), that enhances performance for CHARSET EBCDIC processing. See the
OPTPER DB2 compiler directive option topic for details.
- A new DB2 directive option, BINDDIR, which specifies an alternative directory in which to write the DBRM file created during compilation.
See the
BINDDIR DB2 compiler directive option topic for details.
- 64-bit support for PL/I on appropriate platforms. See
Additional Software Requirements on Windows for details.
- HCO for SQL Server
- This release provides:
- Support for the DATA-CHANGE-TABLE-REFERENCE clause.
- The following HCOSS Add-Ins have been converted to VSPackage Extensions:
- HCO for SQL Server Tools, now available under
View > Micro Focus SQL Tools
- Options for HCO for SQL Server Tools, now available under
Tools > Options > Micro Focus
- Context Help is now provided for:
- Options for HCO for SQL Server tools
- For each tool in the HCO for SQL Server user interface
- OpenESQL
-
- ADO.NET Connection Editor
- In this release:
- The ADO.NET Connection Editor has been redesigned using a series of Wizards that guide you through the processes of adding, copying, and removing connections.
- Context Help is now provided for the main window, and each Wizard page and dialog box.
- Date/Time Processing
- This release provides streamlined datetime processing for ODBC and ADO.NET.
- Performance
- This release includes a new SQL compiler directive option, OPTPER (NOOPTPER), that enhances performance for CHARSET EBCDIC processing. See the
OPTPER SQL compiler directive option topic for details.
- PL/I
- This version provides 64-bit support for PL/I on appropriate platforms. See
Additional Software Requirements for details.
- PostgreSQL
- In this release, PostgreSQL 9.4 has been tested with OpenESQL and OpenESQL Assistant with the following PostgreSQL software:
- Server software
- PostgreSQL EnterpriseDB version 9.4.1-3
- Client software
-
- psqlODBC driver version 09.03.04.00
- Npgsql ADO.NET 4.0 driver version 2.2.5
PostgreSQL 9.4 has been tested with OpenESQL and OpenESQL Assistant on the following Windows platforms:
- Windows 32-bit
- Windows 64-bit
Note: Micro Focus provides compatibility for PostgreSQL but does not directly contribute to or support the PostgreSQL open source project. Any issues relating to PostgreSQL functionality should be addressed through an open source support vendor.
- SQL Server
- This release provides support for the SQL Server OUTPUT clause.
- Mainframe Batch Database Tools (MBDT)
- Windows only. This release includes mainframe batch utilities that provide the following functionality for Oracle, DB2 LUW, and SQL Server agnostically, as well as specifically for HCO for SQL Server:
- DSNTEP2
- DSNUTILB LOAD
- DSNUTILB UNLOAD
- 32-bit and 64-bit support
- New batch configuration utility
- SQL Option for DB2
- This release provides the following z/OS DB2 version 10 enhancements:
- Extended support for implicit casting
- Greater timestamp precision for applications
- Support for TIMESTAMP WITH TIME ZONE
This release provides initial XML support for the XDB engine.
- XA Switch Modules
-
In this release, the XA interface has been redesigned to provide:
- Consistent look and feel for SQL Server, DB2, and Oracle user personalization
- Consistent look and feel for both RM dynamic and static registration (SQL Server, DB2, Oracle, generic one-phase commit)
- Additional support for two instances of the same switch module using
CICS and
Web Services applications via the new XAID compiler directive
- Using a specified XA resource only with batch applications executing under
Enterprise Server
For more information see
Related Information at the end of this topic.
Enterprise Server for .NET
Back to list
This release provides enhancements in the following areas:
For more information see
Related Information at the end of this topic.
Environment Variables
Back to list
The following new environment variables are available:
- MFJ_REPRO_EMPTY
- Enables or disables the ability for the IDCAMS REPRO action to copy from a pristine VSAM file. Permissible values: Y or N.
- ES_JESYSMSG_RESTRICTED
- When system message spool files are being routed directly to the Output queue, by using ES_JESYSMSG_OUTPUT, you can hold back spool files based on their class, by using ES_JESYSMSG_RESTRICTED. Permissible values: class names or numbers entered as a continuous string; for example, ES_JESYSMSG_RESTRICTED=ABC123.
For more information see
Related Information at the end of this topic.
File handling
Back to list
This release contains the following new configuration options:
- ACUFH
- Enables or disables the use of the ACU file handler (ACUFH), which is required to handle Vision and RM/COBOL indexed files.
- ESACUFH
- Enables or disables the use of the ACU file handler (ACUFH) for file handling operations running under Enterprise Server. ACUFH must also be enabled for this option to take effect.
For more information see
Related Information at the end of this topic.
IFileshare - Fileshare support under Enterprise Server (Technology Preview)
Back to list
Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability; however, this feature is not intended for production use and it is not supported as such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA level and if it is, then the functionality provided might differ considerably from this technology preview.
Should you wish to test and provide feedback for this feature please contact Micro Focus Support Line for instructions on how to enable the new functionality.
You can configure iFileshare to offer enhanced availability for mission critical files by configuring a high availability group, consisting of a primary iFileshare server and a number of stand-by servers. (Currently, this type of configuration only supports having one stand-by server)
Files that are critical to your application can be replicated from a primary server onto the stand-by servers. Should the primary server fail, you have up-to-date data (minus any in-flight transactions) available.
To reduce the complexity and to increase the stability of an iFileshare high availability group, it is recommended that each region is configured as a dedicated iFileshare server. If other Enterprise Server work is hosted within the group, the setup must be consistent on each server so that in the event of a fail-over, the non-Fileshare work can be continued on the new primary server.
For more information see
Related Information at the end of this topic.
Library routines
Back to list
The following library routines are new in this release:
- CBL_MANAGED_SESSION_GET_USERDATA
- Retrieves user data saved in the current RunUnit.
- CBL_MANAGED_SESSION_SET_USERDATA
- Sets user data in the current RunUnit.
The following library routines contain new parameters in this release:
- CBL_LOCATE_FILE
- You can now specify a file name that is a null-terminating string, which has resulted in three new values available for the
user-mode parameter.
For more information see
Related Information at the end of this topic.
Mainframe compatibility
Back to list
- IMS DBCS - Enterprise Server IMS support has been expanded to include applications that use double-byte character sets (DBCS). MFS EATTR=ECGS (full DBCS string without SOSI) is now supported.
- Implement /DIS USER DEQUEUE - the /DEQUEUE USER command is now available to remove messages from the message queue to provide you with greater flexibility when managing IMS systems.
For more information see
Related Information at the end of this topic.
Managed COBOL syntax
Back to list
The following enhancements have been made to the managed COBOL syntax:
- The
TYPE OF type-name[ANY...] syntax enables you to obtain the
System.Type (.NET) or
java.lang.Class (JVM) object for a generic class, interface, or delegate.
- The
self:: or
super:: syntax is no longer required to access inherited data within a subclass.
- The
ATTRIBUTE-ID syntax enables you to define new attribute types, which can be used in various contexts.
For more information see
Related Information at the end of this topic.
Micro Focus FTP utility
Back to list
A new utility,
Micro Focus FTP (MFFTP), provides FTP support for JCL-enabled enterprise servers within
Micro Focus
Enterprise Server. The MFFTP utility provides a support mechanism for batch processes that takes advantage of FTP from JCL on the mainframe.
Support is available for:
- Fixed Block (FB) files
- Variable Block (VB) files
- Generation Data Group (GDG) files
- Configuring third party FTP clients
- Input and output temporary file handling
- Configuring the end-of-line markers
- Configuring the error codes
- Configuring the text messages
For more information see
Related Information at the end of this topic.
Micro Focus Rumba
Back to list
Micro Focus Rumba version 9.4 is now supplied with the
Enterprise Developer 2.3 setup file. The license for
Enterprise Developer will license all components of Rumba.
For more information see
Related Information at the end of this topic.
Micro Focus Unit Testing Framework
Back to list
Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability, but it is not intended for production use and is not supported as such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA level and if it is, then the functionality provided might differ considerably from this technology preview. During the preview, you are encouraged to share your feedback and experiences via the Micro Focus community forum -
http://community.microfocus.com/microfocus/).
The Micro Focus Unit Testing Framework is an xUnit style testing framework, available from the command line, for procedural COBOL applications.
It includes much of the architecture you would expect in an xUnit framework. The test runner is a 32- or 64-bit executable that you run from an
Enterprise Developer
command
prompt. A test fixture or suite is a COBOL program compiled to
.dll that can include the setup, the test case code, and the teardown associated with the test case.
Test results are available in a number of formats. By default, results are displayed to screen and to a
.txt file, but you can use additional parameters on the command line to produce reports in JUnit format.
For more information see
Related Information at the end of this topic.
Microsoft Azure support
Back to list
Enterprise Developer support for
Microsoft Azure has been updated to version 2.6 of the
Microsoft Azure SDK.
Support has been added to the product for making any future versions of the Microsoft Azure SDK available before the next major release of
Enterprise Developer. Micro Focus will deliver support for these only upon customers' requests.
For more information see
Related Information at the end of this topic.
PL/I support
Back to list
This release provides the following enhancements to PL/I support in
Enterprise Developer:
For more information see
Related Information at the end of this topic.
Preprocessors
Back to list
Support has been added in the IDE for enabling and using multiple preprocessors with your projects.
A new page,
Preprocessors, has been added to the project's and the files' properties of native COBOL applications to enable you to choose one or more preprocessors to use when building your application and to specify their order of execution.
New reporting capability is now available for user preprocessors: resp-main code 18 indicates that a buffer contains a data name to be marked as modified by the immediately preceding preprocessed line. The data name may be qualified and resp-more contains the column information for the reference.
For more information see
Related Information at the end of this topic.
Profiler
Back to list
Enterprise Developer now provides support for Profiler for native COBOL applications directly from within the IDE. To produce reports, you need to:
- Enable Profiler in the COBOL property page for a project.
- Compile your application to apply the changes.
- Run your application with Profiler to produce the relevant reports.
For more information see
Related Information at the end of this topic.
REST service interfaces
Back to list
RESTful service interfaces utilizing JSON as the media type in request and response messages are now supported using the Interface Mapping Toolkit. This enables you to extend COBOL applications using modern transport payloads and protocols.
For more information see
Related Information at the end of this topic.
Single file support
Back to list
The recommended way to work with files within
Enterprise Developer is to include them in a project. For situations where you might want to quickly open edit a single file,
Enterprise Developer now provides support for native COBOL files in the IDE when the file is not opened as part of a project. There is limited support for the IDE editing, compiling and debugging features as full support requires a project file.
To enable full IDE support for single files,
Enterprise Developer provides a path for creating projects from them - right-click such files in the editor, and click
Create COBOL Project.
For more information see
Related Information at the end of this topic.
Spooler housekeeping
Back to list
A new spooler housekeeping utility has been introduced (MVSSPLHK). It offers additional archiving functionality compared to the previous spooler housekeeping utility (MVSP0027), and can also be configured to run directly from a JCL job.
For more information see
Related Information at the end of this topic.
Transaction class (TRANCLASS) support
Back to list
Transaction class (TRANCLASS) support is no longer a technology preview feature, and is now a full release feature.
For more information see
Related Information at the end of this topic.
Tunables
Back to list
This release of
Enterprise Developer contains the following updates to tunables:
- default_cancel_mode
- A new parameter, and default, has been introduced for this tunable; see
default_cancel_mode for more information.
- subsystem_cancel_mode
- A new parameter has been introduced for this tunable; see
subsystem_cancel_mode for more information.
For more information see
Related Information at the end of this topic.
Updated run-time system
Back to list
Enterprise Server has been updated to provide an execution environment capable of running applications that were each built using different development products. A consequence of this is that If your application has a main COBOL executable (.exe) that was built with a previous version of
Enterprise Developer, you should ensure that the executable is rebuilt and packaged with the new run-time system.
This does not affect mainframe subsystem projects deployed to
Enterprise Developer. You can rebuild from the IDE or the command line.
Other COBOL subprograms built with previous versions of
Enterprise Developer are not required to be rebuilt.