Fixed Errors

The fixed errors that customers have reported are listed in this section. The numbers that follow each error are the Reported Problem Incident number followed by the Customer Incident Numbers (in parentheses). RPIs that have numbers only (and no text) are included to confirm that the RPIs have been fixed, since no further information is required.

Errors have been fixed in the following areas:

• Animator (Character version)
• CAS (COBOL App Server) General
• CAS ES RTS Support
• CAS Resource Manager Interface
• CAS Security
• CAS XA Switch modules
• Checker
• Checker ECM Support
• CICS
• Client/Server Binding
• Cobdebug
• COBOL Program Execution
• Data Tools Converter
• Documentation
• EJB Generation
• Embedded HTML Pre-Processor
• File Handling - External File Handler
• File Handling - Fileshare
• File Handling - Rebuild
• Interface Mapping Toolkit
• J2EE Connector
• JCL
• MDSA API for CAS
• MF Common Client
• MF Communications Server
• MF Directory Server
• MF Server Administrator (GUI)
• NCG
• Product Build System
• RTS
• Remote Debug
• SQL: Cobsql
• SQL: DB2 ECM
• SQL: OpenESQL
• UNIX Publisher
• XML Schema to COBOL generation
• XML syntax support preprocessor
• XML syntax support runtime

Animator (Character version)

• There was a problem attaching to a multi-threaded application using animator. Depending on where the application was when the animator attached, the user might have been presented with a blank Perform/Call stack window. From here, there was very little the user could do to actually debug the application correctly. We have now added two new functions to the Perform/Call stack window: Zoom and View Thread. See Supplementary Information in the Readme for more details.

  1058893 (2140135)

CAS (COBOL App Server) General

• On strict-alignment platforms such as Solaris SPARC, using ES Security with the MLDAP ESM Module and the "Use all groups" option enabled could cause SEPs to terminate with RTS 114 errors, due to a memory alignment issue. This has been corrected.

  546439 ( )

• The name of the exit specified in MFDS was not built properly if it had less than 8 characters. So the exit could not be found.

  1059718 (2148112)

• RTS 249 was produced when we tried to lock shared memory on a terminate immediate and the memory was already locked. The SEP was killed, instead of terminating gracefully.

  1061082 (2178881)

CAS ES RTS Support

• A hang sometimes occurred during REXX initialisation on some Unix platforms when ES security was enabled.

  545176 ( )

• A SEP was not terminated if a fatal run-time system error, such as COBRT105 ("Memory allocation error"), occurred during the loading of a service's main program.

  1060021 (2150248)

• Run-time system error COBRT197 ("Screen handling system initialisation error") occurred when attempting to run a REXX exec in TSO batch.

  1060125 (2151452)

• Members of dynamic PDSs are now located by the IRXJCL utility when run under Enterprise Server JCL on UNIX platforms.

  1060199 (2151854)

• Printer exit-module and Device name were not set properly in the DCA so the process could not start properly.

  1060323 (2152756, 2153794, 2154869, 2178614)

CAS Resource Manager Interface

• The SNMP V3 auditing facility support provided by the Micro Focus Security Pack no longer requires a 3rd party OpenSSL installation, nor does it require an OpenSSL compliant Net-SNMP installation. Its V3 support will now work with a basic Net-SNMP installation after: 1. Installing the Micro Focus MIB file into that installation's MIB collection using mf_audit_net_snmp_deploy.bat from the NetExpress bin directory. 2. Applying the relevant mfauditmgr configuration options from the mf_audit_net_snmp.cfg sample configuration file.

  1060496 (2154810)

CAS Security

• In WS02 and WS03, the default LDAP partition for Enterprise Server security information was "CN=Micro Focus,DC=local". Now, in order to use a similar structure under both Active Directory and ADAM, the default is "CN=Micro Focus,CN=Program Data,DC=local". If you have an existing ADAM-based ES Security configuration from WS02 or WS03, you may have to add a "base=CN=Micro Focus,DC=local" directive to the [LDAP] section of your Security Manager configuration.

  545082 ( )

• When ES LDAP security was enabled, setting a user's description or default group to an empty string would sometimes fail, due to an LDAP processing issue.

  545483 ( )

