Significant Changes in Behavior or Usage

Changes in Behavior in This Release

Back to Top

• .NET COBOL projects

• Licensing changes

• LOCKDB replaces Enterprise Server Cluster Global Lock Manager (GLM)

• Locally declared variables
• INITIALIZE <condition-name> produces syntax error

• Default passing mode when passing pointers to a method

• Viewing active spool jobs

• Validation during emulation of ICETOOL's SELECT operator

.NET COBOL projects

The 9.0 release installs several .NET NuGet packages each of which contains the assemblies for a specific Micro Focus functionality. New .NET projects, as well as existing projects you edit or build in 9.0 are linked to a core package, MicroFocus.COBOL.Runtime.Core, that includes the basic functionality for the projects. You need to add any additional packages (such as a specific file handler, COBOL Accept/Display etc.) manually to the projects.

Building existing .NET COBOL projects created prior to 9.0 might result in build errors. You can ensure compatibility by enabling the use of the MicroFocus.COBOL.Runtime metapackage. Alternatively, you need to add any required NuGet packages manually to the older projects.

See Upgrading existing .NET COBOL project files for details.

Licensing changes

• 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.

LOCKDB replaces Enterprise Server Cluster Global Lock Manager (GLM)

The LOCKDB feature replaces the functionality of the Enterprise Server Cluster Global Lock Manager (GLM). See Enterprise Server LOCKDB for more information.

Locally-declared variables

A new Compiler directive, DECLARE, has been introduced to support the introduction of the parameterized sections syntax. The default behavior of this directive (DECLARE"2") is to allocate locally declared directives afresh each time a SECTION is entered. Previously, the default behavior was that locally declared variables were added to local-storage, and therefore would not be allocated afresh each time a parameterized section is performed. To maintain previous behavior, set DECLARE"1"; however, this setting is not supported when compiling to .NET COBOL, or when a program contains a parameterized section.

INITIALIZE <condition-name> produces syntax error

The INITIALIZE <condition-name> statement, where condition-name is true for multiple values, now correctly receives a syntax error in all scenarios. In previous releases, some scenarios would allow compilation (although did not work).

Use of the com.microfocus.cobol.references package in JVM COBOL

This package was previously used to pass all types BY REFERENCE in a JVM COBOL application, including to pass items from a Java program to a JVM COBOL program (although, this is not intended customer use).

In this release, the package has been split into two: com.microfocus.cobol.references and com.microfocus.cobol.user_references. The references package is used to pass, BY REFERENCE, all COBOL items that map to Java primitive types (short, int, etc...). All other types use the user_references package (for String, array of primitive types, etc...). Classes in the user_references package are generated as required by the Compiler, and need to be added to the JVM COBOL application's .jar file.

There are two issues to be aware of:

• If you have created any Java code to use com.microfocus.cobol.references directly, that code needs to be updated to use the user_references package for passing non primitive types.
• A separate package is now used for the Compiler-generated classes, to allow signing of .jar files to work correctly. This is because separately-signed .jar files cannot contain the same package.

  If a customer application has two separately-signed .jar files, and each one requires the use of the Compiler-generated com.microfocus.cobol.user_references classes, a security exception will occur when the .jar files interact with each other. (This was also true when the namespace com.microfocus.cobol.references was used.)

  The solution is to move any structures reliant on com.microfocus.cobol.user_references out of the generated class file directory structure for the application(s), and to package those structures into a separate jar file, which can also be signed, if required - this .jar file would also be need to be added to the CLASSPATH for the overall application.

If your application is affected by this issue, your feedback, via Customer Support (Micro Focus Customer Care website), would be appreciated, to help us refine a solution to these issues.

Default passing mode when passing pointers to a method

In previous releases, if a pointer was passed to a method without explicitly stating the passing mode (BY VALUE or BY REFERENCE), it was assumed to be passed BY REFERENCE. From this release, such items are assumed to be passed BY VALUE, making them consistent with other parameter types.

To pass a pointer BY REFERENCE, you must explicitly state reference in the method signature: for example:

method-id M1(reference ptr as pointer)
...

And ensure that the argument is also passed with the reference keyword; for example:

invoke M1(reference myptr)
...

Validation during emulation of ICETOOL's SELECT operator

A validation check has been implemented to ensure that when making use of the DISCARD operand, the data set opened for output does not have an LRECL greater than the LRECL that ICETOOL is expecting. If it does, the job will fail.

This check may now cause jobs that previously ran successfully to now fail, but this behavior is now consistent with that of the mainframe.

Changes in Behavior in Release 7.0

Back to Top

For an up-to-date list of these changes for release 7.0, see this product's Release Notes available from the Product Documentation section of the Micro Focus Customer Care website.

• Exceeding the maximum record length
• ISO2002 support via the Compiler directive
• Initializing variable-length groups when ODOSLIDE is in effect
• .NET COBOL interoperating with other languages

Exceeding the maximum record length

The maximum record length supported by the File Handler is 62KB. If you create records that exceed this limit, a COBCH0649 error is generated on compilation. You can continue to use programs that utilise these large records, but you may experience adverse results in your file handling operations.

ISO2002 support via the Compiler directive

The ISO2002 directive now supports an option to provide different levels of ISO2002 features. ISO2002"1" provides the level of features supported in Server Express and Net Express, and ISO2002"2" provides those features, plus additional ones added since Visual COBOL. If you have used the ISO2002 directive in Server Express/Net Express, and are migrating to Enterprise Developer, use ISO2002"1" if your applications are affected by the change in behaviors provided with ISO2002"2".

Initializing variable-length groups when ODOSLIDE is in effect

The target of an INITIALIZE statement cannot be a variable-length group if the ODOSLIDE Compiler directive is set. This now results in a severe syntax error, whereas in previous releases this was incorrectly allowed to compile and produced unexpected run-time results.

.NET COBOL interoperating with other languages

.NET COBOL programs compiled with REENTRANT"2" now produce instance methods, whereas previously, compilation of these programs produced static methods. If your non-COBOL code relies on these methods being static, you will have to refactor your code to handle this, or recompile the .NET COBOL code with the ILSTATIC directive.

Changes in Behavior in Release 6.0

Back to Top

For an up-to-date list of these changes for release 6.0, see this product's Release Notes available from the Product Documentation section of the Micro Focus Customer Care website.

• Early warning of compatibility issues with current operating systems
• Call prototyping in library routines
• Database Access - OpenESQL
• Handling of Anonymous Root Field in JSON
• National data items in .NET COBOL code
• VALUE clause not permitted to follow items that use the OCCURS DEPENDING ON clause when ODOSLIDE in effect
• iFileshare

Early warning of compatibility issues with current operating systems

In order to better support modern operating systems, we are aligning closely with their operability guidelines. We now detect previously-undefined behavior when interacting with OS level functions.

Error RTS096 alerts you to any calls to the operating system's fork() API, in a process that has directly or indirectly called COBOL functionality, in your code.

The error gives you an early diagnosis of a situation which, if left unchecked on modern operating systems, could lead to deadlocks, crashes or other failures at run time. These problems would often occur intermittently and be very challenging to track down.

See the KB article https://community.microfocus.com/t5/Visual-COBOL-Knowledge-Base/fork-rts64-Error-96-encountered-in-child-process/ta-p/1771191 for more details.

Call prototyping in library routines

The copybooks cbltypes.cpy and cblproto.cpy, provided by this system for call prototyping in library routines, include features of the latest syntax, specifically the CONSTANT keyword. If these files are used in conjunction with the MF directive, it should be set to the current level, 21; otherwise, you should remove the directive, or do not use these copybooks.

Database Access - OpenESQL

Just like other DBMS SQL COBOL precompilers, OpenESQL now follows embedded SQL standards and disallows the use of group host variables in WHERE <column> = :hostvar clauses. In the past, this was not flagged at compile-time, and would lead to unpredictable results when executed.

Handling of anonymous root field in JSON

For JSON (RESTful) service interfaces, the IMTK no longer forces the outermost (root) structure of a JSON message body to always be a JSON object, but now also supports a root JSON array or primitive. Though the root is obligatorily nameless in the JSON message, in the Interface Mapper the anonymous root must now be defined in the operation's interface fields as the top-level body field. Consequently, since there cannot be more than one input top-level body interface field nor more than one output top-level body interface field in an operation, all interface fields that appear in the body of a message must now be children of the top-level body field. Any non-conforming pre-6.0 JSON service interface is still supported as-is, but conformance would be required upon saving in the Interface Mapper.

National data items in .NET COBOL code

.NET COBOL code that uses IS NUMERIC tests on NATIONAL or NATIONAL NUMERIC data items, or uses NATIONAL NUMERIC data items in programs compiled with the CHECKNUM Compiler directive must be recompiled in this release. Compiled code from earlier products that uses such constructs will generate a MissingMethodException error when run under this release.

VALUE clause not permitted to follow items that use the OCCURS DEPENDING ON clause when ODOSLIDE in effect

If your Working Storage contains a data item with the OCCURS DEPENDING ON phrase, and ODOSLIDE is in effect, any subsequent data items at the same or higher level must not contain a VALUE clause. If they do, an error (COBCH1962) is now generated.

If you cannot remove the VALUE clauses from your source code or remove ODOSLIDE, contact Customer Care.

iFileshare

iFileshare is no longer a strategic component of this product, and is no longer being enhanced. We recommend that if you currently rely on it, you migrate to a stand-alone FileShare server instead; see Using Fileshare with Enterprise Server.

Changes in Behavior in Release 5.0

Back to Top

For an up-to-date list of these changes for release 5.0, see this product's Release Notes available from the Product Documentation section of the Micro Focus Customer Care website.

• Communications Facility syntax no longer supported

• Monitoring Resource Manager Connections

• Compiling

• Configuring SSL Security

• JCL - Copying Empty Data Sets
• JES Housekeeping
• JES Security
• JES Catalog Updates

• File Handling

• Calling coblongjmp() within an error procedure, exit procedure or signal handler

Communications Facility syntax no longer supported

The Communications Facility (also referred to as the COMMS SECTION or COMMUNICATION SECTION) has long since been deprecated. Certain syntax relating to this was still accepted (but ignored) by the Compiler. That syntax is no longer permitted, and if encountered, the Compiler will now generate an error (COBCH1895 Communication Facility not supported); you must remove the section from your sources before recompiling.

