This section describes significant changes in behavior or usage in the current and past releases of Enterprise Test Server. These changes could potentially affect the behavior of existing applications or impact the way the tools are used.
The SafeNet Sentinel licenses are no longer supported, and you need to use AutoPass licenses starting with release 10.0. Contact your account manager to replace your existing SafeNet Sentinel with AutoPass licenses.
Enterprise Server security features provided by the VSAM External Security Manager (ESM) module are enabled by default. This includes support for authentication and authorization for users, user groups, and resources. On installation of the product, a password will be randomly generated for the SYSAD user. This password will be stored in the Vault Facility and can be retrieved using the following command:
mfsecretsadmin read microfocus/temp/admin
See the VSAM ESM Module chapter for more information on configuring the VSAM ESM Module. See Enterprise Server Security Considerations in After Installing for more details on the impact from this change.
The intrinsic function LENGTH and special register LENGTH OF were not always returning the correct result for PIC N NATIONAL fields. These have been updated to the correct behavior, namely returning the number of characters for the former and number of bytes for the latter. If your legacy code has been relying on the previously incorrect behavior, results may now differ.
The SafeNet Sentinel licenses are no longer supported, and you need to use AutoPass licenses starting with release 10.0. Contact OpenText Support for Micro Focus Products to replace your existing SafeNet Sentinel with AutoPass licenses.
The LOCKDB feature replaces the functionality of the Enterprise Server Cluster Global Lock Manager (GLM). See Enterprise Server LOCKDB for more information.
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) ...
A new EXTFH configuration option, FLUSHSYSOUT, is now available to enable you to view the progress of active spool jobs. When set to ON (the default), the buffer is flushed after each record is written, enabling you to view the progress as it runs. Previously, a pre-defined buffer had to be completely written to before progress was displayed; this behavior was more performant, and so can be re-enabled by setting FLUSHSYSOUT=OFF
For an up-to-date list of these changes for release 8.0, see this product's Release Notes available from the Product Documentation section of the OpenText Support for Micro Focus Products website.
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.
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 OpenText Support for Micro Focus Products website.
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.
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".
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 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.
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 OpenText Support for Micro Focus Products website.
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.
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 OpenText Support for Micro Focus Products website.
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.
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.
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.
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.
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.
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.
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.
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 OpenText Support for Micro Focus Products website.
The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).
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.
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.
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.
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.
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).
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 OpenText Support for Micro Focus Products website.
The numbers that follow each issue are the Support Incident Numbers followed by the Reported Problem Incident (RPI) number (in parentheses).
JES000058E JES validation - Product requires new spool control files. Run spool conversion utility, splconv, to create them.
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:
Variable | Description |
---|---|
MFSYSCAT | The location and name of the current JES catalog. This is mandatory.
If multiple catalog files are being used (that is, one or more user catalogs are defined), this environment variable should point to the catalog where JES spool datasets are cataloged. |
MVSSPOOLDIR | The location of the current JES spool control files (for example: casspool.dat). This is only mandatory if the location is different to the location of the JES catalog. |
NEWSPOOLDIR | The location for the resulting JES spool control files (that is, the SPL* files if running the conversion, or the old-style spool files if running the regression). This is only mandatory if the location is to be different to the location of the existing spool files. |
MFSYSCAT_ERRS | The number of catalog errors that will be tolerated during the conversion process before the conversion is terminated. This
is optional, and defaults to 100.
If the process is terminated, the following error is produced: *** Error: Error count exceeded - program terminating |
The conversion process runs, and details of the files and records converted are displayed to screen.
*** Error: Error raised on READ of MVSSPL File status is 23 Processing record: Type=15 J#=,job no.> Seq#=<seq no.>
Such a message is produced when a casspool sysout record is found, but no matching record is found in the MVSSPL01/02 file. The record type (15) indicates that this is an active spool record, which should only be present in casspool if a copy of the file were made while the associated ES region was in a started state, or the associated job had crashed.
These messages can be safely ignored, but if more than 100 are generated, the default error limit will be exceeded, causing the conversion to terminate. If this situation occurs, set the error limit to a higher value, using the MFSYSCAT_ERRS environment value, and rerun the conversion process .
JES000058E JES validation - Product requires new spool control files. Run spool conversion utility, splconv, to create them.
If you plan to downgrade to an older version of your current product, any enterprise server region that has been converted or created with the current product will not be compatible. Before you can use them, they must be reverted to using the old JES spool repository.
Use this process if you are wanting to use a JES-enabled region in a previous version of the product:
The regression process runs, and details of the files and records converted are displayed to screen.
You can now use the region identified by the variables in previous versions of Enterprise Developer.If you plan to export a region to Enterprise Server for .NET, any enterprise server region that has been converted or created with the current product will not be compatible. Before you can use them, they must be reverted to using the old JES spool repository.
Use this process if you are exporting a JES-enabled region to Enterprise Server for .NET:
The regression process runs, and details of the files and records converted are displayed to screen.
You can now use the region identified by the variables in Enterprise Server for .NET.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.
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.
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.
See Reserved Words Table at the end of this topic for more information.
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).
2869848 (619107)
2816871 (1099564)
2854207 (1103659)
2852302 (1103304)
2838118 (1101539)
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).
2839272 (1101672)
2835112 (1101201)
2841220 (1101955)
2834206 (1101079)
2698700 (1094266)
2831984 (1100883)
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.
mfaudit.timeout = nWhere 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)
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.
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.
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)
This is a one-time only change to the database.
2843818 (1102248)
2830383 (1100609)
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).
2806239 (1097738)
2807531 (1097783)
2682101 (1092325)
2664675 (1091082)
2786397 (1095265)
2795077 (1096322)
2799213 (1096684)
2816179 (1098882)
2815695 (1098825)
2814249 (1098636)
2812899 (1098412)
2812899 (1099966)
2812878 (1098417)
2794881 (1096221)
2789939 (1095803)
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.
2792382 (1096011)
2804069 (1097253)
Other COBOL subprograms built with previous versions of Enterprise Developer are not required to be rebuilt.
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).
2663890 (1091979)
2697615 (1094527)
2697571 (1094370)
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)
Field | Environment Variable |
---|---|
LANG=PL/I PCB address lists | ES_IMS_PLI_INDIRECT_PCBADDR=D|Y|N
Where:
|
IBM Platform | ES_IMS_IBMPLATFORM=M|D
Where:
|
Secondary Index Sparse exit language | ES_IMS_SPARSE_EXIT_LANG=C|A
Where:
|
2784949 (1095190)
2784622 (1095971)
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:
Or:
Additionally:
2804069 (1097253)
2579600 (1084675)
(606142)
2651654 (1090287)
2660651 (1091290)
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).
2673619 (1093197)
set intLength to testString::Length()must change to:
set intLength to testString::Length
2692826 (1093604)
2671175 (1091627)
2642115 (1089055)
2664639 (1090992)
2659555 (1090759)
(592452)
2686149 (1093587)
2665006 (1091034)
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).
2195519 (1062800)
2643384 (1088993)
2646770 (1089380)
2610362 (1087601)
2619050 (1089095)
2641890 (1088838)
2487164 (1081693)
2562118 (1083203)
2655482 (1090444)
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.
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).
2552658 (1082755)
(594968)
2593798 (1085945)
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).
2550800 (1082337)
2579335 (1084817)
2553438 (1082469)
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).
2549058 (1082441)
2518330 (1079491)
2525670 (1080092)