• If MFDS was configured to use LDAP security, and a user tried to sign on to MFDS using an account that had no default group (LDAP attribute microfocus-MFDS-User-DefaultGroup) associated with it, MFDS could crash.

  546487 ( )

• In previous releases, when using the MLDAP ESM module, ESF Auth calls could fail if the DN (distinguished name) of the resource container was too long; for example, if the container was placed deeper into the LDAP hierarchy. This has been corrected.

  1060132 (2151581)

• On some systems, configuring MFDS to use external security could cause MFDS to crash with a segmentation violation in some situations, due to thread stack overflow. This has been corrected.

  1060239 (2152471)

• In some configurations, when using ES Security with the MLDAP ESM Module, attempting to change a user's password caused an RTS 114 error. This has been fixed.

  1061151 (2179257)

CAS XA Switch modules

• The build script for the DB2 one-phase commit switch module contained a logic error which affected operation on non-HP/UX platforms. This has been fixed.

  545199 ( )

• The SQL Server XA and ODBC one-phase commit switch modules have been updated to support JES-initiated transactions under ES/MTO. -1060310

  1060310 (2153059, 2153103, 2153370, 2153509)

Checker

• An intrinsic function taking an ANY LENGTH data item as an argument no longer produces incorrect run-time results when executed.

  543853 ( )

• A program with a DECLARATIVES section but no matching END-DECLARATIVES, would sometimes result in a hang during compilation. It now receives the checker error message "COBCH0745S END DECLARATIVES missing."

  544131 ( )

• The figurative constant HIGH-VALUES is now processed correctly for programs containing a user defined COLLATING SEQUENCE.

  544703 ( )

• Animating a program with copybooks and the CP processor would result in copybook not found errors from the animator.

  1059285 (2144637, 2146428, 2149680)

• Compiling a multi-program source with the checker directive STICKY-LINKAGE would sometimes produce the internal error "COBOP0013R Illegal intermediate code." Even if this error was not produced, run-time results could still be incorrect when executed. Such programs now compile cleanly and execute correctly.

  1059296 (2142561)

• A program containing a level-78 constant declaration at the start of the SCREEN SECTION would sometimes receive the internal error "COBCH0903S Internal error - Dictionary corruption. Inform Technical Support" during compilation. This now compiles without error.

  1059373 (2145338)

• A program compiled with the INDD directive and defining the associated sysin file in the catalog with attributes different from those of the default for that file, would sometimes receive run-time error "226 EXTERNAL file definition inconsistent" at execution time when a similarly compiled sub-program was called. This now executes without error.

  1059393 (2145418)

• A new Compiler directive, ERRFORMAT, has been added to control the format of error messages displayed on the command line and in .lst files. ERRFORMAT(1) uses the existing format and is the default. ERRFORMAT(2) uses the format used by Mainframe Express and Net Express IDEs.

  1059440 (2145863)

• Syntax error COBCH0324S ("More than one USE procedure for same open mode") occurred when compiling a program that include USE AFTER STANDARD ERROR and USE AFTER STANDARD FILE LABEL clauses on the same file.

  1059491 (2146402)

• Compiling a program with a mainframe directive such as COBOL370 would sometimes result in the error message "COBCH0613S Invalid program name" on an END PROGRAM <quoted literal> statement where the literal was of mixed case - even though the the literal matched the program-id exactly. This now compiles without error.

  1059531 (2146385, 2148390)

• Compiling a class which did not contain any methods would sometimes result in RTS error "114 Attempt to access item beyond bounds of memory" in check.gnt. This now compiles without error.

  1059542 (2146918)

• Run-time system error 114 no longer occurs when running a program containing a STRING statement with sliding source operands.

  1059639 (2147266)

• The syntax DISPLAY UPON CONSOLE WITH NO ADVANCING was executing incorrectly at run time. When compiled with a non-mainframe dialect, the NO ADVANCING phrase had no effect. This is now only the behavior under mainframe dialects as intended.

  1059858 (2149016)

• Qualification of non-unique names defined in both working-storage and object-storage could sometimes result in the checker error message "COBCH0012S Operand is not declared." This now compiles without error.

  1059867 (2149231)

• You no longer receive the error message 56-S "COPY is recursive" when compiling a program with nested COPY statements which use the IN directory syntax and a preprocessor.

  1059963 (2150161)