Monitoring Resource Manager Connections

The processing associated with the ES_XA_RECONNECT environment variable has changed.

This processing has been replaced by a new CICS transaction (CRCN) monitoring and testing for disconnection and attempting reconnection at regular intervals.

ES_XA_RECONNECT is now used to specify this interval (in seconds) between connection tests carried out by the transaction.

If you currently have ES_XA_RECONNECT=TRUE, set it to an acceptable time for your installation (e.g. 5 seconds, 30 seconds, 60 seconds, etc…)

The ES_XA_???_NB_RETRIES variable is also no longer required with the new method of monitoring connections.

One or more RMs can be excluded from CRCN processing using environment variable ES_XA_EXCLUDE_MONITORING, i.e., ES_XA_EXCLUDE_MONITORING=RM1;RM2;RM3 excludes three resource managers, named RM1, RM2, and RM3.

See Monitoring Resource Managers for more information.

Compiling

Inclusion of line numbering information in run-time error messages provides useful diagnostic assistance during abnormal program termination. This is already the default behavior on Unix and Linux platforms, and is now the default compiler behavior when using the command line on Windows platforms too.

For debug builds it is normal to specify the ANIM compiler directive, and for release builds it is normal to leave the ANIM directive absent from build scripts. In these circumstances, you might now notice the presence of .idy files where you had not previously. The production of these .idy files does not affect the behavior or performance of your application other than generation of line number information. IDY files are not required to execute your application and you should not distribute them unless you have a specific requirement to debug your application.

Configuring SSL Security

The default behavior for TLS certificate Common Name (CN) matching has changed for Enterprise Developer 5.0. It now requires a strict match on the CN value or any Subject Alternate Name (SAN). For example, 127.0.0.1 and localhost are no longer implicitly equivalent, nor are hostname and its IP address or fully-qualified domain name (FQDN) variants.

When starting a region from the Enterprise Server Administration Web interface, a resolved IP address is used for the casstart -m parameter value. A resolved IP address is also used even if a hostname is specified on a command line startup. To change this behavior and use a resolved hostname value (as determined by the machine TCP configuration, for example, hosts file entries.) set the environment variable MFDS_DNS_RESOLVE=Y. To use an unresolved string literal hostname, for example, a value explicitly passed in via the casstart -m command line parameter, set MFDS_DNS_RESOLVE=N.

JCL - Copying Empty Data Sets

As of Patch Update 5 of release 5.0, the incorrect changing of a VSAM data set file status from pristine to used when REPROing an empty data set has been corrected. When REPROing records into a data set, if the source data set is empty, the destination data set is not opened. The affect of this is that when OPENing INPUT a VSAM data set that was the destination of a REPRO of an empty data set, the file status is 35, rather than 00.

JES Housekeeping

When using the MVSSPLHK housekeeping process, the Spool Housekeeping history file (INDEXO) can now support 7-digit job numbering.

When you enable 7-digit job numbering, any existing data sets (specified by INDEXO) must be converted to a new format. A sample .jcl file (CONVERT.JCL) and a conversion utility (MFHKHCOV) are both supplied with this version of the product. Edit the .jcl file to reflect the name of your data sets and run it to convert the file. Once converted, the newly formatted data set supports both 5- and 7-digit job numbering. If you only use 5-digit job numbering, you do not need to run the conversion.

See the MVSSPLHK Spool Housekeeping Process section in the Help for more information.

JES Security

JCL security checks have been extended to verify that a user who submits a job has, at least, READ access to partitioned data sets whose members are used as catalogued procedures or INCLUDE files in the JCL file. Similarly, the user who runs the job must have, at least, READ access to JOBLIB and STEPLIB partitioned data sets mentioned in the job.

JES Catalog Updates

When using the public catalog API, MVSCATPB, changes to or deletion of a data set that is currently allocated to the job step are not permitted after the data set has been opened. If attempted, MVSCATPB will return a retcode of 78-RET-VALIDATE-ERROR (20) and a reason code of 78-dataset-in-use (19).

Also, when updating the DSORG of a data set using the REPL function, a check now verifies that the change is appropriate. If it is not, a return code of 78-RET-VALIDATE-ERROR (20) and a reason code of 78-MISMATCHED-DSORG (50) is produced.

File Handling

Applications which make calls directly to EXTFH or EXTSM, passing the FCD (File Control Description) now need to initialize the FCD correctly. This means that any unused or reserved areas need to be initialized with binary zeros or you could receive an RTS114 error, for example when calling EXTSM. See File Control Description (FCD).

Calling coblongjmp() within an error procedure, exit procedure or signal handler

Calling coblongjmp() within an error procedure, exit procedure or signal handler now generates a fatal Run-Time System error message: COBRT131 coblongjmp() can not return from current context (Fatal).

This scenario was previously documented as a restriction, and is now enforced, to prevent subsequent issues. The resolution to such an error is to refactor the code to remove the coblongjmp() call from any error procedures, exit procedures, or signal handlers.

Changes in Behavior in Release 4.0

Back to Top

For an up-to-date list of these changes for release 4.0, see this product's Release Notes available from the Product Documentation section of the Micro Focus Customer Care website.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Compiling
• Enterprise Server security
• Executables may require relinking or recompiling
• HCO for SQL Server (HCOSS)
• IMTK runtime configuration
• Application Server JCA Support for Enterprise Server
• Test Coverage results

Compiling

The Compiler now produces an E level message - COBCH1888 Typedef is defined differently in another external program - if different external programs have conflicting definitions of the same typedef name. To restore the previous behavior, where the earlier definition was ignored, use the directive HIDEMESSAGE"1888".

Enterprise Server security

Web access to the Enterprise Server Console Log and Communications Server Log is now restricted when the enterprise server region is secured using external security. Users will be required to provide a valid username and password in order to view either log file.

Web access to the logs can be controlled using the standard ACL definitions under the new Communications Server resource class, with resources Enterprise Server Console Log and Communications Server Log. If these resources exist, users require 'read' access to be allowed to view the logs. If the resources do not exist, the default behavior is to allow 'read' access on entry of a valid username and password.

An example of the new resource class and resource definitions can be found in the es_default_ldap_msuser.ldf file, which is located in the bin sub-directory of your product directory.

Executables may require relinking or recompiling

Version 4.0 of your product is dependent on a later version of the Microsoft C run-time system than earlier Micro Focus products. This means that COBOL executables (.exe) built with an earlier version of your product might not be compatible with version 4.0 run-time products. If the behavior of your application changes with version 4.0, we strongly recommend that you relink the main executable with version 4.0. This will ensure that the COBOL run-time system fully handles any run-time error conditions that might occur.

A new executable that is fully compatible with version 4.0 can be produced without recompiling the application, as long as the original object code is available and it is relinked with version 4.0.

To allow your executables to benefit from the product's latest programming and performance enhancements, we recommend a full recompilation of your source code.

HCO for SQL Server (HCOSS)

When using the DIALECT=MAINFRAME setting, the OpenESQL STRICTPARSE SQL compiler directive option is now turned on by default for ODBC (DBMAN=ODBC). This ensures strict compliance with z/OS DB2 syntax.

If your applications require the OpenESQL preprocessor to behave as it did in an earlier release, compile using NOSTRICTPARSE.

IMTK runtime configuration

Due to changes made to the Configure Runtime Environment dialog box in this release, after you upgrade your system, you must reenter all previously set values on this dialog box before running a service.

Application Server JCA Support for Enterprise Server

With this release, all CICS-related Java artifacts have been delivered using a new directory structure under the javaee-ccl directory of your Enterprise Developer installation directory. The javaee-ccl directory structure mimics the structure of the javaee directory. For example, mfccl.jar is no longer located in the bin subdirectory, but can be found in the javaee-ccl\common directory.

Test Coverage results

Schema changes that affect the test coverage results generated from the tcutil utility mean that if you propagate the results to a third-party application (for example, an XSLT processor), and rely on the <copyFileCoverage> element, you need to alter your transformations to focus on <sourceFileCoverage> instead. The element was renamed to more appropriately reflect its contents, as tcutil now gives global coverage for all source files (not just copybooks).

Changes in Behavior in Release 3.0

Back to Top

For an up-to-date list of these changes for release 3.0, see this product's Release Notes available from the Product Documentation section of the Micro Focus Customer Care website.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• JES-enabled enterprise servers
• Compatibility AddPack
• Compiler Directives
• JES security - the PHYSFILE resource class
• Managed COBOL
• OpenESQL
• Reserved words

JES-enabled enterprise servers

Back to the list

In this release, the infrastructure of the JES spool repository has been upgraded in order to improve performance. For each JES-enabled region, before you can submit any jobs to JES, you must run the spool conversion utility; any newly created regions will automatically be configured to use the new spool files.

The conversion process converts the information in the existing spool files to a set of new files required under the new system. There should be no loss of data in moving to the new system.

As well as significantly improved times when running housekeeping tasks, these changes have the additional benefits:

• The new infrastructure is more disk-efficient, reducing the space required by the spool files by up to 75% in some cases.
• Internal indexing is greatly improved, resulting in quicker generation of messages and SYSOUT records during processing.
• Improved navigation of spool queues: job status Complete replaces the Output, Out Hold, and Printed statuses, and completed jobs with any combination of sysout files can be displayed in a single list.
• Increased range of job numbers, from 5 digits to 6 or 7 digits; see details on the MF_MVSJOB environment variable.
  Important: After converting to the new JES spool infrastructure, we recommend that you do not employ the increased range of job numbers until you have thoroughly tested the new infrastructure. Reverting back to the previous JES spool files is possible, but requires that you remove all job entries using more than 5 digits, for which there is no easy process.

Compatibility AddPack for Visual COBOL

Back to the list

Compatibility AddPack for Visual COBOL is now deprecated and will not be available with release 3.0 and later.

The Dialog System GUI and run-time components and Dialog System Character Mode (on Windows and UNIX) which were part of the AddPack are now installed as part of Enterprise Developer for Visual Studio. The run-time components are installed as part of Enterprise Server. These are only included for backward compatibility and Micro Focus does not recommend that you use them for new development.

The other components which were part of the AddPack, the Character-Based Data File Editor, CSBIND and Screens, will be available upon request from Micro Focus Customer Care.

Compiler Directives