• A program compiled with REENTRANT(1) which has an ASSIGN name defined in THREAD-LOCAL-STORAGE and no THREAD-LOCAL clause on the FD entry, was compiling cleanly but producing unexpected run-time results when executed. Such programs will now receive the checker error message "COBCH0471S ASSIGN name in THREAD-LOCAL, but no THREAD-LOCAL clause on FD".

  1060144 (2149538)

• A program with a variable length EXTERNAL sequential file, and compiled with a mainframe dialect, no longer receives run-time error message "252 Memory corruption detected" when a READ on that file is executed.

  1060177 (2150778)

• A declaration of an edited field immediately after a unicode field sometimes led to unexpected run-time results when the edited field was referenced. This now executes as expected.

  1060221 (2152091)

• Support has been added so that operands of the form "ADDRESS OF ..." may be specified in MOVE statements. This means that many SET statements can now also be coded as a MOVE.

  1060259 (2150299)

• Syntax error COBCH0214 ("VALUE too long for data item or has too many decimal positions") erroneously occurred when you used the Enterprise COBOL dialect and the TRUNC(BIN) directive to compile a program containing a level-88 data item whose VALUE clause had more digits than the PICTURE definition of its associated COMP field.

  1060285 (2153034)

Checker ECM Support

• A program containing EXEC CICS statements, but compiled without the CICSECM directive was compiling without error and the syntax processed as a format 2 EXEC statement. To avoid ambiguity this now receives checker error message "COBCH0472S No CICS directives have been set".

  1060195 (2150498)