The default for the FASTINIT directive has changed: FASTINIT is now the default when setting the MF dialect. The directive remains not set by default (that is, NOFASTINIT) for other dialects.

JES security - the PHYSFILE resource class

Back to the list

• The PHYSFILE security setting is now checked when a dataset entry is inserted into the catalog, or when a dynamic PDS member is created. The check is made for all cataloged files, including spool files (for example, JESYSMSG and SYSOUT files). You should review any existing PHYSFILE rules to ensure they are correct, otherwise access may be denied where it was previously allowed; see Resource Classes for JES Security for more information.

  If the PHYSFILE class is created in the LDAP repository it is necessary to add appropriate rules to allow users that submit jobs to have 'write' access to the job log location, so that job submissions are successful.

  Note: If the files provided with release 3.0 have been used to populate the LDAP repository, the PHYSFILE resource class is created with no rules.

Managed COBOL

Back to the list

References to types within an assembly other than mscorlib need to be explicitly referenced. You can achieve this by using the ILREF Compiler directive.

Previously, in certain circumstances, the Compiler would allow access to types within the System.dll assembly without the need for an ILREF"System" directive.

OpenESQL

Back to the list

The new OpenESQL OPTIMIZECURSORS SQL compiler directive option is turned on by default for both ADO.NET (DBMAN=ADO) and ODBC (DBMAN=ODBC). For ADO.NET, this reduces cursor memory consumption thereby providing optimal performance. This also ensures that, for ODBC, embedded SQL cursors that use WITH HOLD and FOR UPDATE clauses have the same data integrity across all databases.

If your applications require the OpenESQL preprocessor to use the behavior provided in an earlier release, compile them using OPTIMIZECURSORS=NO.

Reserved words

Back to the list

• There have been a number of new reserved words added to the COBOL language; these are all in effect under MFLEVEL"19", which is the default level when running under the MF dialect. Any of the following words are now not allowed under default conditions, and you will need to remove/rename them, or specifically configure your environment to allow them:
  • ALLOCATE
  • FREE
  • JSON
  • END-JSON

  See Reserved Words Table at the end of this topic for more information.

Changes in Behavior in Release 2.3 Update 2

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Compiler
• Enterprise Server
• JCL Support
• Micro Focus Directory Server
• Monitoring and Management
• PL/I Support
• Run-Time System

Compiler

Back to the list

• The ILPINVOKE directive is now allowed only in an initial $SET. This is in line with similar directives like ILREF and ILTARGET. Previously, the ILPINVOKE directive was allowed in other positions in the source code which could cause issues with insufficient memory.

  2860347 (1104422)

• In previous product releases, the scoping rules for nested programs (as defined in ANS85 COBOL), were not enforced in managed COBOL (.NET and JVM). This meant that, in cases where program A contained programs B1 and B2, and programs B1 and B2 contained C1 and C2, respectively, it was possible to call program C2 from C1, for example. The lack of scoping rules also meant that it was not possible for B1 and B2 both to contain a program with the same name.

  This product release enforces the correct ANS85 scoping rules for nested programs, including COMMON programs, and makes it possible to have multiple programs with the same name at different levels of the nesting hierarchy. In this way, the behavior in managed COBOL is now compatible with the behavior of native COBOL programs.

• Replacing a partial token no longer causes the second part of the token to appear on a new line. This could happen if the new text was larger than the text being replaced.

  2869185 (1105763)

• There is no longer a problem opening an RM/COBOL indexed file when the program has a RECORD CONTAINS n CHARACTERS clause and there are record descriptions with lengths less than n. This situation previously caused a 39 error on the OPEN (other than OPEN OUTPUT) because there was a mismatch in the minimum record length.

Enterprise Server

Back to the list

• Previously, it was possible to install groups that should not have been installed. If a group name, as defined in the Startup List, did not exist in the list of Groups then the next Group in the alphabetical order would be loaded instead. Now, if a Group is not defined in the list of Groups, a warning that the Group could not be loaded is issued.

  2869848 (619107)

Micro Focus Directory Server

Back to the list

• The "-n" option for the mfds command now supports hostnames as the network addresses in addition to IPv4 addresses.

  2816871 (1099564)

Monitoring and Management

Back to the list

• Messages that are written to the console log by applications that perform "display upon console" now contain a standard message ID (CASMG0001I).

  2854207 (1103659)

JCL Support

Back to the list

• A printer exit can now evaluate the spool copybook field lk-dest-source-is to find the source of the value in the spool DEST-NODE and DEST-USERID fields, to determine if it is from a SYSOUT 'DEST=' value or from a /*ROUTE PRINT value.

  2852302 (1103304)

PL/I Support

Back to the list

• A problem with PUT STRING when compiled with the -bigendian option in effect has been fixed. Note that when upgrading your application from a version of Enterprise Developer earlier than 2.3 Update 2, you must recompile any program using PUT STRING.

  2857374 (1104039)

• Previously, if using the -incafter option of the macro preprocessor to infuse a %INCLUDE with macro logic, you were required to schedule a second macro pass to preprocess the contents of the %INCLUDE. This is no longer necessary and the macro logic will be preprocessed on the first macro pass as if it was part of the original source.
• Previously, if writing output to a CTLASA (PRINT) file with the optional LINE(x) parameter having a value of x that was less than the current line, PL/I did not generate ASA Control characters to end of page and emit the output on the first line of the new page. This no longer occurs.

  2871278 (1106114)

• Previously, if SIGPIPE was triggered when a PL/I program was in the callstack, then PL/I error handling got control and processed the ERROR. This no longer occurs. Users who rely upon catching SIGPIPE can re-enable it by adding a call to cobpostsighandler() to their code to turn it back on.

  2859980 (1104399)

Run-Time System

Back to the list

• The command_line_linkage tunable has been deprecated; equivalent functionality can be achieved by using the COMMAND-LINE-LINKAGE Compiler directive instead.

  2838118 (1101539)

  Attention: As of release 4.0, this tunable is no longer deprecated.

Changes in Behavior in Release 2.3 Update 1

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Communications Server
• Data Tools
• Dialog System
• Editor Writing Assistance
• Enterprise Server
• IBM Language Environment for OS/390 & VM Support
• JCL Support
• Run-Time System
• SQL: OpenESQL
• SQL Option for DB2

Communications Server

Back to the list

• A new option, [Operation] synchronous=yes (or 1, or Yes, or y or Y) is now supported in the Fileshare listener configuration.

Data Tools

Back to the list

• When filtering a data file, if there is no valid temporary directory set, you are prompted to set one using the option in the Preferences dialog box.
• The editor no longer allows you to open a file if the file size (without header size) is not a multiple of the record size on disk; an error is produced instead.
• The level numbers displayed in a record layout correspond to the levels used in the .idy file that was used when the structure file was created.

Dialog System

Back to the list

• Versions of the Micro Focus Compatibility AddPack released with version 2.3 of Enterprise Developer or Visual COBOL 2.3 or with earlier versions supported the use of the "MFOLECL_NO_THREAD_INIT" environment variable. Using this variable, you could disable the default OLE Class Library COM threading initialization. This helped avoid issues that could manifest as hangs and crashes, especially on Microsoft's Windows 8.x or 10 and with applications that are a hybrid between Dialog System, OLE class library and .NET elements - see http://community.microfocus.com/microfocus/cobol/visual_cobol/w/knowledge_base/20715.exception-occurs-when-native-dialog-system-program-calls-managed-winform.aspx.

  In the version of the Micro Focus Compatibility AddPack released with Enterprise Developer 2.3.1 or Visual COBOL 2.3.1, this environment variable is now enabled by default and no longer needs to be set exclusively. To restore the previous behavior, use a new environment variable, MFOLECL_THREAD_INIT, and set it to Yes.

  2848875 (1102920)

Editor Writing Assistance

Back to the list

• IntelliSense suggestions are no longer offered if you start typing numbers and automatic triggering of suggestions is enabled.
• Pressing TAB in the Visual Studio editor now always inserts the highlighted item in the IntelliSense list of suggestions.

Enterprise Server

Back to the list

• In situations where the crossregion option of the shareoptions parameter is either 1 or 2, both a CICS and a JCL job could have the same file open for IO. This has been fixed. In addition, the '-oo' (and the synonymous '-o ') option of the casfile command has been deprecated. If '-oo' is used, you will now receive a return code 4 (warning). Instead of '-oo', you need to use the '-ooi' option (open immediate). If -oo is used with a region configured for VSAM shareoption use, the '-ooi' option is now forced.

  2839272 (1101672)

• When using an external security manager to secure a region, the EXEC CICS START TRANSID API now works as expected and honors the USERID option. Previously, the started transaction would run under the authority of the user that executed the EXEC CICS START API.

  2835112 (1101201)

IBM Language Environment for OS/390 & VM Support

Back to the list

• When calling SETENV, SYSOUT(?) can be specified. This designates the file as a spool file but will not update its CLASS.

  2841220 (1101955)

JCL Support

Back to the list

• The return code from a JCL printer exit will now be checked. If it is non-zero, the dataset that was sent to the printer exit will be moved to the OUT-HOLD queue rather than to the PRINTED queue. To release the dataset, click "Release" in the ESMAC view - this will also present the dataset again to the printer exit.

  2834206 (1101079)

• Under Enterprise Server and Enterprise Server for .NET, flushing an active job previously resulted in all associated spool records for the job being deleted, but left the job running. A subsequent attempt to kill the running job using casout/seeout failed due to the job spool record no longer existing. This change causes the flush request to fail if the job is active. You must kill the active job first before attempting to flush it.
• The catalog search facility has been enhanced to provide a quicker return when using wildcards in the dataset name selection.

  2698700 (1094266)

• REXX can now be executed in VSE via IKJEFT01 and IRXJCL using in-stream data.

  2831984 (1100883)

Run-Time System

Back to the list

• The Audit Manager contains a new TIMEOUT option. When a client sends an audit event using the ‘CBL_AUDIT_EVENT’ API, the event gets placed in the next available slot in a shared memory block. If shared memory is full (i.e. no slots are available), the event is re-tried until a slot becomes available.

  If no Audit Manager is running, no events are removed from shared memory, and no slots will ever become available. Therefore, use the new TIMEOUT option so that a client will only retry sending until the TIMEOUT duration is reached; after which, it will stop sending audit events. If Audit Manager is recycled, events will start to be sent again.

  To set the TIMEOUT for all Audit Manager clients, specify the following line in the Audit Manager configuration file:

  mfaudit.timeout = n

  Where n is the timeout value in milliseconds.

  To set the TIMEOUT for an individual Audit Manager client, use the ‘CBL_AUDIT_CONFIG_PROPERTY_SET’ API. It takes an integer property-value, which should be the timeout value in milliseconds.

  If TIMEOUT is set using both methods, the client property TIMEOUT takes precedence, unless this property is set to zero; in such cases, the TIMEOUT in the configuration file is used. If you use the ‘CBL_AUDIT_CONFIG_PROPERTY_GET’ API on the ‘TIMEOUT’ property, it only returns the TIMEOUT value for the client property; it does not return the value set in the configuration file.

  2838689 (1101685)

• Several changes have been made to the implementation of IS DBCS, IS KANJI and IS JAPANESE class condition tests:
  • IS [NOT] DBCS

    When CHARSET"EBCDIC" is in effect, the IS DBCS test returns true when each character in the string is deemed to be a valid DBCS character. A valid character has its first byte in the range 0x41 through 0xFE, and the second byte in the range 0x41 through 0xFE, or the character is an EBCDIC space (0x4040). When CHARSET"ASCII" is in effect, the DBCS test uses an OS call to determine if the string contains only valid double-byte character, and returns true if valid.

  • IS [NOT] KANJI

    When CHARSET"EBCDIC" is in effect, the IS KANJI test returns true when each character in the string is deemed to be a valid Kanji character. A valid character has its first byte in the range 0x41 through 0x7F, and the second byte in the range 0x41 through 0xFE, or the character is an EBCDIC space (0x4040). When CHARSET"ASCII" is in effect, the IS KANJI test uses an OS call to determine if the string contains only valid Kanji character, and returns true if valid.

  • IS [NOT] JAPANESE

    When CHARSET"EBCDIC" is in effect, the IS JAPANESE test is not supported, and will generate a COBCH1806 Feature not supported in selected charset message on compilation.

    When CHARSET"ASCII" is in effect, the IS JAPANESE test returns true when the string contains only double-byte Japanese characters or single-byte Japanese Katakana characters, and returns true if valid. When NSYMBOL"NATIONAL" is in effect, these class tests are not supported, and will generate a COBCH0303 Operand has wrong data-type message on compilation.

  2812895 (1098401)

SQL: OpenESQL

Back to the list

• The DB2 CONCAT function and operator now convert to SQL Server using the HCOSS-supplied dbo.CONCAT for character, numeric and datetime data. If you are using BINARY or VARBINARY data, you must apply the HCOSS-supplied dbo.CONCAT_BINARY function. HCOSS applications deployed with earlier versions of Enterprise Developer are affected, if they use string or binary concatenation. The mainframe dialect DB2 || operator and CONCAT function now call a new SQL Server scalar function dbo.CONCAT(). All existing programs with dialect=mainframe that use DB2 concatenation syntax should be recompiled. All existing SQL Server databases that are accessed by these programs must have dbo.CONCAT installed. To create the new function in your application’s SQL Server database, you can either:
  • Run a DSN bind against the customer database. Or:
  • Execute the %ALLUSERSPROFILE%\Micro Focus\Enterprise Developer\hcoss\InstallDigitsFunction.sql script.

  This is a one-time only change to the database.

  2843818 (1102248)

SQL Option for DB2

Back to the list

• Spurious errors were sometimes returned while querying using an ALIAS.

  2830383 (1100609)

Changes in Behavior in Release 2.3

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

Where present, the numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Assembler Support
• Building
• Converting Additional Directives to Projects' Properties
• CAS Security
• CAS XA Switch modules
• Compiler
• Data Tools
• Discontinued Support for cwgui
• File Handling
• IDE
• J2EE Connector
• JCL Support
• Mainframe Access
• MF Server Administrator (GUI)
• PL/I Support
• SQL - HCO for SQL Server
• Updated Run-Time System

Assembler Support

Back to the list

• Previously, the Assembler run-time error SOC4 (Invalid 370 address abend) was mapped to the COBOL run-time error 200 (Internal logic error) which was misleading. It is now mapped to the COBOL run-time error 205 (COBRT205 Invalid mainframe pointer value (Fatal)). Note that, in most cases, you receive an Assembler SOC4 abend if the calling COBOL program was compiled without the AMODE(24) or the AMODE(31) Compiler directives.

  2806239 (1097738)

Building

Back to the list

• Enterprise Developer now supports Visual Studio parallel builds for COBOL projects. Parallel builds enable you to build multiple projects faster on multi-CPU machines.

  If, after upgrading to this version of Enterprise Developer, you start receiving unexpected build errors when compiling an existing multi-project solution, this may be a result of enabling support for parallel project builds. These are a couple of examples of issues that might be causing these errors:

  • Using file references to project outputs in the same solution. You need to use project-to-project references instead.

    Use Project > Project Dependencies to manage the project dependencies and build order within your solution.

  • A customized build process such as one that is using pre- or post- build events.

  If resolving any of these issues does not help resolve the build errors, consider disabling the parallel build support - click Tools > Options > Projects and Solutions > Build and Run and set maximum number of parallel project builds to 1.

Converting Additional Directives to projects' properties

Back to the list

• Starting with this release, an Update Project Properties dialog box might start to appear when you are opening existing COBOL solutions. The dialog box recommends converting some of the directives specified in Additional directives to project's properties. This is to address an issue where you might try to set file properties that differ from the project directives and the directives specified in Additional directives that have a property equivalent take precedence over the file properties. As a result of this you might receive unexpected build issues when building your applications.

  This dialog box helps eliminate the issue by converting the directives specified in Additional directives to project properties.

  If you do not want the IDE to perform this check, click Tools > Options > Micro Focus > General and uncheck Check Additional Directives for project properties.

CAS Security

Back to the list

• The Enterprise Server External Security Facility now includes MLDAP ESM Module 2.0, with a new algorithm for identifying the best-matching resource-access rule and ACE for resource-access security checks. This algorithm is faster and matches most customers' expectations. The new algorithm also provides an optional "username substitution" feature. It can be enabled by setting "rule substitutions" to "yes" in the [Operation] section in the Security Manager configuration text area. When this is enabled, the string "${user}" in a resource-rule name will be replaced with the name of the user that makes the request. For example, a DATASET rule named "USERS.${user}.**" would apply to datasets with the requesting user's name as the second qualifier. In rare cases, customers with complex, ambiguous resource-access security rules might see experience changes in behavior as a result of the new algorithm. The old algorithm is still supported and can be enabled by setting "version 1 authentication" to "yes" in the [Operation] section of the Security Manager configuration.

  2807531 (1097783)

CAS XA Switch modules

Back to the list

• The XA switch modules now support dynamic registration.

  2682101 (1092325)

• The XA switch modules now support batch-only operations when multiple XA Resource Managers have been defined.

  2664675 (1091082)

• In Enterprise Developer 2.2 update 2, Micro Focus identified undefined run-time behavior when the following combination of directives was specified: SIGN"EBCDIC", CHARSET"ASCII", and one of the following: HOST-NUMMOVE, HOST-NUMCOMPARE or SIGN-FIXUP. Previously (Enterprise Developer 2.2 update 1 and earlier), if this combination was specified, the SIGN”EBCDIC” directive should have been ignored, to avoid a mixture of ASCII and EBCDIC characters; however, SIGN”EBCDIC” was still being honored, resulting in undefined run-time behavior. Therefore, this combination of directives is now invalid for Enterprise Developer 2.2 update 2 or later, and if specified, will be rejected at compile time.

  2786397 (1095265)

Compiler

Back to the list

• For native COBOL, the size limit of the Data Division now stands at 2GB -1.

  2796076 (1096384)

• COBDATA has no effect on compilation. The output of the Compiler is the same location regardless of whether COBDATA is set.

  Previously, it was not possible to specify sign(EBCDIC) with sign-fixup, host-num-move or with host-num-compare. This combination is now supported in native COBOL but remains invalid for managed COBOL code. This is applicable to version 2.2 U2 HotFix 10 onwards.

  2824577 (1100823)

Data Tools

Back to the list

• DFCONV now returns the correct return-code; previously, it would always return 0.

Discontinued support for cwgui

Back to the list

• The cwgui debugger is no longer available. You can now use the cw_java debugger which provides a richer graphical debugging experience.

File Handling

Back to the list

• Custom file handlers (using DYNREDIR) are now called for each part of a concatenated file.

  2795077 (1096322)

IDE

Back to the list

• The default warning level for new COBOL projects in Enterprise Developer for Visual Studio is now "Include recoverable errors (Level E)". This also includes "Severe errors only (Level S)" and unrecoverable (Level U) errors. Micro Focus recommends you set the warning level on the COBOL page in a project's properties to "Include warnings (Level W)" where appropriate to help avoid potential coding problems.

J2EE Connector

Back to the list

• This release provides a new command-line argument to Java, mf.ssl.algorithm, which can be set to an appropriate algorithm.

  2799213 (1096684)

JCL Support

Back to the list

• When allocating a dataset to a step using MVSCTLBP, the values returned for the dataset attributes are those defined in the catalog. If these are unset in the catalog, then the values defined in the MVSCTLBP call are returned.

  2816179 (1098882)

• The program attributes for the SSTM job have been changed to default to a mainframe dialect, AMODE 31 program. These attributes will be used when constructing the MVS Control Blocks for the job, which means that the pointers to the sub-block areas will be in mainframe format rather than native format.

  2815695 (1098825)

• Any OUTPUT statement information passed to the printer exit now includes the correct class of that statement.

  2814249 (1098636)

• In ESMAC, when deleting the Spool, the physical spool files and the entries in casspool.dat are deleted.

  2812899 (1098412)

• New functionality has been added to the printer exit interface that enables you to delete the printer spool file after a file has been printed. Set (ws)-prn-file-disp, which is defined in cascbprn.cpy, to 1 to delete the spool file after printing. Additionally, the environment variable ES_JESYSMSG_OUTPUT=Y now correctly routes spool files to the Output queue. Previously, ESMAC still showed the job on the HELD display, even when there were no spool files HELD.

  2812899 (1099966)

• A new environment variable has been introduced - ES_JESYSMSG_RESTRICTED. JESYSMSG spool files are normally routed to HELD. This can be overridden by setting the environment variable ES_JESYSMSG_OUTPUT=Y, which causes all JESYSMSG spool files to be routed to OUTPUT. If ES_JESYSMSG_OUTPUT=Y is set but you require specific classes to be held, set the environment variable ES_JESYSMSG_RESTRICTED to a string containing the classes to be HELD.

  2812878 (1098417)

• The IEBDG PICTURE value length must match the length specified. The value can now contain any characters including quotes as on the mainframe.

  2794881 (1096221)

• Changes to the IDCAMS ALTER processing prohibit applying MGMTCLASS changes to GDGs and to a VSAM element other than a Cluster. Shareoption settings in a SMS DATACLASS are now applied to the VSAM elements correctly.

  2789939 (1095803)

Mainframe Access

Back to the list

Mainframe Access is now built using the IBM XL/C compiler rather than the SAS/C compiler that was used previously. This change requires you to update your production JCL procedures with reference to the supplied samples MFA, MFAS, and MFAAS. In each JCL procedure, change the STEPLIB DD statement and add a new one, CEEOPTS.

The web administration feature is no longer available in Enterprise Developer.

To use the Mainframe Access support for Endevor you must be using Endevor R14 or later. CA stabilized the Endevor API at R14, so if you upgrade from R14 to a later version you will not need to update the support module that Mainframe Access uses.

MF Server Administrator (GUI)

Back to the list

• Passwords that entered through either the MFDS or the ESMAC interface now use the same encoding.

  2792382 (1096011)

PL/I Support

Back to the list

• For BASED variables declared using the form BASED (ADDR(x)), storage checking is now performed on the base reference “x”. This behavior requires the compiler option –nolaxbased. See the Open-PLI User guide for more information on the options –[no]laxbased and –[no]laxdefined.

  2819663 (1099293)

• The behavior of the –zp1 option has been reverted to that of before Enterprise Developer 2.2 Update 1, with an additional correction relating to Char Varying data items. For a full description of the –zp1 option, refer to the Open-PLI User’s Guide in your product help. If you are installing Enterprise Developer 2.2 U1 HF5 as an upgrade to Enterprise Developer 2.2 U1, you must rebuild any applications that are compiled using the –zp1 option after the upgrade.

  2789213 (1095636)

• Previously, when using any of the complier options -mvs, -dli, -ims, or -cics, the BINARY attribute was incorrectly applied if the FIXED attribute is specified without BINARY or DECIMAL. The default attribute DECIMAL is now applied.
• The BIGENDIAN attribute, when explicitly applied to a structure, is now propagated to its CHAR VARYING and WIDECHAR VARYING members.
• Declarations using DEFINED storage are now checked for compatible types between the DEFINED variable and its base variable. This behavior requires the compiler option –nolaxdefined. See the Open-PLI User guide for more information on the options –[no]laxbased and –[no]laxdefined.
• The PL/I Macro preprocessor has been enhanced to support the use of the ANSWER statement from within a PL/I Macro.

  2698537 (1094243)

• The macro preprocessor has been enhanced to support arrays of CHAR and FIXED variables. New macro builtin functions have been implemented (HBOUND, LBOUND, DIMENSION).

  2696129 (1094011)

SQL: HCO for SQL Server

Back to the list

• The return type for the HCOSS DB2 CHAR() function has changed from CHAR(255) to VARCHAR(255).

  2804069 (1097253)

Updated Run-Time System

Back to the list

• Enterprise Server now provides 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 version of Enterprise Developer prior to version 2.3, 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 Server. 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.

Changes in Behavior in Release 2.2 Update 2

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

CICS Support

Back to the list

• In CRTE mode, the transactions are now run using the correct userid if the user has signed on after running CRTE.

  2663890 (1091979)

Compiler

Back to the list

• When using the HOSTRW directive with the mainframe dialect, Report Writer will now produce the full range of ASA control characters and will emulate mainframe print files.

  2697615 (1094527)

• Fixed Binary (p<=7) is now an 8-bit, signed, 2's complement binary integer by default.

Documentation

Back to the list

• The default setting for the MFALLOC_PCFILE environment variable has changed; the default is now set to Y, which means that when cataloguing a file that has a DCB attribute of DSORG=PS, a physical file is created for it if one does not exist. Previously, the default was set to N, which meant that a file was not created.

  2697571 (1094370)

Enterprise Server

Back to the list

• The Enterprise Server External Security Facility now includes MLDAP ESM Module 2.0, with a new algorithm for identifying the best-matching resource-access rule and ACE for resource-access security checks. This algorithm is faster and matches most customers' expectations.

  The new algorithm also provides an optional "username substitution" feature. It can be enabled by setting "rule substitutions" to "yes" in the [Operation] section in the Security Manager configuration text area. When this is enabled, the string "${user}" in a resource-rule name will be replaced with the name of the user that makes the request. For example, a DATASET rule named "USERS.${user}.**" would apply to datasets with the requesting user's name as the second qualifier. In rare cases, customers with complex, ambiguous resource-access security rules might see experience changes in behavior as a result of the new algorithm. The old algorithm is still supported and can be enabled by setting "version 1 authentication" to "yes" in the [Operation] section of the Security Manager configuration.

  2807531 (1097783)

• Starting with this release, IMSCONFG.DAT is no longer used for configuring enterprise servers. Instead, you need to use environment variables to control the following fields:

  Field	Environment Variable
  LANG=PL/I PCB address lists	ES_IMS_PLI_INDIRECT_PCBADDR=D|Y|N Where: D Dynamic (default) use indirect PCB address list when PSB language is PL/I and main program is PL/I. Y Always use indirect PCB address list if PSB language is PL/I. N Never use indirect PCB address list.
  IBM Platform	ES_IMS_IBMPLATFORM=M|D Where: M MVS (default) D DOSVS Required by some DOS/VS customers.
  Secondary Index Sparse exit language	ES_IMS_SPARSE_EXIT_LANG=C|A Where: C COBOL A Assembler Not set (default) Sparse exits disabled

Enterprise Server for .NET

Back to the list

• The data file location list in the region startup file now supports both on-disk and database folders – for example, c:/project/bin/debug and sql://(dbinst)/VSAM/?folder=FOLDER1;type=folder.

  When searching for a file, CICS will check in all of the provided locations in the order specified. Files that are accessed using fileshare or the catalog are not affected by these changes and continue to work like they did before. You can configure how CICS locates the underlying data files using a new set of properties. When using the CICS Resource File Editor to explore the ResourceDefinitions.config file, FCTs now include a File Location Overrides section with the following properties:

  • Filename – specify a filename or a filename with an extension (for example, ACCTFIL.DAT) that CICS will search for instead of using the FCT name.
  • File Extension –specify a file extension. The FCT name must be used as the file name.
  • Folder – specify where CICS should search for files.
  • If this is set to the absolute path to a folder on your machine or to a database folder, CICS only searches for files in that folder and does not use the data file locations.
  • If this is set to a relative path (such as "/subfolder1/subfolder2/"), CICS applies that relative path to each of the data file locations in which it searches for the file.
  Note: Previously, the Folder property was called Path and had to be set to the full absolute path to the data file. These three properties are compatible with the native Enterprise Server and can be enabled in any combination.

  Previously, in order for CICS to locate a file in the database, you had to set the Format property to RDBMS and the Path property of an FCT to the name of the datastore. This is no longer required.

  Instead, you need to add the datastore folder that contains the file either to the data file locations or to the Folder property in the File Location Overrides section in the FCT properties. You can still use the RDBMS format value as a hint to configure CICS to create the file (for example, using CFCR) in the database and not on disk.

  If you install this release, you must modify any FCTs that were using the old Path property. For example:

  If you previously had:

  FCT ( Name=fct1 Path="c:\folder\file1.dat" )

  This must be converted to: FCT ( Name=fct1 FileName="file1.dat" )

  And the data file location, c:\folder\, must be added to the region startup file.

  2780059 (1094576)

File Handling

Back to the list

• The ES_IMS_TLOG_FLUSH environment variable is now deprecated. To control TLOG flushing, use the following environment variable: ES_IMS_DB_TLOG_WRITETHRU=0|1

  0

  Forces the flushing of TLOG buffers to disk on COMMIT only (default)

  1

  Forces the flushing of TLOG buffers to disk on all database I/O

  To control database flushing, use the following environment variable: ES_IMS_DB_COMMIT_FLUSH=0|1

  0

  Forces the flushing of database buffers to disk on CLOSE only (default)

  1

  Forces the flushing of database buffers to disk on COMMIT only

  Depending on the number of database updates, the frequency of COMMITs, and other concurrent computer activities, use of these environment variables could cause significant performance degradation.

  2784949 (1095190)

• The use of the environment setting MFJ_INPUTDS_ERROR=N has been extended so that an input file for a JCL step is now considered as optional and you no longer receive an error when the file is missing.

  2784622 (1095971)

Host Compatibility Option for SQL Server (HCOSS)

Back to the list

The mainframe dialect DB2 CHAR() function now calls a new SQL Server scalar function dbo.MFCHAR(). To create the new function in your application’s SQL Server database, you can either:

• Run a DSN bind against the customer database.

  Or:

• Execute the %ALLUSERSPROFILE%\Micro Focus\Enterprise Developer\hcoss\InstallDigitsFunction.sql script.

  Additionally:

• The return type for the HCOSS DB2 CHAR() function has changed from CHAR(255) to VARCHAR(255).

2804069 (1097253)

J2EE Connector

Back to the list

• The listSystem.properties file in package com.ibm.ctg.client was missing documentation for some sections.

IMS Support

Back to the list

• The NODCX mfims dbdgen directive has been added to enable you to compile DBD source without executing data capture exit routines contained in the DBD source. Previously, data capture exit routines contained in the DBD source but that were not found during compilation were ignored. The new default behavior is to process all data capture exit routines unless NODCX has been specified.

  2579600 (1084675)

• All existing IMS Global Physical Terminal edit routines (DFSGPIX0) in use must be recompiled with charset EBCDIC instead of charset ASCII.

  (606142)

JCL Support

Back to the list

• Following the detection of an unrecoverable file status error on the casspool file, a message is displayed on the console and an ACCEPT statement is issued. This stops processing, allowing you to fix the underlying file problem, before continuing the job.

  2651654 (1090287)

• You can now activate support for the VSAM Shareoption for batch jobs and for CICS files that use a catalog entry. For more details, see your product help.

  2660651 (1091290)

PL/I Support

Back to the list

• Important: If you are installing this release as an upgrade to Enterprise Developer 2.2 Update 1, after the upgrade you must rebuild any applications that are compiled using the –zp1 option.

  The behavior of the –zp1 option has been reverted to that of versions of Enterprise Developer earlier than 2.2 Update 1, with an additional correction relating to Char Varying data items. For a full description of the –zp1 option, refer to the Open PL/I User’s Guide in the product help

  This fix restores the behavior in Enterprise Developer versions earlier than 2.2 where, when compiling with –zp1, all parameters are treated as unaligned. (In Enterprise Developer 2.2 Update 1, the behavior when compiling with –zp1 was to not treat parameters as if unaligned).

  When using the –zp1 compiler option, all Character Varying data items are now treated as if unaligned. In previous versions of Open PL/I, for Character Varying data items, the –zp1 unaligned requirement was applied only to structure members and parameters.

  To illustrate the change, consider the following example:

  zptest: proc options(main); 
   
     dcl 1 st1, 
       2 c char, 
       2 x(4) char(7) var init ('a', 'xx', 'yyy', 'zzzz'); 
   
     dcl y(4) char(7) var init ('a', 'xx', 'yyy', 'zzzz'); 
   
     dcl sub entry ((4) char(7) var); 
   
     call sub (x); 
   
     call sub (y); 
   
  end; 
   
  sub: proc (z); 
   
     dcl z(4) char(7) var; 
   
     dcl i fixed bin(31); 
   
    do i = 1 to hbound(z); 
        z(i)  = 'x'; 
    end; 
   
  end; 

  Where:

  • For x and z, each char (7) var item is 7 plus 2 bytes which equals 9 and then multiplied by 4 equals 36.
  • If y were aligned on half-word by default, each array element is half-word aligned and each equals 10 bytes (9 + 1 pad byte), and the total size equals 40 bytes.
  • At call sub (x), the calling argument and parameter are matched.
  • At the call sub (y), the y element size (10 bytes) is mismatched against the parameter z element size (9 bytes) due to –zp1. This is incorrect and causes unexpected program behavior.

  Due to this correction of treating all Char Varying data items as if unaligned when using –zp1, the size of CHAR VARYING arrays now differs from previous versions of Open-PL/I. For example:

     dcl X(4) char(7) var; 
   
     Put skip list (size(X))  /* size is 36 bytes vs. 40 bytes in previous versions of Open-PL1 */ 

  2789213 (1095636)