• Syntax error COBCH0012S ("Operand <operand-name> is not declared (message applies to code produced by External Compiler Module)" sometimes occurred when compiling a program containing EXEC CICS statements and nested sub programs.

  1061107 (2178736, 2179837)

• Syntax error COBCH0012S ("Operand <operand-name> is not declared (message applies to code produced by External Compiler Module)" no longer occurs when compiling a program containing EXEC CICS statements and nested sub programs.

  1061205 (2179837)

CICS

• User access rights are now correctly applied to the user when they log on.

  1060911 (2157082)

• The "Use all groups" security manager option did not work correctly for security managers using the MLDAP ESM Module (mldap_esm). Sometimes permissions for groups that were not the user's default group were not applied. This has been fixed.

  1059770 (2148352)

• AutoInstall default terminal IDs and NETNAMEs were generated in the range from A000 to z999 (NETA000 to NETz999). Alpha upper- and lowercase characters were used for the first character. Now, default IDs are generated from A000 to ZZZZ (NETA000 to NETZZZZ) excluding any IDs that start with "P". The first character of the terminal ID is uppercase alpha (A-O, Q-Z). The remaining characters of the ID are each uppercase alphanumeric (0-9, A-Z).

  1060039 (2150734)

Client/Server Binding

• In some releases of Server Express 5.0, the Client/Server Binding demo configuration file specified CSBIND-over-ES ("commsapi=es"), but the instructions were for CSBIND-over-CCI. The configuration file has been corrected to use CSBIND-over-CCI, so the demo works as documented. See the product documentation for more information on CSBIND-over-ES.

  544878 ( )

Cobdebug

• It is now possible to single-step an INT code application running under the single-threaded run-time after it has been dynamically attached to by the debugger.

  544904 ( )

• Dynamic debugging/ remote debug could fail to connect when the IP address was specified, if the DNS reverse lookup tables were not setup correctly. This has been fixed.

  1059428 (2144505)

• The animator will now save breakpoints when using COBESDEBUG if the user specifies the COBAIFNAME environment variable.

  1059472 (2146210)

COBOL Program Execution

• The intrinsic functions NATIONAL-OF and DISPLAY-OF did not work correctly for UTF-8 conversions in a program compiled with CHARSET(EBCDIC).

  1060107 (2151095)

Data Tools Converter

• Run-time system error COBRT114 ("Attempt to access item beyond bounds of memory") sometimes occurred when the Data File Converter validated an input filename.

  1060261 (2152761)

Documentation

• A few of the entries in the EBCDIC/ASCII Translation Tables appendix of the User's Guide have been amended.

  1058067 (2131391)

• The CBL_DIR_SCAN_READ syntax has been corrected.

  1058138 (2132281)

• In the Help, in Programming > COM > COM, COBOL, and .NET > 4: Creating COM Clients > COM Automation Exceptions, the example requires a third parameter. This has been added.

  1059489 (2146432)

• The limit on the number of files for sorting or merging has been amended to read 128.

  1059847 (2148941)

• The Help topic "To export a service interface" now provides additional information on the architecture of the generated .sie file. -544564

  544564 ( )

EJB Generation

• The code generated for very large arrays no longer causes compilation errors.

  1059788 (2148695)

• The handling of large arrays/fields has been fixed.

  1060709 (2156560)

Embedded HTML Pre-Processor

• The status value is now returned in the correct 64-bit memory address.

  545000 ( )

File Handling - External File Handler

• Read operations on a line sequential file which has been opened for sharing, and which has been extended by another process since the open, now successfully reads all added records to the end of the file.

  1059490 (2146333)

• An incorrect file status value of 10 is no longer returned for a READ NEXT operation which is using an alternate key, if the file handler configuration READSEMA=OFF is in effect and the file has been updated since the previous START or READ NEXT has been performed.

  1059960 (2149820)

• Under certain extreme conditions, if a disk I/O error occurred while a new record was being added to an indexed file, the index could have become corrupted. The following items have been added to help recover transactional files open at the time of a Fileshare failure: configuration file option FSIDXINTEGRITY, environment variable FSIDXINTEGRITY, additional values for the standard record header. See Supplementary Information in the Readme for more details.

  1060013 (2150054, 2150132)

• Run-time system error COBRT144 ("Boundary violation") sometimes occurred when writing to a mainframe print file if NOHOSTFD was specified.

  1060272 (2150542)

File Handling - Fileshare

• Access to a Fileshare file whose non-spacey filename is enclosed in double quotes is now redirected to the Fileshare server if the FHREDIR.CFG file specifies the non-quoted filename.

  544491 ( )

• A new FSVIEW function has been added which will allow a temporary user to be added to Fileshare only for the lifetime of the Fileshare process. See Supplementary Information in the Readme for more details.

  1053612 (2088677)

• Fileshare client applications which are sent CTRL+C signals while communications are in progress will now respond to the signal once the communications are complete. Previously the signal was ignored.

  1059346 (2145057)

File Handling - Rebuild

• Rebuild no longer finishes processing with a 114 error.

  1059884 (2149314)

Interface Mapping Toolkit

• In Enterprise Server, web service interfaces defined with a user field called "fault" now get handled correctly.

  1060399 (2154048, 2154122)

• In a COBOL web service client, a doc-literal SOAP request now correctly includes any attributes specified for the outermost field.

  1060526 (2154071)

• Interface mapping to COBOL fields defined as PIC G() or PIC N() has been enabled.

  544377 ( )

• The "Create an IMS Web Service Interface" chapter of the Application Extension IMS tutorials has been updated to reflect a change that requires users to enter the transaction name. -546670

  546670 ( )

• The interface field being renamed is no longer erroneously moved to the bottom of a group, if the field was part of a group structure.

  1059360 (2144734)

J2EE Connector

• The javac error was occurring because of the method size being too large for multi-dimensional arrays. The array data is stored in a sidefile and prevents the method size from becoming too large.

  1058834 (2139653)

• A Custom Class specified as output will not cause a COBOL Exception.

  1060224 (2152316, 2155512)

• You can now connect to Enterprise Server using NEX J2EE Server and JDK 1.5.

  1060691 (2156473)

JCL

• The return codes for the IDCAMS PRINT and REPRO (with and without the COUNT option) commands and the VERIFY command for various data sets (such as PS, VSAM, empty and non- empty) have been changed to be more consistent with the return codes returned on the mainframe.

  1059342 (2145137, 2146276)

• The dump format of dataset display is now correctly formatted regardless of the data contained within the dataset.

  1060402 (2154137)

• Concatenated instream and non-instream datasets are now handled correctly.

  1059762 (2148477)

• Existing but empty (zero file size) members of dynamic PDSs are no longer erroneously removed.

  1059687 (2147864)

• You can now create dynamic PDSs via JCL. For example, the following JCL will create TEST.DYN1 as a dynamic PDS whose members are files in the directory C:\DPDS with the extension .DAT: //DD1 DD DSN='TEST.DYN1',DISP=(NEW,CATLG), // DCB=(RECFM=FB,LRECL=123,DSORG=PO) //*MFE: %PCDSN=C:\DPDS\*.DAT

  1060109 (2151357)

• JCL Spool Housekeeping will now continue following a failed delete.

  1060074 (2150416)

• IDCAMS REPRO will now pad (with blanks) short LSEQ input records to the minimum record length (for primary and alternate keys) for VSAM datasets.

  1060056 (2150834)

MDSA API for CAS

• When external security was configured for MFDS, and an ES region was started using the MFDS file repository as its directory, the casmgr32 process could hang during startup. ES will now start correctly in this situation. Note that the repository will be processed using MFDS internal security, rather than the configured external security, when accessing the files directly rather than through MFDS.

  545174 ( )

• Where security is not enabled, user authorization checks are no longer performed for jobs submitted via the Internal Reader.

  1060587 (2155303)

MF Common Client

• Web Service requests made to a server that sends 100-Continue responses no longer result in an error 14 from the Web Service proxy.

  1060044 (2150799, 2151072, 2152489)

• Owing to a change in the installation mechanism for the Security Addpack, the Micro Focus Common Client was unable to find the default CA root certificate file, which caused client-side SSL processing to fail if the root certificate file was not specified in mf-client.dat. This has been corrected.

  1060222 (2152098)

MF Communications Server

• In previous releases, the EZASOKET API SOCKET function set ERRNO 12 when no more sockets were available. To match mainframe behavior, it now sets ERRNO 1002.

  539794 ( )

• If a TN3270 listener is configured for an Enterprise Server that does not have MTO enabled, and a TN3270 client connects to the listener, the client now receives an explanatory message indicating that MTO is not enabled. In previous releases, the client received a misleading error message such as "LU name in use".

  542737 ( )

• On Windows, the EZASOKET API function CONNECT, when called on a non-blocking socket, would set ERRNO to 35 instead of 36. It now sets ERRNO to 36, to match mainframe (and POSIX) behavior.

  1058571 (2137043, 2178156)

• Some TN3270E clients incorrectly send non-zero sequence numbers. In some cases, this could cause Enterprise Server to misinterpret part of the data stream, producing various errors such as incorrect AID bytes. MFCS now recognizes these sequence numbers and handles them correctly.

  1060872 (2156133)

MF Directory Server

• The name of the predefined Web Services / J2EE listener in Enterprise Server has been changed from "Web Services" to "Web Services and J2EE", to better reflect its use.

  530323 ( )

• The default system administrator user "SYSAD" should have been automatically added to the MFDS Internal Security Manager when installing WS02 and WS03 on top of Net Express or Server Express 5.0 WS01, but it was not. If the user "SYSAD" does not exist, then WS04 MFDS will create it when it first starts up.

  545216 ( )

MF Server Administrator (GUI)

• In previous releases, a Security Manager object definition in MFDS that had more than 255 bytes of configuration data could not be edited or deleted. This problem has been fixed.

  545036 ( )

NCG

• Repeated loads from decimal items now always return the correct values.

  545342 ( )

• Arithmetic now works as expected in optimized code.

  546457 ( )

• Using opt(1) where .int code was not compiled for animation will no longer cause a 114 error.

  546464 ( )

• Unicode constants in 'MOVE ALL "constant" TO data-field' entries now correctly pass as many copies of "constant" to the data-field as are necessary to fill the field.

  1056649 (2115509)

• An error in "accept from date", "accept from time" in generated code in reentrant programs has been fixed.

  1059592 (2147234)

• An EXTFH.CFG file containing SPACEFILL=OFF no longer causes error "* File I-O error: $COBDIR/ncg.ops" at generate time.

  1059691 (2147889)

• An incorrect use of predicated code on IA64 has been fixed.

  1059769 (2148424)

• A move of a PIC N to a numeric item produced error "013-R Illegal intermediate code" when compiling to native code. This has been fixed.

  1060280 (2152091)

• SIGN-FIXUP was not applied to MOVEs of ASCII data to numeric fields in generated code. This has been fixed.

  1060362 (2153805, 2157375)

• The Divide using remainder and on size error clause now works as expected if the remainder(2) directive is used.

  1060431 (2154264)

• When HOSTARITHMETIC was set and the truncated result of a COMPUTE was reused in another calculation, the second result was wrong in generated code at OPT(2) and above. This has been fixed.

  1060452 (2154469)

Product Build System

• For HP-UX, gzip did not work on PA-RISC 1.1

  1059822 (2148960)

RTS

• Loading a CSO with hidden entry points no longer results in an RTS 114 error at process termination.

  544820 ( )

• An scCSO, created with cob -y, will now be unloaded by the operating system when the application (that originally loaded it) tries to unload it.

  545204 (2148181)

• A memory leak no longer occurs when calling the NLS message handling routines.

  545431 ( )

• When a self-contained callable shared object (created with cob -y) was loaded using a full path, an RTS 173 error could occur if it was loaded from a directory that was not on LIBPATH/LD_LIBRARY_PATH/SHLIB_PATH. This has now been resolved.

  1059747 (2148181, 2148371)

• On HP/UX, the performance of CBL_ALLOC_MEM has been improved.

  1059991 (2148672)

• Modules linked using the threaded version of the dynamic shared run-time library could intermittently fail to execute correctly.

  1060117 (2150884)

• CBL_MEM_VALIDATE() did not always detect that a memory block had been corrupted. This has been fixed.

  1060178 (2150778)

• Previously, in the faultfinder configuration details you could specify: set faultfind_outfile="fault%p.log". Where 'fault' would be a name of your choice, %p would be replaced with the process id of the faulting process, and '.log' would be another name of your choice. Now we have added the %d and %t options. See Supplementary Information in the Readme for details.

  1060198 (2151783)

• MFEXTMAP now handles filenames with embedded spaces and no longer gives a "9/004: Illegal file name" error at run time.

  1060686 (2156336)

• When using a third party C-ISAM file handler, an OPEN INPUT could incorrectly lock the file.

  1060753 (2154591)

• The Faultfinder log file now includes the failing code PC for generated code programs on the call stack.

  1061202 (2154746)

Remote Debug

• Dynamic debugging of JCL and IMS from Net Express to Server Express now works correctly.

  1060184 (2151754)

SQL: Cobsql

• The Cobsql preprocessor was updated so that when terminating an EXEC SQL statement, the period character is written within Area B.

  1056920 (2118840)

• The COBSQL preprocessor now correctly reports errors issued by the Oracle Pro*COBOL 1.8.xx precompiler.

  1057993 (2130152)

• The COBSQL preprocessor now correctly processes input filenames greater than 65 characters in length.

  1058421 (2135014)

• The COBSQL precompiler has been updated to more thoroughly detect when Pro*COBOL errors had occurred, and to abort compilation.

  1059125 (2142946)

• The COBSQL preprocessor now correctly honors the Pro*COBOL lname option when searching for the Pro*COBOL list file output.

  1060207 (2151928)

SQL: DB2 ECM

• EXEC SQL INCLUDE files specified in other directories should now be found correctly by the OpenESQL precompiler when using Visual Studio.

  543691 ( )

• DB2 UDB V9.5 (VIPER 2) uses a new PID structure that resulted in DB2 compile error 4904. This is now fixed.

  545916 ( )

SQL: OpenESQL

• The OpenESQL run-time was updated on UNIX platforms to work correctly with the unixODBC Driver Manager.

  1060097 (2151159)

UNIX Publisher

• UNIX publisher no longer gives an access violation when publishing a project that contains a text file with no dependencies, such as a readme.txt file.

  1060357 ( 2152212, 2153530)

XML Schema to COBOL generation

• CBL2XML now cleans up all recursive reference nodes which caused memory access errors.

  1059685 (2147718)

• Prefix support is now enabled in XMLIO output.

  1059755 (2148239)

• CBL2XML now handles Reference Element correctly.

  1060900 (2177411)

XML syntax support preprocessor

• The XML preprocessor now handles words with an underscore '_' correctly.

  544378 ( )

• A PERFORM statement in a preprocessed COBOL program with XML syntax was not recognised during Stepping in Animation.

  1059328 (2144846)

• The XML preprocessor now reads the data item (SIGNED numeric with usage COMP) correctly.

  1060352 (2146280)

XML syntax support runtime

• CLOSE statments no longer return the wrong I-O status if the physical document is removed.

  1059617 (2147385)