• Previously, the SRC list in the debugger only included the source filename without the path to the file. If a source file did not exist in the current directory, the debugger could not find it using the filename as it always expects a fully qualified filename. The SRC list now contains the fully qualified file name which includes the path. Also, when changing the SRC or ENV values the source is updated correctly.

  2783734 (1094988)

Changes in Behavior in Release 2.2 Update 1

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• COBSQL
• Compiler
• File Handler
• JCL Support
• PL/I Support

COBSQL

Back to the list

• COBSQL now displays appropriate COBOL syntax errors after encountering EXEC SQL statement errors.

  2673619 (1093197)

Compiler

Back to the list

• In member reference in managed COBOL syntax, you may now only use parentheses when referencing methods. You can no longer specify parentheses when referencing fields or properties, as this will produce a syntax error. For example:

  set intLength to testString::Length()

  must change to:

  set intLength to testString::Length

File Handling

Back to the list

• Random and Dynamic access of an empty VSAM file would open successfully. This has been changed to return a 3/5 file status to bring it into line with the mainframe.

  2692826 (1093604)

JCL Support

Back to the list

• The final disposition processing of temporary datasets has been corrected to be in line with the mainframe processing, with a default value of PASS unless DELETE has been specified in the DD card. Previously, the default value was DELETE.

  2671175 (1091627)

• When running batch programs, receiving an "Out of Space" error requires operator intervention to continue processing.

  2642115 (1089055)

• You can now use MGMTCLAS to provide an EXPIRE AFTER number of days. This is used to calculate an expiry date for datasets allocated using the MGMTCLAS parameter.

  2664639 (1090992)

• MFLEX*.DAT files were not being moved with spool files. Spool housekeeping now deletes LEX files when it deletes JESYSMSG. Also, to identify any remaining orphan LEX files, the MF_SPOOL_HK_LEX_SCAN environment variable sets spool housekeeping to scan the data directory for LEX files older than the max retain period.

  2659555 (1090759)

• Spool housekeeping has been rewritten to provide a number of new features. These will be described in the product documentation.

  (592452)

• The state of VSAM virgin files is now being correctly processed.

  2686149 (1093587)

• A REPRO COUNT of zero is now processed as zero records to be included in the REPRO operation.

  2665006 (1091034)

PL/I Support

Back to the list

• On Intel platforms, the -bitsltr Compiler option can be used to store bit strings left-to-right within each byte. This is similar to Big Endian bit ordering on Intel platforms. The Intel default is to store bit strings right-to-left within each byte similar to the Intel hardware bit ordering.

  2675860 (1092098)

• The libraries libmf.so, libespli.so and libespliz.so are no longer delivered. This is transparent if linking PL/I objects using mfplx or ldpli, and no changes are needed to your build process.

  However, if linking PL/I objects using either the UNIX ld command or the Enterprise Developer cob command, you must include the libraries libmfpli.so when linking stand-alone Open PL/I objects (executed outside of Enterprise Server), or libmfpliz.so when linking PL/I objects executed under the control of Enterprise Server.

  To do this, use the option -lmfpli for stand-alone Open PL/I objects or -lmfpliz, respectively, for PL/I executed under Enterprise Server. These options replace the –lmf option.

• Open PL/I applications must be recompiled and re-linked in order to use them with this release.

• The debugger now stops before an ON UNIT triggers. This lets you perform debugging on the ON UNIT itself. You can configure the ON UNITS the debugger stops on.

  2674783 (1092319)

• Writing to SYSPRINT when running outside of Enterprise Server now drives output directly to the terminal and does not buffer the I/O.

  2477031 (1076203)

Changes in Behavior in Release 2.2

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Assembler Support
• Common Communications Interface
• Compiler
• File Handling
• IDE
• Interface Mapping Toolkit
• IMS Support
• JCL Support
• MF Directory Server
• MF Server Administrator (GUI)
• Micro Focus Batch Scheduler Integration
• PL/I Support
• Request Handler
• Samples Browser

Assembler Support

Back to the list

• A "." (dot) specification is no longer ignored in the SYSIN environment variable or in the mf370ctl.cfg file when used to specify an output directory, and indicates the current directory. This is a change in behavior from Mainframe Express, where the "." (dot) character in the SYSIN environment variable or in the mf370ctl.cfg file is still ignored and assembler output files are placed in the directory specified by the SYSIN environment variable.
• Assembler Build Output will now be sent to the location specified in the COBOL output path project setting. Previously, all Assembler build output went to the project directory.

Common Communications Interface

Back to the list

• A new option, use_global_namespace, is available for the CCI.INI file in the Windows %SystemRoot% folder. If use_global_namespace is set, all the ccishared memory objects are created in a system-wide address space, and the applications hosted by different users, including system services, can communicate. To use this facility, edit the CCI.INI file and ensure use_global_namespace is set to "yes". [ccismem-base] # Allow interaction between users on a # single system. Using this option reduces security as # all users will have access to the same name space. use_global_namespace=yes If the value of this option is anything other than "yes", or if the option is missing, no change is made to the existing behavior.

  2195519 (1062800)

Compiler

Back to the list

• The use of ILSMARTLINKAGE in sub-programs is now working correctly. In previous versions, if it was specified in a sub-program, a dynamic call of that program from another program could cause execution failure.

  2608825 (1087435)

• In managed code, the statement DISPLAY UPON SYSERR now behaves as expected. Previously, it was behaving the same as DISPLAY UPON CONSOLE.

  2589053 (1085576)

• When the PROPERTY keyword is used on a numeric edited field, the SET method now works correctly when the program specifies DECIMAL POINT IS COMMA.

  2588508 (1085560)

• The default for the NSYMBOL directive under DIALECT(ENTCOBOL) has been changed to NSYMBOL(NATIONAL) to emulate the equivalent IBM default.

  2657471 (1090355)

• To improve RM/COBOL and ACUCOBOL compatibility, the SIGN clause at a group level is no longer applied to non-DISPLAY usage signed numeric data items within the group, just as it is not applied to unsigned numeric data items and non-numeric data items within the group.

  2549904 (1082171)

• Previously, even though no code was generated, the Compiler allowed the ON EXCEPTION and NOT ON EXCEPTION phrases in the DISPLAY statement in formats that do not allow these phrases. As a result, if the DISPLAY statement was in the ON EXCEPTION phrase of another statement, the NOT ON EXCEPTION phrase would bind incorrectly with the DISPLAY statement instead of with the intended containing statement - for example, ACCEPT or CALL.

File Handling

Back to the list

• When used with MFJSSTRICTSORT=ON, MFJSORT now errors (return code 16) if the input RECFM is different to a SORTOUT RECFM. It also errors if the input RECFM is different to an OUTFIL RECFM when FTOV or VTOF/CONVERT has not been specified.

  2643384 (1088993)

IDE

Back to the list

• Performance when loading and building COBOL projects that consist of a large number of files has been improved.

  2657121 (1090316)

• When building a project outside of the IDE, adding a new file to a project no longer results in a full rebuild of the project.

  2617003 (1089623)

• You can now change the display format of values on individual rows in the Watch window using modifiers after the names of variables and expressions. To do this, click a row, press F2, and type a modifier after the name of the variable or the expression as follows - type VariableName,h or VariableName,x to always display the variable or the expression in hexadecimal format; type VariableName,d to always display numeric variables in decimal format and strings - as text.

  2614182 (1087959)

• When you perform a search in the IDE for copybooks that your programs depend upon, the COPYEXT directive you set from the Additional directives field on the COBOL tab in your project's properties is now used in preference to the list of copybook extensions specified in Tools > Options > Text Editor > Micro Focus COBOL > Advanced, and in Copybook extensions. This change does not affect the project build and background parsing that already use COPYEXT.

  2612053 (1087773)

• Attempting to restart an enterprise server failed if the process took longer than fifteen seconds.

  2607051 (1087259)

• When you debug native code and query a data item which contains null bytes, the value displayed in the Watch window is no longer truncated at the first null byte.

  2604749 (1087235)

• A new setting, "Define DEBUG constant", is now available on the COBOL page in the project properties of managed projects for the Debug configuration. You can select it to add "constant"DEBUG(1)"" to the build directives.

  2600567 (1086629)

• The Output window now displays a notification when the compilation of the IMS files has been successful.

  2600137 (1086667)

• A problem with the value of "Link with objs" setting being duplicated after you reload the COBOL Link properties page has been resolved.

  2595408 (1086091)

• IntelliSense now displays data names longer than 32 characters correctly.

  2594901 (1086053)

• Previously, when you upgraded COBOL projects with signed assemblies from Visual Studio 2003 format to Visual Studio 2010 format, the signed assembly property was lost.

  2585458 (1085258)

• There is an improvement in the performance of the cursor in the text editor when working with larger files and projects.

  2585450 (1085255)

• Using linked files in projects has been improved as follows:
  • Folders that only contain linked files no longer disappear from the project when you reload it.
  • The location of linked files is preserved in the project structure when you reload the project.
  • Moving a linked file within a project no longer moves the actual file on the disk but only moves the link inside the project structure.
  • It is no longer possible to copy a linked file into the same project where, previously, this created a copy of the actual file on the disk.

  2574102 (1084208)

• When you convert Net Express projects that compile to .int or .gnt files to Enterprise Developer for Visual Studio, the application environment variables are now imported successfully.

  2569777 (1083953)

• It is now possible to convert Net Express projects that do not contain any COBOL source files to Visual Studio projects.

  2568638 (1083900)

• You can now set environment variables used by the native COBOL Run-Time system during initialization from the project properties - click Environment on the Application tab.

  2539447 (1081251)

• Pressing Enter to create a new line now preserves the indent in the COBOL editor in Smart edit mode.

  2496411 (1077769)

• The "Edit IMS Database" command was disabled for DBD files in your project if the ACB file was not in the project directory. You can now optionally define a location for the ACB files different than the project directory by setting the ES_ACBLIB environment variable.

  2496391 (1077864)

• Pressing End inside the writing area of the COBOL editor now positions the cursor on the first non-blank character, if columns 12-72 contain any text. If the line is blank, the cursor is positioned on column 73.

  2496351 (1077767)

• The COBOL editor now supports a "Smart edit mode" (see Tools > Options > Text Editor > Micro Focus COBOL > Margins) which is enabled by default. In Smart edit mode, when you press ENTER in the code (A/B) area the comments move to the next line and stay in the right-hand area.

  2496350 (1077768)

• You now receive a suitable error message when you try to use "Start Without Debugging" with Mainframe Subsystem Application projects.

  2495298 (1078343)

• You can now use Solution folders to group projects in your solution.

  2259310 (1065760)

• If, when you start debugging, the debug target does not exist you now receive an error message that correctly states the missing filename.
• Any leading or trailing spaces you added to the name specified in the "Output name" field on the Application tab in the properties of a native project are now ignored.
• Class view no longer contains outdated information from previous background syntax checking after classes have been renamed.
• Class view no longer contains outdated information from previous background syntax checking when the files defining types have been removed.
• A problem with navigating to member definitions from the Class View has been resolved.
• A problem with navigating to member definitions from the Class View has been resolved.
• An issue where canceling some of the dialogs in Tools > Options resulted in the changes being saved anyway, or the pages not reverting when next loaded, has been resolved.
• You can now start and stop servers from the Server Explorer when using the local machine's IP address or DNS name.
• It is now possible to debug a project that has its "Compile for debugging" setting enabled in the project properties for the Release configuration.
• Selecting a project in Class View now triggers background syntax checking, if it has not been performed for that project yet.
• If you have .NET Framework v. 4.5 installed, creating a COBOL Web application with Visual Studio 2010 Shell was failing with a Signal 114 error and was causing the IDE to crash. This issue has been resolved for the IDE. To work around the issue when you compile COBOL Web Applications from the command line, you need to manually set the environment variable VisualStudioVersion to 10.0 before compiling.
• Using the tab character in comments no longer causes issues with the colorization of the code.
• The Visual Studio IDE no longer crashes if you try to close it while directives scan is in progress.
• Adding files to a project when directives scan is disabled was taking a long time to complete.
• Friend assemblies (as identified by the InternalsVisibleToAttribute) are now correctly handled during syntax checking, and types are correctly found within friend assemblies when they are present.
• An issue with adding new platforms or configurations to a project or solution when the project contains pre- or post-build events has been resolved.
• A problem with navigating to member definitions from the Class View, when the definitions occurred within copybooks used within partial classes, has been resolved.
• A problem where trying to navigate to the source of an item from the Class View positioned you on the wrong line, has been resolved.
• An issue where the Implements smart tag was present for interfaces that were fully implemented (when some of the methods from that interface were implemented explicitly; and in addition to another interface which was not fully implemented) has been fixed.
• An issue where method signatures were rendered incorrectly if the member had a 78 level item in its local storage has been resolved.

Interface Mapping Toolkit

Back to the list

• For program-based Service Interfaces, if the program-id name in the COBOL source is in lowercase and is not surrounded by quotes, its corresponding entry-point name is now forced to uppercase when used in a Service Interface Operation. Previously, the case was preserved. As a result of this change, existing Service Interfaces will become invalidated if you refresh their program's annotations because of the new spelling of the entry-point name. To avoid this, you need to surround the program-id name in the COBOL source with quotes before you refresh the annotations.

IMS Support

Back to the list

• The DBDCPY, MFSCPY, and PSBCPY environment variables are no longer required and have been deprecated. Use the IMSCPY environment variable to specify copybook locations.

JCL Support

Back to the list

• The default for previous releases was to create a catalog entry with no physical file until data was actually written to the catalog. Now, a PC file is allocated for non-VSAM files by default. You can emulate the previous behavior if you set the environment variable MFALLOC_PCFILE to N.

• Empty values for the USER or NOTIFY parameters on the JCL JOB card no longer cause an error when parsing the JCL.

  2646770 (1089380)

• The disposition processing of PASSed datasets has been revised to be consistent with mainframe processing. Particularly, received datasets are removed at the end-of-step processing, unless they are to be passed on to another step in the job. Any passed datasets that were not received at the end of the job may be removed if they conform to the mainframe conditions for this.

  2610362 (1087601)

• The value for the JCL DD UNIT=device parameter is now stored in the system catalog entry for the dataset.

  2619050 (1089095)

MF Directory Server

Back to the list

• The mfds command line option for exporting registered Enterprise Server definitions to an XML file now supports the "*" option. This exports all registered servers rather than a specified server. Multiple server definitions are now exported into the target directory and saved into a file with the default name ALLSERVERS.xml. The import option now also supports the import of multiple server definitions from a single XML file.

  2641890 (1088838)

• mdump now supports a new option, -e, to help you query the Security Manager configuration details. The possible values of the option are: "1" - shows security configuration that applies to any returned enterprise servers; "2" - shows security configuration for MFDS and the default Enterprise Server security configuration. This requires MFDS version 1.15.00 or higher; "3" - returns the properties of all configured external Security Managers.

  2487164 (1081693)

MF Server Administrator (GUI)

Back to the list

• When adding a user to an external security manager, you can now include a password expiry time in the Advanced Configuration section of the Add New User wizard in Enterprise Server Administration. The field value is specified using generalized time format (YYYYMMDDHHMMSS.0Z), and can be used by the MLDAP ESM for calculating whether a user's password has expired and requires updating. This value may only be specified using this page when adding a user. You need to use an external directory services configuration tool to edit it.

  2562118 (1083203)

Micro Focus Batch Scheduler Integration

Back to the list

• casout now correctly sets return-code to the job status for the sysout retrieval when the file is less than 65K. Also, MFBSI now considers return codes of 0, 7 or 8 to be successful for JESYSMSG retrieval where, previously, it only considered 0 as successful.

  2655482 (1090444)

PL/I Support

Back to the list

• Open PL/I applications must be recompiled and re-linked in order to use them with this release.

  2675860 (1092098)

• If using the -cics, -ims, or -mvs options when compiling on a little endian platform, the possibility for errors existed. Starting with this release, using the -cics, -ims, or -mvs options automatically uses -bigendian, thereby eliminating the possibility for these errors. Evaluate any applications that were built with a prior release to determine any impact on any data files being used, or where programs compiled with the -mvs option pass data to sub-programs compiled without it. The -bigendian option can be suppressed by adding the -native option after the -cics, -ims, or -mvs options.

• CodeWatch no longer attempts to use an incorrect directory when starting. Also, CodeWatch is now the default debugger when no other debugger is specified, and is the only debugger available when using -optexec plitest.

  2655906 (1090193)

• Support for the evaluation of X, NX, Z, A, and E constants nas been added to CodeWatch.

• A problem with possible truncation or trailing zeroes within PICTURE assignments has been fixed. As the fix depends on changes to both the Compiler and the run-time, you must perform a complete rebuild of all your source code (recompile and relink) in order to apply it.

  2662261 (1090768)

• Previously, when taking a PLIDUMP, if the .PDB file needed for a PLIDUMP was not in the same directory as the .DLL and the .STB files, and they were not in the first CAS_BATCH_PATH subdirectory, then the PLIDUMP was not successfully generated and an S0C4 abend could occur.

  2615412 (1090483)

• The Open PL/I debugger no longer loses its place and behaves erraticly when debugging code containing the same PL/I macro multiple times within the same source routine, even if the -nodebuginfo and -pp options are not specified.

  2612530 (1087809)

Request Handler

Back to the list

• A problem that caused BIS to create log files in a directory named C:\ProgramData\AcuCorp\BIS\LogFiles was fixed. BIS no longer creates log files unless specified and the BIS logging service is now disabled by default. To enable it, you need to use the following global environment variable: BIS_LOG=[ OFF | ON | <directory> ] Where the values are:
  • OFF - disables logging (the same as if BIS_LOG is not specified or is left blank)
  • ON - enables logging and directs the log files into the default location, which must not be read-only.
  • <directory> - enables logging and directs the log files into the specified directory. The user must ensure that the BIS request handler has write rights for this directory. The directory must be an absolute path or network path. If the specified directory does not exist, BIS will attempt to create it. The containing directory must exist.

  The BIS_LOG variable is only examined when the BIS application pool is started or recycled. After setting or changing BIS_LOG, IIS must be restarted in order for the variable to take effect.

Samples Browser

Back to the list

• If you have installed the version of this product for both Visual Studio 2010 and Visual Studio 2012, the Samples Browser now provides links for you to open the samples in either one of them.

Changes in Behavior in Release 2.1 Update 1

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Documentation
• Enterprise Server
• IDE
• JCL Support
• OpenESQL
• PL/I Support

Documentation

Back to the list

• To ensure no loss of functionality when accessing Vision and RM/COBOL data files, you should use the appropriate IDXFORMAT Compiler directive setting or file handling option, and not use the CALLFH(ACUFH) Compiler directive. See 'Configuring Access to Vision Files' and 'Configuring Access to RM/COBOL Data Files' for more information.

Enterprise Server

Back to the list

• HSF includes the following enhancements:
  • A new record type (JCLF) for JCL files.
  • A Job class has been added to the JCL JOBSTART records.
  • A condition code has been added to the JCL STEP records.
  • Statistics for up to 5 Transient Data Queues per CICS record has been added (same as for exisiting TSQ stats). The HSF files will now be created with the following header: #HSFVer=02 Type,PID,Task,Date,Time,Tran/Job,User/DDName/CC,LU/Step,Prog/DSName,Latent/ReadCount,Resp/WriteCount,API/RewriteCount,SQL/DeleteCount,IMS,DSType,DSAccessType,File1,Count1,Time1,File2,Count2,Time2,File3,Count3,Time3,File4,Count4,Time4,File5,Count5,Time5,TS1,Count1,Time1,TS2,Count2,Time2,TS3,Count3,Time3,TS4,Count4,Time4,TS5,Count5,Time5,TD1,Count1,Time1,TD2,Count2,Time2,TD3,Count3,Time3,TD4,Count4,Time4,TD5,Count5,Time5

  2552658 (1082755)

IDE

Back to the list

• There is no longer a crash when adding a reference path to a managed COBOL project.

  2604844 (1087055)

• When you debug native code and query a data item which contains null bytes, the value displayed in the Watch window is no longer truncated at the first null byte.

  2604749 (1087235)

• An issue where you could not open copybooks from the context menu in the COBOL editor when the filename was specified with its extension and without surrounding quotes has been resolved.

  2604709 (1087031)

• A problem with the value of "Link with objs" setting being duplicated after you reload the COBOL Link properties page has been resolved.

  2595408 (1086091)

• Previously, when you upgraded COBOL projects with signed assemblies from Visual Studio 2003 format to Visual COBOL 2010 format, the signed assembly property was lost.

  2585458 (1085258)

• There is an improvement in the performance of the cursor in the text editor when working with larger files and projects.

  2585450 (1085255)

• The Error List window now shows the details about the "Illegal command line" error when it is a result of setting invalid SQL directives.

  2585426 (1085251)

• Adding files to a project when directives scan is disabled was taking a long time to complete.

  (593378)

JCL Support

Back to the list

• Input files are no longer optional so you can receive errors if you catalog a file without creating the physical file. To help avoid failures of JES job steps because of a missing input file, you can use one or both of the following environment variables: 1) MFALLOC_PCFILE=Y - results in the creation of a catalog file if DSORG=PS is set in the DCB parameters. 2) MFJ_INPUTDS_ERROR=N - results in IEBDG, IEBGENER and IEBCOMPR utilities to treat missing input files as though they were present but empty files.

  (594968)

OpenESQL

Back to the list

• SQLWARN4 flag was not being set when more than one row was returned for a singleton SELECT statement. The OpenESQL run-time now correctly sets SQLWARN flags when a singleton SELECT statement returns multiple rows.

  2593798 (1085945)

PL/I Support

Back to the list

• When running the macro preprocessor as part of an Open PL/I compile, if there are missing %INCLUDE files, we now flag them as SEVERE errors which are visible in the Visual Studio Output Tab even with the minimal level of MSBuild information enabled. We terminate after the macro phase, allowing the customer to correct the situation before continuing.

  2577072 (1084419)

Changes in Behavior in Release 2.1

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• CICS Support
• Compiler
• IDE
• Run-Time System
• Vision File System

CICS Support

Back to the list

• If external security is configured (MLDAP) and the default ESMAC user is not allowed to login, the region does not startup.

  2550800 (1082337)

Compiler

Back to the list

• The use of extended ACCEPT or DISPLAY statements in Windows applications (ilsubsystem"2") now produces error COBCH1634: Extended ACCEPT/DISPLAY not allowed with a Windows GUI executable (ILSUBSYSTEM"2"). Remove the syntax or change the output type of your application to 'Console Application'.

  2575702 (1084365)

IDE

Back to the list

• A problem with the item templates in the Add New Items dialog box not available for PL/I projects has been resolved.

  2581187 (1084876)

• There is now a build summary report for projects that compile to multiple output files.

  2578006 (1084506)

• Previously, Visual Studio used to always rebuild the entire project after you changed the project properties or added files when there were build error. This has been changed so that during subsequent builds Visual Studio only rebuilds the files that are out-of-date.

  2576400 (1084393)

• A new setting has been added to the COBOL tab in the project properties, "Generate listing option", which produces an .lst file in a Listing subfolder in the project directory. The "Generate directives file" setting now generates the directive file in the project output directory.

  2494484 (1077662)

• Command line arguments are now passed to the program when started via the 'Start without Debugging' option in the Visual Studio IDE.
• Previously, if you started debugging using CBL_DEUGBREAK and there was a COBOL source file open in the editor, when you stopped debugging its dictionary file (.idy) was not being released. This resulted in any subsequent builds and rebuilds failing. This problem has been resolved.
• The native COBOL projects in Visual Studio have been enhanced so that you can now build them to multiple executables - each COBOL program in the project producing a separate executable.
• You no longer receive an error message when adding an event handler to an object in a COBOL WPF project if the .xaml code behind file includes a class that does not have methods in it.
• The IDE no longer ignores certain Run-Time System errors from the Compiler which previously caused the build to fail without an explanation.
• Compile extensionless COBOL files with the IDE no longer fails.
• Using the UI to add COBOL switches or environment variables to a COBOL Web Application (right-click the configuration file in Solution Explorer and select Edit) no longer causes a configuration error when you run the application.

  2558133 (1082871)

Run-Time System

Back to the list

• When running a full-screen application inside a terminal emulator on Linux, the actual size of the terminal is read at startup and reread when the terminal is resized. This behavior is also supported on AIX, HP/UX, and Solaris. The Micro Focus vt220 terminfo entry now correctly describes a 24-line display. A vt220-25 terminfo entry is included for compatibility with the previous behavior.

  2579335 (1084817)

Vision File System

Back to the list

• When you configure your application to return RM/COBOL file status codes, by setting COBFSTATCONV=rmstat, the codes returned are ANSI'85 codes.

  2553438 (1082469)

Changes in Behavior in Release 2.0

Back to Top

This section describes significant changes in behavior or usage. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.

The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).

• Compiler
• HCO for DB2 LUW
• File Handling
• IDE
• OpenESQL
• Run-Time System

Compiler

Back to the list

• An attempt to serialize a class containing COBOL data such as PIC X or group items could lead to a serialization exception.

  2555177 (1082730)

• Dependent assemblies (ones that are required by other assemblies) that fail to load now issue a COBCH1581 warning "Could not load dependent assembly AssemblyName". Previously, they generated a COBCH0942 error. If an assembly generates both COBCH0942 and COBCH1581 errors, the error report lists only the COBCH0942 error.

  2507380 (1078845)

• The scope of the ILUSING Compiler directive when used in a $set command has changed. The scope of the directive is now limited only to the source file it is set in, and not globally. This new behavior may mean that your source files no longer compile. To resolve this, add the required ILUSING statements to the required individual source files, or add the ILUSING directive on the command line. Alternatively, use the IDE to achieve the required behavior by using the Namespaces tab.

HCO for DB2 LUW

Back to the list

• The DB2 ECM has been updated to resolve run-time errors returned when compiling against mainframe databases in 64-bit mode.

  2549058 (1082441)

File Handling

Back to the list

• When reading a file cataloged as DISP=SHR the file handler now buffers the read for better performance.

  2518330 (1079491)

• Using SKIP=nL in the SECTIONS section of SORT will now cause the following behavior: 1)Under a mainframe sort, (n/3 rounded up) blank lines (when n>0) will be skipped and the appropriate carriage control character will be placed in column 1 of each blank line. 2) For sequential file organizations, the same behavior will occur but no carriage-control characters will be printed. 3) For line sequential files, n blank lines will be skipped.

  2525670 (1080092)

IDE

Back to the list

• Using File > New > Solution From Net Express Project to convert a Net Express project to a Visual COBOL solution on a machine with a language locale other than English or Japanese produced an empty solution.

  2548551 (1082073)

• The COBOL tab in the project properties of a new WPF Application sometimes was not showing any settings.

  2535705 (1080950)

• In some menus and dialogs in the IDE copybooks were referred to as copy files. They are now consistently referred to as copybooks.
• The project properties have been enhanced. The SQL directives are no longer shown in Build Settings on the COBOL page where they sometimes appeared as out-of-date. The SQL directives now appear only on the SQL page.
• Adding a watch on an item of the form buffer(1:size) caused the IDE to hang when "size" was not initialized.
• ActiveX components in the Windows Forms of a managed project could cause the programs to crash at run-time. Previously, to work around this problem, you had to check the ActiveX references in the project and set their CopyLocal reference property to True. This is now done automatically when the references are added.

  2536071 (1080978)

• Adding an existing Windows Form to another project as a linked file did not function correctly. When you reopened the project, the designer and the resx files were missing from all Windows Forms in the project.

  2524313 (1079984)

OpenESQL

Back to the list

• OpenESQL did not always return a consistent error message or it returned an incorrect error message when a data conversion exception occurred within the ADO.NET run-time system.

Run-Time System

Back to the list

• On Windows 7, building 64-bit native COBOL applications always rebuilt the entire project. This was caused by the Microsoft FileTracker tool, used by the COBOL projects to track dependencies, not working because of Windows 7 security updates. This product now includes a fix to work around this issue.