Hub 2.3 Micro Focus Visual COBOL Development › documentation › books › ... · 2015-11-10 ·...

Micro Focus Visual COBOL DevelopmentHub 2.3

Release Notes

Micro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUKhttp://www.microfocus.com

Copyright © Micro Focus 2009-2015. All rights reserved.

MICRO FOCUS, the Micro Focus logo and Visual COBOL are trademarks or registeredtrademarks of Micro Focus IP Development Limited or its subsidiaries or affiliatedcompanies in the United States, United Kingdom and other countries.

All other marks are the property of their respective owners.

2015-11-09

ii

Contents

Micro Focus Visual COBOL Development Hub 2.3 Release Notes ................5Installation .......................................................................................................... 6

System Requirements for Visual COBOL Development Hub ..............................................6Hardware Requirements for Micro Focus Visual COBOL Development Hub ...........6Operating Systems Supported ................................................................................. 6Software Requirements ............................................................................................7Additional Software Requirements for Micro Focus Visual COBOL Development Hub

................................................................................................................................. 8Installing Visual COBOL Development Hub ...................................................................... 13

Downloading the Product ....................................................................................... 13Installing ................................................................................................................. 13Installing as an Upgrade .........................................................................................14Installing silently ..................................................................................................... 15UNIX and Linux Installer Issues ............................................................................. 15Configuring the Remote System Explorer Support ............................................... 17Repairing on UNIX ................................................................................................. 18Uninstalling .............................................................................................................18

Licensing Information ......................................................................................19To buy and activate a full unlimited license ....................................................................... 19To start Micro Focus License Administration ....................................................................19Installing licenses .............................................................................................................. 19

If you have a license file ......................................................................................... 19If you have an authorization code ...........................................................................19

To obtain more licenses .................................................................................................... 20New Features in 2.3 ..........................................................................................21

Code Coverage ................................................................................................................. 21Compiler Directives ........................................................................................................... 21Data File Structure Command Line Utility .........................................................................21Data File Tools (Technology Preview) ............................................................................... 21Database Access .............................................................................................................. 22File Handling ..................................................................................................................... 23File Locking ....................................................................................................................... 23Library Routines ................................................................................................................23Managed COBOL Syntax ..................................................................................................24Micro Focus Infocenter ......................................................................................................24Micro Focus Unit Testing Framework ................................................................................ 24Preprocessors ................................................................................................................... 25Profiler ...............................................................................................................................25REST service interfaces ....................................................................................................25RM/COBOL Compatibility ................................................................................................. 25Single File Support ............................................................................................................25Tunables ............................................................................................................................25Updated Run-time System ................................................................................................ 26

Known Issues ................................................................................................... 27Significant Changes in Behavior or Usage ....................................................28Resolved Issues ............................................................................................... 31Updates and SupportLine ................................................................................48

Further Information and Product Support ......................................................................... 48Information We Need ........................................................................................................ 48Creating Debug Files ........................................................................................................ 49

Contents | 3

Disclaimer ......................................................................................................... 50

4 | Contents

Micro Focus Visual COBOL DevelopmentHub 2.3 Release Notes

These release notes contain information that might not appear in the Help. Read them in their entiretybefore you install the product.

Note:

• This document contains a number of links to external Web sites. Micro Focus cannot beresponsible for the contents of the Web site or for the contents of any site to which it might link.Web sites by their nature can change very rapidly and although we try to keep our links up-to-date,we cannot guarantee that they will always work as expected.

• Check the Product Documentation section of the Micro Focus SupportLine Web site and the MicroFocus Infocenter for any updates to the documentation which might have been uploaded.

• This product includes OpenSSL version 1.0.1m.

Micro Focus Visual COBOL Development Hub 2.3 Release Notes | 5

http://supportline.microfocus.com/productdoc.aspx

http://documentation.microfocus.com


InstallationNote: If you are installing on Solaris, please read UNIX Installer Issues first.

System Requirements for Visual COBOL DevelopmentHub

Hardware Requirements for Micro Focus VisualCOBOL Development HubThe disk space requirements are approximately:

Platform Installer type Setup

file size

(MB)

Disk space

required for

the installation

Disk space

required for

running

the product

(MB)

Sentinel RMS

licenseserver

(MB)

POWERrunning AIX

Micro Focus installer 419 1.68 GB 838 36.5

HP IA Micro Focus installer 763 3.05 GB 1526 69

System Zrunning RedHat Linux

Micro Focus installer 346 1.38 GB 692 36

x86-64running RedHat Linux


SPARCrunningSolaris


x86-64runningSolaris


System Zrunning SUSESLES


x86-64running SUSESLES


Operating Systems SupportedFor a list of the supported operating systems, check the Product Availability section on the Micro FocusSupportLine Web site: http://supportline.microfocus.com/prodavail.aspx.

6 | Installation

http://supportline.microfocus.com/prodavail.aspx

Software RequirementsNote: This product includes OpenSSL version 1.0.1m.

Before installing this product, you must have the following software installed on your computer:

• Xterm, the terminal emulator for the X Window System, is part of your UNIX/Linux distribution but is notinstalled by default. Use your UNIX/Linux installation media to install it.

• The pax archiving utility is required by the setup file. Pax is distributed with most UNIX/Linux systemsbut, if it is missing, you must install it separately. To verify pax is installed, run pax --help or pax --version at the command line.

• The following operating system libraries must be installed:

Library Platform

SUSE 11 Red Hat 6.x Red Hat 7

glibc-locale-32bit X

gcc (gcc-32-bit) X

gcc*.i686 X X

glibc-*.x86_64 X X

glibc-*.i686 X X

libgcc-*.x86_64 X X

libgcc-*.i686 X X

libstdc++-*.x86_64 X X

gcc*.s390 X X

glibc-*.s390 X X

glibc-*.s390x X X

glibc-devel-*.x86_64 X X

glibc-devel-*.i686 X X

glibc-devel-*.s390 X X

glibc-devel-*.s390x X X

libstdc++-*.i686 X X

gdb* X X X

• Visit the Red Hat Web site for more information.

• Oracle's Java Platform, Enterprise Edition (Java EE) Java 7 or Java 8 is required to execute COBOLJVM code and for native COBOL and Java interoperability. You can download Oracle's Java EE from Oracle's web site and install it anywhere on your machine.

Note:

• On AIX and zLinux, you need to have IBM's JDK. The earliest supported release of IBM's JDKis 7.0 Service Refresh 8. You can get IBM's AIX JDK from IBM's Web site.

• On HP-UX, you need to have HP-UX JDK. The earliest supported release of HP-UX is JDK7.0.11. You can get the HP-UX Java JDK from HP's Web site.

Before you start the installation, you need to set the environment as follows:

Installation | 7

http://www.microfocus.com/docs/links.asp?nx=redhat

http://www.microfocus.com/docs/links.asp?nx=java

http://www.microfocus.com/docs/links.asp?nx=ibmsupp

http://www.microfocus.com/docs/links.asp?vc=hp-home

• You need to set the JAVA_HOME environment variable. When installing the product, set this variable toa 32-bit Java installation or the installation terminates. For example, execute the following:

JAVA_HOME=java_install_dir

where java_install_dir is the path to the JAVA installation directory such as /usr/java/javan.n• You need to add $JAVA_HOME/bin to your system PATH variable. To do this, execute:

export PATH=$JAVA_HOME/bin:$PATH

• You need to set the LANG environment variable to pick up localized messages. The LANG settings areEnglish and Japanese only.

Important: This release requires version 10000.2.990 or later of the Micro Focus LicenseAdministration tool. For local servers, you do not need to install it separately, as the setup file installsa new Visual COBOL client and a new licensing server on the same machine.

If you have a network server, you must update the license server before installing the product as theclient is not able to communicate with license servers of versions older than 10000.2.660. To checkthe version of the license server on UNIX, run /var/microfocuslicensing/bin/mfcesveror /var/microfocuslicensing/bin/cesadmintool.sh.

You can download the new version of the license server software from the Micro Focus SupportLineWeb site: http://supportline.microfocus.com.

Additional Software Requirements for Micro FocusVisual COBOL Development HubTo ensure full functionality for some Visual COBOL features, you might be required to obtain and installadditional third-party software in addition to the prerequisite software installed automatically by the VisualCOBOL setup file. The following information specifies the third-party software required for each feature.

• Application server support for JVM COBOL on page 8• Application server JCA support for Enterprise Server on page 9• Java Development Kit (JDK) on page 10• Database Access on page 10• Database Access - COBSQL (Pro*COBOL) on page 10• Database Access - OpenESQL on page 11• Database Access - DB2 ECM on page 12• XML Extensions on page 13

Application server support for JVM COBOL

Back to Top

Restriction: This topic applies only when the Enterprise Server feature is enabled.

The following application servers are supported using the following JDKs:

Application Servers JDK version Containers support version

Tomcat 7.0.39 1.7 Servlets 2.5

JBoss 7.1.1 1.7 Servlets 2.5

WebLogic 12.1.1 1.7 Servlets 2.5

WebSphere 8.5 1.7 Servlets 2.5

Note:

8 | Installation

http://supportline.microfocus.com

• On AIX and zLinux, you need to have IBM's JDK. The earliest supported release of IBM's JDK 1.7is 7.0 Service Refresh 8. You can get IBM's AIX JDK from IBM's Web site.

• On HP-UX, you need to have HP-UX JDK. The earliest supported release of HP-UX JDL 1.7 isJava 7.0.11. You can get the HP-UX Java JDK from HP's Web site.

• On all other platforms, you need Oracle's JDK. The earliest supported release of Oracle's JDK 1.7is 1.7.027. You can download Oracle's JDK from Oracle's Web site.

Application server JCA support for Enterprise Server

Back to Top

Restriction: This topic applies only when the Enterprise Server feature is enabled.

Java EE 5 and Java EE 6 are supported for the deployment of EJBs generated using the Interface MappingToolkit, as follows:

• Java EE 5 includes support for EJB 3.0 and Java Connector Architecture 1.5• Java EE 6 includes support for EJB 3.1 and Java Connector Architecture 1.6

The following Java application servers are supported using the following JDKs:

Application Servers JDK (vendor) Java EE

JBoss 5.1.0 1.5/1.6 (Oracle) 5

JBoss 6.1.0 1.6 (Oracle) 6

JBoss 7.1.1 1.7 (Oracle) 6

Oracle WebLogic 10.3.5 1.5 (Oracle) 5

Oracle WebLogic 12.1.1 1.6/1.7 (Oracle) 6

IBM WebSphere 7.0 1.5 (IBM) 5

IBM WebSphere 8.0 1.6 (IBM) 6

IBM WebSphere 8.5 1.6/1.7 (IBM) 6

The availability of resource adapters for these Application Servers differs between UNIX platforms. Thefollowing table indicates where support is available for each platform:

Feature/Platform

JBoss5.1.0

JBoss6.1.0

JBoss7.1.1

Websphere 7.0

Websphere 8.0

Websphere 8.5

Weblogic10.3.5

Weblogic12.1.1

AIX 6.1 onRS6000

32-bit 32-bit 32-bit 32-bit 32-bit 32-bit 32-bit

HP/UX11.31 onIntel IA64

32- and 64-bit

32- and 64-bit

32- and 64-bit

64-bit 64-bit 32- and 64-bit

32- and 64-bit

Red HatEL 6.2 onIBM390

32-bit 32-bit 32-bit 32-bit 32-bit 32-bit 32-bit 32-bit

Red HatEL 5.5 onAMDOpteron


Solaris 11on AMDOpteron

32- and 64-bit

32- and 64-bit

32- and 64-bit

32- and 64-bit

32- and 64-bit

Installation | 9

http://www.ibm.com

http://www.hp.com

http://www.microfocus.com/docs/links.asp?nx=java

Feature/Platform

JBoss5.1.0

JBoss6.1.0

JBoss7.1.1

Websphere 7.0

Websphere 8.0

Websphere 8.5

Weblogic10.3.5

Weblogic12.1.1

Solaris 10on SPARC

32- and 64-bit

32- and 64-bit

32- and 64-bit

32- and 64-bit

32- and 64-bit

SUSESLES 11SP1 onIBM390


SUSESLES 11on AMDOpteron


Java Development Kit (JDK)

Back to Top

Compiling Java Either the IBM or the Oracle Java Development Kit (JDK), version 1.5 or later, isrequired for compiling Java.

InterfaceMapping Toolkit(IMTK)

Restriction: This feature applies only when the Enterprise Server feature isenabled.

The JDK is required for generating Java interfaces from the Interface Mapping Toolkitor the imtkmake command.

Java Beans Your Java client needs to be compiled with JDK 1.6 or greater.

EJBs Use the same JDK vendor and version that is used by the applicationserver.

After installing the JDK, you need to set up your Java environment.

Database Access

Back to Top

Before you can use Visual COBOL to develop and deploy SQL applications that use COBSQL, DB2 ECM,or OpenESQL, ensure any third-party software prerequisites are installed and the environment is setproperly.

Database Access - COBSQL (Pro*COBOL)

Back to Top

Note: COBSQL (Pro*COBOL) is supported for native COBOL only.

Availability Feature/Platform 32-bit 64-bit

x86-64 running Red HatLinux

X X

x86-64 running SUSELinux

X X

IBM System p runningAIX

X X

10 | Installation

Feature/Platform 32-bit 64-bit

IBM System z runningSUSE Linux

X X

Itanium running HP-UX X X

x86-64 running Solaris X X

SPARC running Solaris X X

XA SwitchModule

When the Enterprise Server feature is enabled, the Oracle XA switch module isprovided for COBSQL (Pro*COBOL), and is available on the same platforms as areindicated in the Availability section above.

Certification ofRDBMSPrecompilers forNative COBOL

Certification of RDBMS precompilers with Micro Focus products is the responsibilityof the RDBMS vendor, rather than Micro Focus. Certification information can befound within the relevant Oracle documentation. If you have an Oracle MetaLinkaccount (http://metalink.oracle.com), document # 43208.1 provides details of alllanguage compilers certified by Oracle for use with their precompilers.

Preprocessors COBSQL supports the following database preprocessors:

• Sybase Open Client Embedded SQL/COBOL Version 11.1 or later• Oracle Pro*COBOL Version 11.1 (11gR1) or later• Informix Embedded SQL/COBOL Version 7.3 or later

Compiling On x86 and x86-64 platforms, when compiling with COBSQL for use with Oracle, donot use the COBSQL directive option NOMAKESYN, since this directive results inCOMP host variables, and on Intel platforms these are incompatible with the nativebyte order expected by Oracle.

Executing On HP-UX, to execute an application precompiled using Pro*COBOL (or COBSQL)after you have created a callable shared object of Oracle DBMS routines, you needset an environment variable, LD_PRELOAD, to point to the Oracle client callableshared object, for example:

LD_PRELOAD=$ORACLE_HOME/libdir/libclntsh.so export LD_PRELOAD

where libdir is:

• lib32 for 32-bit environments• lib for 64-bit environments.

A script is available that creates an executable run-time system or a callable sharedobject containing Oracle support. You can find the script in the Micro FocusKnowledge Base article titled Building and executing Pro*COBOL applications onUNIX.

Testing For this version, COBSQL was tested with Oracle 11.1, 11.2, and 12.1.

Database Access - OpenESQL

Back to Top

Availability Feature/Platform Native and JVMManaged COBOL 32-bit

Native and JVM Managed COBOL 64-bit


X X

Installation | 11

HTTP://METALINK.ORACLE.COM

Feature/Platform Native and JVMManaged COBOL 32-bit

Native and JVM Managed COBOL 64-bit


X X


X X


X X

Itanium running HP-UX X X

x86-64 running Solaris X X

SPARC running Solaris X X

NativeCOBOL

• OpenESQL supports access to relational databases using ODBC 3.0-compliantdrivers

• Refer to your driver vendor's documentation to determine whether your driver issuitable for use with OpenESQL

Testing For this version, OpenESQL was tested with:

• Oracle 11.1, 11.2 and 12.1• DB2 LUW 9.5, 9.7,10.1,10.5• SQL Server 2008 R2, 2012, 2014• PostgreSQL 9.4 on the following platforms only:

• x86-64 running Red Hat Linux• x86-64 running SUSE Linux

Note: Micro Focus provides compatibility for PostgreSQL but does not directlycontribute to or support the PostgreSQL open source project. Any issues relating toPostgreSQL functionality should be addressed through an open source supportvendor.

Database Access - DB2 ECM

Back to Top

Availability Feature/Platform 32-bit 64-bit


X X


X X


X X


X X

Itanium running HP-UX X

x86-64 running Solaris

12 | Installation

Feature/Platform 32-bit 64-bit

SPARC running Solaris X

XA Switch Module When the Enterprise Server feature is enabled, the DB2 XA switch module isprovided and is available on the same platforms as are indicated in the Availabilitysection above.

Certification ofRDBMSPrecompilers forNative COBOL

Certification of RDBMS precompilers with Micro Focus products is the responsibilityof the RDBMS vendor, rather than Micro Focus. You can find IBM documentcertification information for DB2/COBOL applications within the IBM InformationCenter for DB2, in the topic Support for database application development inCOBOL.

Preprocessor DB2 ECM supports the following database preprocessors:

• IBM DB2 LUW Version 9.5 or later• IBM DB2 Connect Version 9.5 or later• On SPARC running Solaris, 64-bit is supported in IBM versions 10.1 or later

Testing For this version, DB2 ECM was tested with DB2 LUW 9.5, 9.7, 10.1, and 10.5.

XML Extensions

Back to Top

• XML Extensions has the same requirements as Visual COBOL. Both 32-bit and 64-bit versions areavailable. See the XML Extensions for Visual COBOL, available from the Visual COBOL productdocumentation section of the Micro Focus SupportLine Web site for more details.

• Additionally, XML Extensions may be used in conjunction with Terminal Server.

Installing Visual COBOL Development Hub

Downloading the Product1. Use the download links in your Electronic Product Delivery email.

For more information follow the links for the installation instructions and the End User LicenseAgreement.

InstallingNote: Micro Focus offers two types of installers on UNIX and Linux - a proprietary Micro Focusinstaller for installing on UNIX and Linux and a standard RPM (RPM Package Manager) installer forinstalling on Linux. See your product Help for instructions on how to use the RPM installer.

These are the steps to install this product using the Micro Focus installer:

1. Give execute permissions to the setup file:

chmod +x setup_visualcobol_devhub_2.3_platform

2. Run the installer with superuser permissions:

./setup_visualcobol_devhub_2.3_platform

If you don't run this as superuser you will be prompted to enter the superuser password during theinstallation.

The COBOL environment is installed by default into /opt/microfocus/VisualCOBOL, (COBDIR).

Installation | 13

SafeNet Sentinel considerations

• The installation of this product could affect the SafeNet Sentinel licensed components running on yourmachine. During installation licensing is shutdown to allow files to be updated. To ensure the processesrunning on your machine are not affected, you need to use the -skipsafenet option, which skips theinstallation of SafeNet:

./setup_visualcobol_devhub_2.3_platform -skipsafenet

• To protect the SafeNet Sentinel installation from accidental updating you can create an empty filenamed SKIP_SAFENET_INSTALL in /var/microfocuslicensing/ as follows:

touch /var/microfocuslicensing/SKIP_SAFENET_INSTALL

While the file is present, the SafeNet installer does not make changes to the installation or shutdown therunning license daemons. If licensing needs to be updated later, remove the file and install SentinelRMS server manually.

Note:

During the installation process, the installer configures the product's Enterprise Server SystemAdministrator Process User ID. The Process User ID will be the owner of all Enterprise Serverprocesses except the one for the Micro Focus Directory Server (MFDS). The Directory Server process(Enterprise Server Administration) runs as root as this allows it to access the system files and ports.

All Enterprise Server processes you start from Enterprise Server Administration run under theProcess User ID which can affects the file access and creation.

By default, the installer uses the login id of the user that runs the installer for the Process User ID. Tochange the user id after you complete the installation, execute $COBDIR/bin/casperm.sh.

Installing as an UpgradeThis release works concurrently with the previous version of Micro Focus Visual COBOL DevelopmentHub, so you do not need to uninstall it. There are two options for installing the latest version in this case:

• Move the existing installation to a different location and install the latest version to the default installlocation specified by the COBDIR environment variable (/opt/microfocus/VisualCOBOL, bydefault).

This ensures you do not need to change your environment. To move the existing older installation to adifferent location:

1. Execute the following command as root:

mv /opt/microfocus/VisualCOBOL /opt/microfocus/VisualCOBOLversion

2. Install the latest version as described in the section Installing.• Install the latest version in a different location and set the environment to point to it. To do this, run the

Micro Focus Visual COBOL Development Hub installer with the –installlocation option:

1. Execute the following command:

. /InstallFile -installlocation="/opt/microfocus/VisualCOBOL"

Note: You can use variables or the tilde syntax for the path for –installlocation. Forexample, the following examples are equivalent:

-installlocation="/home/myid/installdir"

-installlocation="~myid/installdir"

-installlocation="~/installdir"

-installlocation="$HOME/installdir"

2. Execute cobsetenv to set the environment and point to the new install location:

. /opt/microfocus/VisualCOBOL/cobsetenv

14 | Installation

Note that cobsetenv is only compatible with POSIX-like shells, such as bash, ksh, or XPG4 sh. It isnot compatible with C-shell or pre-XPG4 Bourne shell.

Installing silentlyYou can install Micro Focus products silently by using command line parameters to specify the installationdirectory, user information, and which features to install. You must execute the command with superuserpermissions.

You can use the following command line arguments to install silently on UNIX/Linux:

–silent -IacceptEULA

For example, execute:

[as root] setup_filename –silent -IacceptEULA

After the application is installed, you can silently install the license as follows:

• If you have access to the Internet and an authorization code, execute the following commands:

For 32-bit Windows environments:

start /wait "" "C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\cesadmintool" -term activate AuthorizationCode


start /wait "" "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\cesadmintool" -term activate AuthorizationCode

• If you don't have access to the Internet but have a file from Micro Focus that contains the license string:


start /wait "" "C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\cesadmintool" -term install -f FileName


start /wait "" "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\cesadmintool" -term install -f FileName

where FileName is the name of the text file that contains all the license strings to be used.

UNIX and Linux Installer Issues

Installing on Linux

On Linux, the 32-bit version of Java is required to install and use Visual COBOL for Eclipse. When you startthe installation, if the 64-bit version of Java is already installed on your Linux machine, you might not beable to install Visual COBOL. This is a known issue with the Oracle Java installers for Linux which preventyou from installing both the 32-bit and the 64-bit versions of Java on the same machine. To work aroundthis problem:

• Download the 32-bit Java distribution in a compressed .tar format from the Oracle Web site.• Untar the distribution into a location different from the one used for the 64-bit Java version. For example,

untar in /usr/local/java32 and not in /usr/local/java.• Set JAVA_HOME and LD_LIBRARY_PATH to the 32-bit version of Java so that it is used to install and

run Visual COBOL.

Installation | 15

http://www.oracle.com/technetwork/java/javase/install-linux-64-rpm-138254.html

License Infrastructure Installer

On some Solaris platforms, you can receive the following error message when SafeNet license serverneeds to be installed or upgraded on your machine:

tar: /safenet.tar: No such file or directory

• To resolve this issue, wait for the installation to complete and then perform the following:

1. Navigate to the safenet directory in the COBDIR location.2. With superuser permissions execute: ./MFLicenseServerInstall.sh

• Note: The following information applies when you are installing on Red Hat Enterprise Linux(RHEL) 7.

Certain configuration changes in RHEL 7 (such as the /etc/inittab file no longer available) requireda change in the MF SafeNet license installer for this platform and the way you can manually manage thelicensing service.

By default, the MF SafeNet licensing service is still configured so that it starts automatically whenstarting your machine. Only on RHEL 7, you must use the systemctl command available with the OSif you need to override the default behaviour – for example, if you do not want run the MF SafeNetlicensing service at start-up or if you do not want the service to automatically start when you areconfiguring trace levels.

1. Create a file, MFSafeNet.service, in /usr/lib/systemd/system/ with the following contents:

----------- start of /usr/lib/systemd/system/MFSafeNet.service ----------- [Unit] Description=Micro Focus SafeNet licensing daemons. Documentation=http://supportline.microfocus.com

[Service] Type=forking ExecStart=/var/microfocuslicensing/bin/startboth.sh ExecStop=/var/microfocuslicensing/bin/stopboth.sh Restart=no

[Install] WantedBy=multi-user.target----------- end of /usr/lib/systemd/system/MFSafeNet.service -----------

2. Use the systemctl command to manage the SafeNet service:

[ asroot ] systemctl option MFSafeNet

Where some of the values that option can take are:

reenable Installs the SafeNet service.

is-enabled Checks the status of the SafeNet service. Does not require root privileges.

start Starts the SafeNet service.

stop Stops the SafeNet service.

restart Restarts the SafeNet service.

disable Disables the SafeNet service so it does not start when the machine is booted.

enable Enables the SafeNet Service so it starts when the machine is booted.

For more information about systemctl, refer to the help available with the RHEL OS.

License Server

You need to configure the computer hostname to ensure the license server will start properly.

To avoid performance issues, "localhost" and the computer hostname must not both be mapped to IPaddress 127.0.0.1. You should only map "localhost" to IP address 127.0.0.1.

16 | Installation

The following is an example of how to specify these entries correctly in the etc/hosts file:

127.0.0.1 localhost.localdomain localhostIP machinelonghostname machineshorthostname

where IP is the unique IP address of the computer in xx.xx.xx.xx format.

Configuring the Remote System Explorer SupportThe remote development support from the Eclipse IDE relies upon Visual COBOL Development Hubrunning on the UNIX machine and handling all requests from the IDE for building and debugging programs.Visual COBOL Development Hub provides a UNIX daemon, the Remote Development Option (RDO)daemon, which initiates the RDO as Eclipse clients connect to it. Whichever environment is used to startthe RDO daemon will be inherited for all servers and hence all build and debug sessions.

Configuring the Environment

You may need to configure some aspects of the environment before you start the daemon. This is becausewhen a build or debug session is initiated on the Development Hub from one of the Eclipse clients, theenvironment used will be inherited from whatever was used to start the daemon. A typical example of thekind of environment that might need to be set up would include database locations and settings for SQLaccess at build/run time.

Starting the Daemon

Important: Before starting the daemon you must have the following on your UNIX machine:

• a version of Perl• a version of Java• the as (assembler) and ld (linking) programs on the path, as specified by the PATH environment

variable

To start the daemon on the default port (4075) as a background process, perform this command withsuperuser authority:

$COBDIR/remotedev/startrdodaemon

The daemon will now listen for any Eclipse client processes connecting to that machine on port 4075. Ifyou want to use another port, specify another port number on the startrdodaemon command.

The daemon can also be configured to instantiate the servers on a specified port or range of ports. This isparticularly relevant when you want to only open certain ports through a firewall. To do this, perform thiscommand with superuser authority:

$COBDIR/remotedev/startrdodaemon [<port> | <low port>-<high port>]

where:

• <port> is the port number the daemon should use to listen for connections from Eclipse on the clientmachine. If no value is given, it will be assigned a default value of 4075. This value matches the valueassigned within the Eclipse installation.

For example,

$COBDIR/remotedev/startrdodaemon 4999

This command will start a daemon listening on port 4999 and will use random server ports.• <low port>-<high port> is the range of ports on which the servers (launched by the daemon) should use

to communicate with Eclipse on the client machine.

For example,

$COBDIR/remotedev/startrdodaemon 4080 4090-4999

Installation | 17

This command will start a daemon listening on port 4080 and server ports will be in the range 4090 to4999.

Stopping the Daemon

To stop the daemon, type the following command with superuser authority:

$COBDIR/remotedev/stoprdodaemon <port>

Repairing on UNIXIf a file in the installation of the product becomes corrupt, or is missing, we recommend that you reinstallthe product.

UninstallingNote: Before you uninstall the product, ensure that the Enterprise Server instances and the MicroFocus Directory Service (MFDS) are stopped.

To uninstall this product:

1. Execute as root the Uninstall_VisualCOBOLDevelopmentHub2.3.sh script in the $COBDIR/bindirectory.

Note: The installer creates separate installations for the product and for Micro Focus LicenseAdministration. Uninstalling the product does not automatically uninstall the Micro Focus LicenseAdministration or the prerequisite software. To completely remove the product you must uninstall theMicro Focus License Administration as well.

To uninstall Micro Focus License Administration:

1. Execute as root the UnInstallMFLicenseServer.sh script in the /var/microfocuslicensing/bin directory.

The script does not remove some of the files as they contain certain system settings or licenses.

You can optionally remove the prerequisite software. For instructions, check the documentation of therespective software vendor.

18 | Installation

Licensing InformationNote:

• If you have purchased licenses for a previous release of this product, those licenses will alsoenable you to use this release.

• The latest version of the SafeNet licensing software is required. See the Software Requirementssection in this document for more details.

• Your entitlement for using this product is governed by the Micro Focus End User LicenseAgreement and by your product order. If you are unsure of what your license entitlement is or if youwish to purchase additional licenses, contact your sales representative or Micro FocusSupportLine.

To buy and activate a full unlimited licenseTo buy a license for Visual COBOL, contact your sales representative or Micro Focus SupportLine.

For instructions on using the Micro Focus Licensing Administration Tool, see Licensing in the VisualCOBOL help.

To start Micro Focus License Administration

Log on as root, and from a command prompt type:

/var/microfocuslicensing/bin/cesadmintool.sh

Installing licenses

If you have a license file

1. Start the Micro Focus License Administration tool and select the Manual License Installation option byentering 4.

2. Enter the name and location of the license file.

If you have an authorization code

Authorizing your product when you have an Internet connectionNote: This topic only applies if you have an authorization code.

The following procedure describes how to authorize your product using a local or network license server.The license server is set up automatically when you first install the product.

Licensing Information | 19

http://supportline.microfocus.com/

http://supportline.microfocus.com/

1. Start Micro Focus License Administration.2. Select the Online Authorization option by entering 1 and pressing Enter.3. Enter your authorization code at the Authorization Code prompt and then press Enter.

Authorizing your product when you don't have an Internet connectionNote: This topic only applies if you have an authorization code.

This method of authorization is required if your machine does not have an Internet connection or if normal(automatic) authorization fails.

In order to authorize your product you must have the following:

• Your authorization code (a 16-character alphanumeric string).• The machine ID. To get this, start the Micro Focus License Administration tool and select the Get

Machine Id option by inputting 6. Make a note of the "Old machine ID".

If you have previously received the licenses and put them in a text file, skip to step 6.

1. Open the Micro Focus license activation web page http://supportline.microfocus.com/activation in abrowser.

2. Enter your authorization code and old machine ID and, optionally, your email address in the EmailAddress field.

3. Click Generate.4. Copy the licenses strings from the web page or the email you receive into a file.5. Put the license file onto your target machine.6. Start the Micro Focus License Administration tool and select the Manual License Installation option by

inputting 4.7. Enter the name and location of the license file.

To obtain more licensesIf you are unsure of what your license entitlement is or if you wish to purchase additional licenses for VisualCOBOL, contact your sales representative or Micro Focus SupportLine.

20 | Licensing Information

http://supportline.microfocus.com/activation

New Features in 2.3Enhancements are available in the following areas:

Code CoverageVisual COBOL now provides support for code coverage of native COBOL applications directly from withinthe IDE where code coverage uses the Test Coverage functionality. You can produce code coveragereports for applications running in the COBOL run-time and for applications that run in Enterprise Server.

To produce reports, you need to enable code coverage in a project's properties, compile your applicationand then run your application with code coverage to produce the relevant reports. For applications thatrequire an Enterprise Server instance, you start the enterprise server with code coverage.

Compiler DirectivesThe following Compiler directives are new in this release:

EOF-1A Treats a 0x1a character in the source file as the end of file.

JVMDECIMAL Determines the type in which certain items are exposed. This directive affectsCOBOL data items of type 'decimal' and non-integral numeric items exposed as aresult of either ILSMARTLINKAGE usage or the PROPERTY keyword.

NLS-CURRENCY-LENGTH

Specifies the number of bytes to allocate for the currency symbol in a PIC field.

NULL-ESCAPE Treats a 0x00 character in the source file as an escape character for other non-printable characters in the source code.

The following Compiler directives contain new parameters in this release:

DBSPACE The new parameter 'MIXED' extends the DBSPACE directive to be able to evaluate dataitems in programs that contain a mix of single-byte and double-byte strings.

Data File Structure Command Line UtilityThe Data File Structure Command Line (DFSTRCL) utility is a DOS-based command line utility thatenables you to create record layout (.str) files from COBOL debug information (.idy) files. You can usethe utility to process a single .idy file or batch process up to 100 .idy files.

Data File Tools (Technology Preview)Note: This is a technology preview feature only. It is being made available to allow you to test andprovide feedback on this new capability; however, this feature is not intended for production use and itis not supported as such. Furthermore, Micro Focus does not guarantee that this feature will bedelivered at a GA level and if it is, then the functionality provided might differ considerably from thistechnology preview.

The Data File Tools (Technology Preview) is a new standalone text editor in which you can create and editdata files. By nature of it being a 'technology preview' product, it does not currently include all the

New Features in 2.3 | 21

functionality that was available in the previous version of Data File Tools - now referred to as Classic DataFile Tools. If you require any of the functionality not provided in this version, you can still use the classicversion by accessing it in the usual way.

To run Data File Tools (Technology Preview), type mfdatatools2 from Visual COBOL's command prompt or a terminal.

Database AccessThe following new features have been added as part of database access support:

COBSQL This release provides:

• Selection and configuration of the Oracle Pro*COBOL preprocessor for compilingCOBSQL applications in a project's properties on the .

• Support for COBOL directives SOURCEFORMAT(TERMINAL) andSOURCEFORMAT(VARIABLE) for Pro*COBOL applications.

DB2 ECM This release provides:

• Support for the MFHCO environment variable across all platforms by default. See theHCO DB2 compiler directive option topic for details.

• A new DB2 compiler directive option, OPTPER (NOOPTPER), that enhancesperformance for CHARSET EBCDIC processing. See the OPTPER DB2 compilerdirective option topic for details.

• A new DB2 directive option, BINDDIR, which specifies an alternative directory in whichto write the DBRM file created during compilation. . See the BINDDIR DB2 compilerdirective option topic for details.

OpenESQL This version of Visual COBOL supports the following new OpenESQL features:

Date/TimeProcessing

This release provides streamlined datetime processing for ODBC andJDBC.

Performance This release includes a new SQL compiler directive option, OPTPER(NOOPTPER), that enhances performance for CHARSET EBCDICprocessing. See the OPTPER SQL compiler directive option topic fordetails.

PostgreSQL In this release, PostgreSQL 9.4 has been tested with OpenESQLusing the following PostgreSQL software:

Server software PostgreSQL EnterpriseDB version 9.4.4

Client software • psqlODBC driver version 09.03.04.00• JDBC41 PostgreSQL driver version 9.4-1201

In this release, PostgreSQL 9.4 has been tested with OpenESQL onthe following platforms:

• X86-64 running Red Hat Linux, 32- and 64-bit• X86-64 running SuSE Linux, 32- and 64-bit

Note: Micro Focus provides compatibility for PostgreSQL butdoes not directly contribute to or support the PostgreSQL opensource project. Any issues relating to PostgreSQL functionalityshould be addressed through an open source support vendor.

22 | New Features in 2.3

SQL Server This release provides support for the SQL Server OUTPUT clause.

XA SwitchModules

Restriction: This feature applies only when the Enterprise Server feature isenabled.

In this release, the XA interface has been redesigned to provide:

• Consistent look and feel for SQL Server, DB2, and Oracle user personalization• Consistent look and feel for both RM dynamic and static registration (SQL Server, DB2,

Oracle, generic one-phase commit)• Additional support for two instances of the same switch module using Web Services

applications via the new XAID compiler directive

File HandlingThis release contains the following new configuration options:

ACUFH Enables or disables the use of the ACU file handler (ACUFH), which is required to handleVision and RM/COBOL indexed files.

ESACUFH Enables or disables the use of the ACU file handler (ACUFH) for file handling operationsrunning under Enterprise Server. ACUFH must also be enabled for this option to take effect.

File LockingIn versions prior to Visual COBOL 2.3, the semantics of the sharing phrase specified in an OPENstatement or used within a call to CBL_OPEN_FILE were not correctly applied in some cases on UNIX andLinux platforms. From version 2.3 onwards, the sharing phrase is correctly honored when the tunablestrict_file_locking=true is set, which is the default setting.

Example of potential changes in behavior:

• Process-A opens a file with read-only access and a sharing mode that denies other processes writeaccess (SHARING WITH READ ONLY).

• Process-B then attempts to open the file with read-only access and a sharing mode that denies otherprocesses read access (SHARING WITH NO OTHER).

With strict_file_locking=true, Process-B is unable to open the file, because Process-A hassuccessfully opened the file allowing only read access.

With strict_file_locking=false, Process-B successfully opens the file.

If your application encounters unexpected OPEN conditions or fails to open files, it might be as a result ofthe new file locking behavior. In such circumstances, we recommend that you review the file locking andsharing requirements of your application and refactor your source code to work with the default setting. Theoriginal file locking and sharing behavior can be restored by setting strict_file_locking=false.

Library RoutinesThe following library routines are new in this release:

CBL_MANAGED_SESSION_GET_USERDATA Retrieves user data saved in the current RunUnit.

CBL_MANAGED_SESSION_SET_USERDATA Sets user data in the current RunUnit.

The following library routines contain new parameters in this release:


CBL_LOCATE_FILE You can now specify a file name that is a null-terminating string, which has resultedin three new values available for the user-mode parameter.

Managed COBOL SyntaxThe following enhancements have been made to the managed COBOL syntax:

• The TYPE OF type-name[ANY...] syntax enables you to obtain the System.Type (.NET) orjava.lang.Class (JVM) object for a generic class, interface, or delegate.

• The self:: or super:: syntax is no longer required to access inherited data within a subclass.• The ATTRIBUTE-ID syntax enables you to define new attribute types, which can be used in various

contexts.

Micro Focus InfocenterThe Micro Focus Infocenter Web site (http://documentation.microfocus.com) has been upgraded and nowincludes the following improvements:

• Scope being persisted when you select a product documentation in the Product Documentation sectionon the Micro Focus SupportLine Web site and choose to view the documentation in the Micro FocusInfocenter.

• Updated Scope settings - provides the ability to nest four levels deep when setting a scope.• Scope being persisted between browser sessions once it has been set.• Creating automatic scopes using the Search Topics icon, .• A link to change the scope from the search results when there are too many results.• Improved Boolean search expressions.• Details included with the search results.• Help on how to use the Infocenter and how to construct search expressions - available using the

Infocenter Help button, .

Micro Focus Unit Testing FrameworkNote: This is a technology preview feature only. It is being made available to allow you to test andprovide feedback on this new capability, but it is not intended for production use and is not supportedas such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA leveland if it is, then the functionality provided might differ considerably from this technology preview.During the preview, you are encouraged to share your feedback and experiences via the Micro Focuscommunity forum - http://community.microfocus.com/microfocus/).

The Micro Focus Unit Testing Framework is an xUnit style testing framework, available from the commandline, for procedural COBOL applications.

It includes much of the architecture you would expect in an xUnit framework. The test runner is a 32- or 64-bit executable that you run from aVisual COBOL shell prompt. A test fixture or suite is a COBOL programcompiled to .so that can include the setup, the test case code, and the teardown associated with the testcase.

Test results are available in a number of formats. By default, results are displayed to screen and to a .txtfile, but you can use additional parameters on the command line to produce reports in JUnit format.



http://community.microfocus.com/microfocus/

PreprocessorsSupport has been added in the IDE for enabling and using multiple preprocessors with your projects.

A new page, , has been added to the project's and the files' properties of native COBOL applications toenable you to choose one or more preprocessors to use when building your application and to specify theirorder of execution.

New reporting capability is now available for user preprocessors: resp-main code 18 indicates that a buffercontains a data name to be marked as modified by the immediately preceding preprocessed line. The dataname may be qualified and resp-more contains the column information for the reference.

ProfilerVisual COBOL now provides support for Profiler for native COBOL applications directly from within the IDE.To produce reports, you need to:

1. Enable Profiler in the COBOL property page for a project.2. Compile your application to apply the changes.3. Run your application with Profiler to produce the relevant reports.

REST service interfacesRESTful service interfaces utilizing JSON as the media type in request and response messages are nowsupported using the Interface Mapping Toolkit. This enables you to extend COBOL applications usingmodern transport payloads and protocols.

RM/COBOL CompatibilityThis release includes improved support for RM dialect applications. Please consult with Micro Focus beforeconsidering a transition from RM/COBOL to Visual COBOL.

Single File SupportThe recommended way to work with files within Visual COBOL is to include them in a project. Forsituations where you might want to quickly open edit a single file, Visual COBOL now provides support fornative COBOL files in the IDE when the file is not opened as part of a project. There is limited support forthe IDE editing, compiling and debugging features as full support requires a project file.

TunablesThis release of Visual COBOL contains the following new tunables:

putenv_interface Provides backward compatibility for UNIX systems in which the operating system'sputenv() function is required when setting environment variables.

strict_file_locking Enables a new, more reliable method of file locking for UNIX systems. See FileLocking for more information.

This release of Visual COBOL contains the following updates to tunables:


default_cancel_mode A new parameter, and default, has been introduced for this tunable; seedefault_cancel_mode for more information.

subsystem_cancel_mode A new parameter has been introduced for this tunable; seesubsystem_cancel_mode for more information.

Updated Run-time SystemCOBOL Server has been updated to provide an execution environment capable of running applications thatwere each built using different development products. A consequence of this is that If your application hasa main COBOL executable (.exe) that was built with a previous version of Visual COBOL, you shouldensure that the executable is rebuilt and packaged with the new run-time system. You can rebuild from theIDE or the command line.

Other COBOL subprograms built with previous versions of Visual COBOL are not required to be rebuilt.


Known IssuesRefer to the Known Errors and Restrictions topic in the Product Information section of your product Help.

In addition, note the following:

Debugging

Remote debugging does not work for programs running on AIX or HP machines, if you are trying to debugusing Visual COBOL installed on a Linux machine.

Enterprise Server

• The Historical Statistics Facility may generate incorrect records for SSTM-enabled enterprise servers.• Enterprise Server instances will fail to start if they have been configured with the MLDAP ESM module

to use external security and are started using Enterprise Server credentials that are not configured with"user administration" privileges (that is they do not have an allow update ACE in the "UserAdministration" security resource in the Enterprise Server Administration). A fix for this is available if youinstall HotFix 1 of version 2.3. of this product.

ICETOOL Emulation

ICETOOL emulation for managed code is not available in this release.

Resource Adapters

Trying to deploy the local resource adaptor mfcobol-localtx.rar to WebLogic may fail with aClassCastException. To work around this issue, you need to deploy mfcobol-xa.rar first, then need toundeploy this file and deploy the local one, mfcobol-localtx.rar. If there are issues deploying usingthe WebLogic GUI, you can use the command line. If there are issues with this as well, try reducing thelength of the command (for example, by moving the file to a location with a shorter path).

REST/JSON IMTK implementation and the same-origin policy (SOP)

HTTP requests sent from scripts within a web browser to REST services deployed on an enterprise servermight fail due to the same-origin policy (SOP). Some browsers might implement (or support plugins thatimplement) techniques for relaxing SOP such as cross-origin resource sharing (CORS) that enablesending cross-origin requests successfully. For REST services, Enterprise Server does not implement amethod for relaxing SOP. This means that browsers that implement CORS (or any other SOP relaxationtechnique) might still forbid requests made from scripts due to Enterprise Server not implementing theequivalent technique on the server side.

Setup

• On UNIX, check UNIX Installer Issues before you start the installation.

Known Issues | 27

Significant Changes in Behavior or UsageThis section describes significant changes in behavior or usage. These changes could potentially affect thebehavior 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 theReported Problem Incident (RPI) number (in parentheses).

• CAS Security• CAS XA Switch modules• Compiler• File Handling - External File Handler• File Locking• IDE• J2EE Connector• MF Server Administrator (GUI)• SQL - HCO for SQL Server• Updated Run-Time System

CAS Security

Back to the list

• The Enterprise Server External Security Facility now includes MLDAP ESM Module 2.0, with a newalgorithm for identifying the best-matching resource-access rule and ACE for resource-access securitychecks. This algorithm is faster and matches most customers' expectations. The new algorithm alsoprovides 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 therequest. For example, a DATASET rule named "USERS.${user}.**" would apply to datasets with therequesting user's name as the second qualifier. In rare cases, customers with complex, ambiguousresource-access security rules might see experience changes in behavior as a result of the newalgorithm. 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 Visual COBOL 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 (Visual COBOL 2.2 update 1 andearlier), if this combination was specified, the SIGN”EBCDIC” directive should have been ignored, toavoid 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 forVisual COBOL 2.2 update 2 or later, and if specified, will be rejected at compile time.

28 | Significant Changes in Behavior or Usage

2786397 (1095265)

Compiler

Back to the list

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

2796076 (1096384)• 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 managedCOBOL code. This is applicable to version 2.2 U2 HotFix 10 onwards.

2824577 (1100823)

File Handling - External File Handler

Back to the list

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

2795077 (1096322)

File Locking

Back to the list

• In versions prior to Visual COBOL 2.3, the semantics of the sharing phrase specified in an OPENstatement or used within a call to CBL_OPEN_FILE were not correctly applied in some cases on UNIXand Linux platforms. From version 2.3 onwards, the sharing phrase is correctly honored when thetunable strict_file_locking=true is set, which is the default setting.

Example of potential changes in behavior:

• Process-A opens a file with read-only access and a sharing mode that denies other processes writeaccess (SHARING WITH READ ONLY).

• Process-B then attempts to open the file with read-only access and a sharing mode that deniesother processes read access (SHARING WITH NO OTHER).

With strict_file_locking=true, Process-B is unable to open the file, because Process-A hassuccessfully opened the file allowing only read access.

With strict_file_locking=false, Process-B successfully opens the file.

If your application encounters unexpected OPEN conditions or fails to open files, it might be as a resultof the new file locking behavior. In such circumstances, we recommend that you review the file lockingand sharing requirements of your application and refactor your source code to work with the defaultsetting. The original file locking and sharing behavior can be restored by settingstrict_file_locking=false.

IDE

Back to the list

J2EE Connector

Back to the list

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

2799213 (1096684)

Significant Changes in Behavior or Usage | 29

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)

SQL: HCO for SQL Server

Back to the list

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

2804069 (1097253)

Updated Run-Time System

Back to the list

• COBOL Server now provides an execution environment capable of running applications that were eachbuilt using different development products. A consequence of this is that if your application has a mainCOBOL executable (.exe) that was built with a version of Visual COBOL prior to version 2.3, you shouldensure that the executable is rebuilt and packaged with the new run-time system. You can rebuild fromthe IDE or the command line.

Other COBOL subprograms built with previous versions of Visual COBOL are not required to be rebuilt.

30 | Significant Changes in Behavior or Usage

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

• Adis• CASRDO• Character Animator• Code Analysis• Compiler• Debugging• Designer• Documentation• ecijava• Enterprise Server• File Handling• HCO for Microsoft SQL Server• IBM Language Environment for OS/390 and VM Support• Interface Mapping Toolkit• Library• Micro Focus Common Client• Micro Focus Communications Server• Micro Focus Directory Server• Micro Focus Server Administrator (GUI)• MLDAP API Interface• RM COBOL• Run-Time System• Setup• SQL: COBSQL• SQL: DB2 ECM• SQL: HCO for SQL Server• SQL: OpenESQL• XML Extensions• XML Support

Adis

Back to the list

• Paste now works as expected when pasting into numeric items under MS(2) with ACCEPT statements.

2800091 (1096820)• When the MS Compiler directive is set, ACCEPT with EMPTY-CHECK now supports manually entering

of a zero for numeric items and a space for alphanumeric items.

2795831 (1096324)• When using ACCEPT WITH UPDATE with the MS Compiler directive, the pre- and post- display

behavior is now the same as that of the MS compiler.

2795709 (1096311)

Resolved Issues | 31

CASRDO

Back to the list

• When trying to access the Catalog page from casrdo45, the JESSPOOL class was checked instead ofDATASET.

2819633 (1099350)• The ESMAC Spool view is now sorted correctly when using a filter criteria.

2798643 (1096681)

Code Analysis

Back to the list

• An issue that was causing a slow down in opening source files in the editor has been resolved.

2804209 (1097351)• Sequential line calculation has been fixed to provide correct position of POI (Point Of Interest) within file.• The analysis component no longer hangs when running on programs containing DBCS (double-byte

character sets).• 'error starting the query' and other similar non-descriptive error messages have been expanded to

include additional information as to what caused the error.• The generic "Violations detected" string, preceding the actual description for the rule, has been

removed from the rule description. Users of Visual COBOL for Visual Studio will no longer see thisstring as part of the description.

Character Animator

Back to the list

• Monitoring large fields no longer causes the Animator to abort.

2828703 (1100628)

Compiler

Back to the list

• A program compiled with the INIT-BY-TYPE directive that contains 'PROGRAM-ID IS INITIAL' syntaxand declarations of index names or data items now produces correct intermediate code.

2831469 (1100741)• Programs compiled with DIALECT"RM" and containing 'PROGRAM-ID .. AS' syntax now execute as

expected.

2830956 (1100700)• The CP preprocessor used in conjunction with the COBSQL preprocessor now correctly replaces any

text affected by the COPY... REPLACING statement.

2826558 (1100370)• When using the WINDOW1 preprocessor, specification of the AUTOCLOSE option no longer prevents

subsequent preprocessor options from being actioned.

2822206 (1099687)• The output from the SETTINGS compiler directive now also appears for programs specified via the

ILSOURCE option.

2822102 (1099604)• The XML GENERATE statement now functions as expected in programs containing the DECIMAL

POINT IS COMMA clause.

2821786 (1099599)

32 | Resolved Issues

• The XML GENERATE statement now executes correctly when the specified FROM operand is a groupcontaining nested ODO tables (which is only possible with the ODOSLIDE directive).

2821779 (1099600)• The INITBYTYPE compiler directive no longer causes spurious flag messages with DIALECT(OSVS).

2820920 (1099488)• The LINE-COUNT Compiler directive now operates as expected.

2817442 (1098979)• The maximum size of data items in a program compiled with the DIALECT(ENTCOBOL) directive now

correctly reflects the respective mainframe values in the latest version of Enterprise COBOL.

2816030 (1098926)• The Compiler now rejects the use of special register names as arguments for reserved word altering

directives. You can only specify standard reserved words with these directives.

2813931 (1098542)• Data names that start with a numeric digit and contain DBCS characters are now accepted by the

Compiler, as expected.

2813223 (1098456)• A MOVE operation of an alphanumeric literal to an unsigned numeric DISPLAY field under RM/COBOL

emulation now executes as expected.

2812561 (1098446)• Data names longer than 30 characters are now flagged when specifying the FLAG option with a

mainframe argument and not just when using the equivalent full DIALECT.

2810924 (1098133)• Compiling a program with the COBSQL preprocessor, which contains a COPY REPLACING statement

with trailing spaces in the replacement pseudo text, now works as expected.

2807470 (1097737)• Compilation of a program containing a GO TO statement that references an undeclared procedure

name, and has the RESTRICT-GOTO directive set no longer results in a run-time exception.

2807280 (1097616)• A user function that specifies a PIC 1 item as a RETURNING field now receives an appropriate compile-

time error.

2806037 (1097470)• The addressability of a linkage data item is now checked correctly.

2805523 (1097453)• Compilation with a mainframe dialect, of a program containing a CALL statement with a mixture of

non-01 level group items and literals, now proceeds as expected with no internal error produced.

2803613 (1097190)• A debugger query of a condition name with a negative literal VALUE now returns the expected result.

2801993 (1097607)• The combination of a mainframe dialect and SOURCEFORMAT(FREE) no longer produces unexpected

compiler errors referring to tokens being in the wrong area of source.

2800332 (1096911)• The specification of an alphanumeric literal in the VALUE clause of a DBCS data item (i.e. the G\N

prefix is missing) is now accepted as an MF extension. This still generates an error under mainframedialects, but can be hidden/suppressed like any other flag message.

2798426 (1096574)• Under DIALECT"MF", the Report Group description entry now permits the NEXT GROUP NEXT PAGE

clause without a LINE clause.


2798367 (1097201)• It is now possible to specify fixed-point numeric literals without a trailing separator space before the next

token or operator. This provides a better mainframe emulation.

2797274 (1096469)• A new CP option, ANYCOPYCASE, now provides more flexibility in matching the case of copybook

names.

2797035 (1096494)• Previously, numeric items that used a decimal point and the OR sign were truncated when using the MS

display syntax under MS(2).

2795709 (1096308)• DBSPACE(MIXED) directive has been implemented to allow comparison of mixed single and double-

byte spaces to the SPACE figurative constant.

2679222 (1092427)• When importing aVisual COBOL source file, the generation of a CBLast (COBOL Abstract Symbol

Table) file no longer hangs when instructed to process a COBOL.DIR file.• Mixing alphanumeric and national items in intrinsic functions which only allow one type now produces a

syntax error.• A source line longer than the maximum supported by the compiler no longer receives an error about

truncation if the line is simply a comment.• An error reading the default directive file $COBDIR/etc/cobol.dir when COBDATA is set during

compilation has been fixed.

• A bug in accepting a field containing double-byte and single-byte characters has been fixed.

2829369 (1100513)• A bug during compilation has been fixed, which caused a Run-Time System error 114 when generating

32-bit programs using the OPT directive, containing decimal operations.

2819838 (1099305)• An error has been fixed in COMPUTE statements of the following form: COMPUTE a = b / constant

where a and b are COMP-3 or DISPLAY; a has greater than 19 digits and b has less than or equal to 19digits, and constant is a literal which is a power of 10 (such as 10, 100, 1000, etc.)

2808008 (1097715)

• An error in managed COBOL that resulted in EXIT PROGRAM or GOBACK statements not beingexecuted has been fixed. The error could occur when perform ranges overlapped.

2825425 (1100162)• When compiling for JVM COBOL with the ILSMARTLINKAGE directive, pic 9v9 items used as VALUE

parameters are now generated correctly.

2815477 (1098847)• An illegal instruction 'invokespecial' is no longer generated. Previously, in some circumstances, this

could be generated, leading to a verification error on class load.

2811246 (1098205)• When compiling a large program for JVM COBOL, the use of performtype(osvs) or performtype(rm) with

declaratives no longer leads to bad code generation and invalid jump errors when loading the resultingclass.

2695030 (1093952)

Debugging

Back to the list


• Pointer values no longer get incorrectly byte-swapped when their value is accepted.

2824427 (1100287)• Trying to view the values of data-items that contain UTF-8 data no longer corrupts the values.

2810079 (1097992)

Designer

Back to the list

• When importing using the Designer, you now receive an "Source Code Import Wizard Detected ErrorsPage" if there are parsing errors. See your product help for more details. Previously, the import processproceeded even when there were parsing errors. If errors or warnings were reported but the FD and 01extraction process ran to completion, the errors will be reported but the "Next" button is enabled to allowthe partially extracted data items to be imported. The "Back" button is also enabled allowing the processto be repeated once the errors are fixed. If a severe parsing error occurred, the errors are reported and,since they must be fixed, the "Next" button is not enabled.

Documentation

Back to the list

• The product help now includes the optional attributes for the ‘container’ objectclass definition used byEnterprise Server external security.

2801420 (1096977)• The product help now includes information about how to retrieve the Run-Time System error code from

a file status code returned as a decimal value. For example, if you receive 14657 as a value for the filestatus, this is a decimal value. This converts to 3941 HEX. The second byte of this value, 41, must beconverted to Decimal before looking at the RTS error code - thus this HEX value then represents anextended file status code of 9/065 which means the error code is COBRT065, a locked file status.

2822853 (1099769)• The MFJSTATS topic has been updated to clarify that this refers to a COBOL SORT operation.

2828881 (1100446)• The product documentation about the START statement and Relation Conditions now states that THEN

may be used instead of THAN.

2799291 (1096903)• The topic "Using the CP Preprocessor to Expand Copybooks" in the product documentation has been

updated to include the following text: If the MODE=ANSI option is specified to the Oracle precompiler,Pro*COBOL, then you should additionally use CP's SY directive to ensure that the SQLCA getspopulated correctly.

2792368 (1096084)• The default setting for the ES_ESM_PLTPISEC variable is NONE.

2821810 (1099672)• Additional information has been added to the description of the CASSI1400 error message.

2821806 (1099711)• The AdminAPI resource class has been documented for ESF features.

2815870 (1098815)• The Enterprise Server documentation for Retain Periods has been updated to include additional

information specific to spool output.

2790146 (1095777)• The LISTCAT topic in the documentation has been updated to reflect accurate column headings and

descriptions for output format.


2789939 (1095765)• The explanation of error message CASCF0052S has been updated with UNIX-specific information.

2821745 (1099737)• Topic amended to refer to entry_point_mapper rather than entry_name_mapper.

2807744 (1097673)• Details on MF_MVSJOB environment variable added.

2797526 (1096488)• The Micro Focus Communications Server now supports rotational log files. To enable this feature, you

need to edit the mf-server.dat file, which resides in the product's bin directory (Windows), or the$COBDIR/etc directory (UNIX). The mf-server.dat file contains details of this feature under the [logging]paragraph, and full documentation is provided in the online help under "Server Instance Diagnostics:CS Console".

2675327 (1092083)• NONCONNECTED has been added to the list of attributes of DECLARE.

ecijava

Back to the list

• Stateless Java ECI requests no longer cause memory leaks in MFCS as a result of abandonedsessions.

2822108 (1099645)

Enterprise Server

Back to the list

• When using an EXCI link and a PPT defined with commarea 32767, the modified commarea was notreflected back to the caller.

2830739 (1100654)• It is possible to configure a Visual Studio or an Eclipse project to perform emergency debugging of an

application running in an enterprise server even when the server is operating in production mode (withdynamic debugging disabled). To prevent this, starting with this HotFix, you can use the environmentvariable ES_PRODUCTION in the server’s [ES-Environment]. When set to Y, this variable prevents theIDE from initiating a debug session.

2825848 (1100160)• When using a secure region and when the environment variable

ES_ESM_DISABLE_DFLTUSER_ESMAC is set to Y, clicking on the Home button in the signon pagenow correctly opens the MFDS page.

2824772 (1099949)• When the casspool.dat file is shared across multiple servers (excluding cluster scenarios), ESMAC

displays all jobs, including those that are not running in the current server. However, it is only possible tocancel jobs that are running in the current server. For other jobs the CANCEL button is disabled.

2824230 (1099917)• It is now possible to start a BATCH printer in ESMAC if its name consists of space characters only but

an exit name is provided.

2819122 (1099216)• When using ESMAC, Enterprise Server now correctly loads the MFESMAC resource class, when

necessary. Previously, it was loading the ESMAC class.

2814789 (1098652)


• You can now use the environment variable ES_ESM_DISABLE_DFLTUSER_ESMAC in order to disablethe ESMAC default user. When this variable is set, the "DEFAULT" button on the logon screen isdisabled and a valid userid and password must always be entered.

2813092 (1098438)• DBCS fields are now processed correctly when the PS attribute is set in the DSECT rather that defined

in the MAP in single field, groups and OCCURs.

2811683 (1098233)• Web service timeout values are no longer truncated to two digits.

2792860 (1096024)• An issue with dynamic debugging has been fixed where, previously, the ports that were freed were not

being reallocated.

2785911 (1095510)• An artificial restriction on the size of cookies passed when invoking ESMAC requests has been

removed. Previously, this was causing Run-Time exceptions.

2692460 (1094557)• The characteristics of an FCT that references a cataloged file are now refreshed on each file open.• If a file was already present, the date for an open request was not sent to the file handler.• Open and close operations are no longer recorded in the transaction logs and replicated by extension

when they are associated with open input requests.• A secondary node in a group no longer attempts to take over the role of a primary node. The entire

group now initializes correctly and all roles are assigned as expected.

• This release provides a number of enhancements to the CAS administration console:

• Improvements have been made to the log-in mechanism for situations where you are using anExternal Security Manager to secure the MFDS and Enterprise Server, and you are logged on toMFDS and ESMAC using different user accounts – for example, "user1" and "user2", respectively. Ifyou navigate from ESMAC to MFDS and you log off "user1" from the MFDS, this will nowautomatically log off "user2" from ESMAC as well.

• When using an external security manager, if you sign off from ESMAC, the sign on screen no longerpreserves and displays the userID of the last user that was logged on.

• An issue with the "Home" link in the ESMAC sign on page when the environment variableES_ESM_DISABLE_DFLTUSER_ESMAC is set has been resolved.

2814494 (1098607)

• A memory leak occurred in the External Security Facility's MLDAP ESM Module in some HotFixreleases of COBOL Server 2.2 Update 2.

2833758 (1101024)• When using the Enterprise Server External Security Facility with the audit feature, some audit events

generated by ESF Admin requests (such as ADDGROUP or ALTGROUP commands specifying manygroup members) may include too much information to fit in a single audit event. These parameters arenow split across multiple audit events of category 5, type 3. Each split parameter has a unique number(per process), and each piece of a split parameter has a sequence number. The original event willcontain a string with the split parameter identifier.

2827010 (1100238)• The new resource access authorization processing in Enterprise Server's MLDAP ESM Module (LDAP-

based security), introduced in HotFix releases of COBOL Server 2.2 Update 2, now correctly handlescases where multiple access control entries have the same rank. For example, this may apply when allgroup mode is enabled and an Access Control List (ACL) contains Access Control Entries (ACE) fordifferent groups the user belongs to.

2826650 (1100313)


• In COBOL Server 2.2 Update 2 HotFix 06 only, when Enterprise Server External Security is used withthe "Version 2 Authentication" mode enabled, some ACEs might not be processed or applied. This hasbeen fixed.

2826650 (1100195)• When using the Enterprise Server External Security Facility (ESF) with auditing enabled, and using the

ESF Admin API (programmatically or with the Enterprise Server Administration web interface or theesfadmin command-line tool) to make certain changes to security data, very large audit events could begenerated. In some circumstances these could cause the Audit Manager process to crash or hang theprogram making the request. This has been corrected by truncating parameter information for very largesecurity administration requests.

2825505 (1100158)• When using Enterprise Server External Security Facility (ESF) with the optional Referential Integrity

User Exit, integrity constraints are now ignored for Access Control List (ACL) actors containing wildcardcharacters. This enables ESF Admin actions that include resource access control ACLs containingwildcard actors.

2824117 (1099908)• The optional ESF Referential Integrity user exit module no longer fails with an LDAP "filter error"

message when processing certain resource-rule commands, such as ALTRESOURCE, for resourcerules with names that include an asterisk, "*".

2824049 (1099884)• The "referential integrity" sample user exit module for Enterprise Server External Security no longer

causes the MFDS process (Enterprise Server Administration) to terminate when external security withthe exit is configured for MFDS, and MFDS is used to add a user or to perform some other securityadministration tasks.

2823947 (1099880)• A new MFDS command line startup option (-b) is now available. Specifying -b disables the

establishment of anonymous MLDAP API sessions.

2818587 (1099264)• This release enables you to prevent an Enterprise Server Monitor and Control (ESMAC) user from

displaying an enterprise server's environment variable settings using the "Env. Vars." button or the directURL. To enable this feature, you need to create a new element (ENV*) in the LDAP schema in theCN=MFESMAC group below CN=Enterprise Server Resources.

This release includes an updated copy of the supplied LDIF import files that contain this change. Oncethis element is installed in the security manager, you can control the visibility of the environmentvariables page by configuring the group/user access rights using the microfocus-MFDS-Resource-ACEattribute.

2811696 (1098264)• The number of security manager user group members displayed by the Enterprise Server

Administration and the esfadmin tool is no longer limited to a maximum of 1024.

2807579 (1097703)• Trying to use the SNMP audit emitter with Enterprise Server no longer fails with a run-time system error

114.

2800729 (1096951)• The MLDAP ESM Module, part of the Enterprise Server External Security Facility, now supports

"nested" user groups where one user group can contain another user group. Members of the containedgroup belong to both groups. This enables administrators to define very large user groups as well ashierarchies of user groups.

2510993 (1078988)• A new option, "LITERAL=YES" has been provided in the Enterprise Server External Security Facility's

Administration API, and in the esfadmin command-line utility. When this is set, "*" is not interpreted as a


wildcard when using any of the administrator's LIST commands. This is particularly useful for listingresource access rules that include "*" in their name. Search the product documentation for esfadmin formore information.

• Oracle and OCI XA switch modules leaked memory when using user personalization.

2830922 (1100676)

• When issuing an ENQ change request in a cluster environment, the request to change the lock typewas being sent to the GLM but not processed locally. It is now also being processed locally.

2826218 (1100148)• During a cluster RECONNECT request, each cluster client sends a list of active locks and the GLM re-

populates the Global ENQ. Since the introduction of the VSAM shared options, the lock may alsocontain a tca ptr which is used to store the client's casmgr information. This is required for lock withpersistence server. A pointer set to low-value was sent as part of a GIVELOCK request, but on the GLMthat value was not used. This causes a run-time system error 114 in casgreqt on the RECONNECT/GIVELOCKS function. This fix allocates the required tca for client casmgr for a RECONNECT request,sets up the pointer depending on the lock persistence type as well as the clients casmgr PID.

File Handling

Back to the list

• You now receive an RC16 error message, if a PDSM file is missing from a list of concatenated DD's.

2821187 (1099770)• Indexed files are no longer corrupted when their file size limit is reached.

2817599 (1099359)• When lock mode is set to 'automatic', with single record locking, the lock from the previous operation is

released at the start of the next file operation; this is to avoid an ABBA deadlock situation occurring.

2816981 (1099052)• A new file handler configuration file option (STRICTLSEQ) has been added. Only use this option if

instructed to by Support.

2814458 (1099019)• RM and ACU files accessed from Visual COBOL no longer crash with a 114 error for I/O operations on

a non-existent optional file opened for input. An appropriate error code is now returned.

2809718 (1098141)• MFSORT now takes the record length from a previous output file, if its record length is specified, rather

than defaulting to the value in the SORTIN statement.

2808188 (1098243)• The rollback recovery process is now working as expected.

2802180 (1097066)• This release provides a new format of the dataset allocation override rules file that supports multiple

conditions.

2783138 (1095007)• The ACUFH interface between the MF File Handler and the RM File Manager will no longer report an

05 status (optional file created) to more than one COBOL run unit for creation of the same file. The 05status will be reported to the COBOL run unit that actually created the file. The RM File Manager thatruns under ACUFH and the Micro Focus File Handler for Visual COBOL now includes optimizations thatenable it to use pread and pwrite system calls and to report status 99 (record locked) quicker. Theseoptimizations match the optimizations added to the RM File Manager within RM/COBOL.

• The file handler configuration file (extfh.cfg) now supports the following options:

• ACUFH=ON/OFF - enables or disables any calls to ACUFH. ON by default.


• ESACUFH=ON/OFF - enables or disables calls to ACUFH while running under Enterprise Server.OFF by default.

Note: As a result of this change, calls to ACUFH are now disabled by default when running underEnterprise Server.

• Copying an ESDS file no longer causes an RTS114 error.

2811583 (1098244)• When a file is closed under Enterprise Server, the file's details are correctly removed from Fileshare.

Previously, some details were not removed.

2810549 (1098111)• When handling indexed files, the correct .IDX file is now being processed.

2803247 (1097279)

HCO for Microsoft SQL Server

Back to the list

• The DISCARDDN option is now enabled.

(608200)

IBM Language Environment for OS/390 and VM Support

Back to the list

• The Language Environment utilities are now available as Java managed code.

2826067 (1100134)• Mainframe Language Environment support (LE Services) is now available in Micro Focus Visual

COBOL and COBOL Server.

2799388 (1097806)• The Language Environment functions CEEGMT, CEEUTC and CEELOCT now return the number of

seconds to millisecond precision.

2796098 (1098276)• The I-S-Info field of the Language Environment (LE) Feed-Back group has been changed from a pointer

to a PIC S9(9) BINARY item.

Interface Mapping Toolkit

Back to the list

• The Interface Mapping Toolkit was not properly recognizing 64-bit applications, and would not generate64-bit DLL files.

2792065 (1096292)

Library

Back to the list

• Using a dd_ environment variable to specify the path used in CBL_LOCTE_FILE now works asexpected.

2822153 (1099632)

Micro Focus Common Client

Back to the list


• The Micro Focus Common Client, used by COBOL Web Service proxies and other components, nowallows HTTP URLs with certain characters such as ":". It also no longer rejects correct URLs with "%xx"escape sequences.

2828629 (1100520)

Micro Focus Communications Server

Back to the list

• Certain Enterprise Server administration actions such as notifying a running enterprise server of asecurity update could cause MFCS to hang.

2784219 (1095045)

Micro Focus Directory Server

Back to the list

• The generated HTML fragment displayed for an individual resource entity element when using theEnterprise Server Administration HTML GUI to administer an external Security Manager wasoverflowing a fixed size buffer. This is now allocated based on the actual length required.

2828732 (1100545)• Corrected the resource entity that the Enterprise Server Administration GUI checks to determine

whether the external Security Manager administration pages are accessible to a logged on user. Thecorrect resource entity is "User Administration" under the "Enterprise Server Administration" resourceclass.

2828553 (1100539)• Require read permission before returning repository data for authenticated users if MFDS is started with

the -b option.

2828228 (1100364)• Access to password data is prevented on the security manager edit page in the Enterprise Server

Administration HTML GUI.

2827942 (1100333)• When MFDS is secured using an external Security Manager, it does not display internal security

configuration pages which no longer have an effect.

2827786 (1100314)• Correct display of user session data in the Enterprise Server Administration HTML GUI.

2826210 (1100161)• An issue with the persistency of the audit output option in the MF Directory Server security configuration

has been resolved.

2824201 (1099902)• Honor the trace flags values set in an Enterprise Server XML configuration file when importing it into

MFDS via the -g command line option.

2823855 (1099846)• An issue with storing certificate passphrase in the Enterprise Server Administration HTML GUI form

data has been resolved.

2820846 (1099448)• The resistance of the Enterprise Server Administration HTML GUI log-on page to cross-site scripting

attacks has been increased.

2819223 (1099212)• Improve browser caching control to increase security of the Enterprise Server Administration HTML

GUI.


2819218 (1099209)• An issue with storing certificate passphrase in the Enterprise Server Administration GUI has been

resolved.

2819212 (1099207)• The Enterprise Server Administration web page makes additional authorization checks before

displaying screens.

2819069 (1099192)• The Enterprise Server Administration web page no longer displays sensitive session data.

2818974 (1099178)• Password length restriction has been fixed in the Enterprise Server Administration login page.

2818973 (1099179)• Enterprise Server Historical Statistics Facility (HSF) configuration can now be exported and imported

via the mfds -x and -g command-line options.

2815030 (1098695)• Previously, the Enterprise Server Administration journal export to text truncated the exported file.

2802793 (1097108)• It is now possible to expand and collapse items within the tree view of the external security manager

security resources in Enterprise Server Administration.

2801421 (1096979)• The MFDS GUI now correctly displays external Security Manager resource ACL strings that are greater

than 3K byte length.

2800727 (1096978)• The MFDS -x XML export option was not exporting Windows Monitoring and Management configuration

values for enterprise server instances.

2794382 (1096428)

Micro Focus Server Administrator (GUI)

Back to the list

• If access to Enterprise Server Administration is restricted by use of an MLDAP ESM-based externalSecurity Manager, you can now configure a user to have access to the "Security" menu item but not tothe "Options" menu item.

2804728 (1097916)• Previously, when expanding or collapsing items in the tree view for external Security Manager within

Enterprise Server Administration, items associated with a user or a group no longer would always moveto the top of the resource list.

2803399 (1097848)• If MFDS is configured to use an external Security Manager with the Windows "user" class, it is not

possible to edit the users from the MFDS GUI and you receive a warning.

MLDAP API Interface

Back to the list

• The MLDAP ESM module now recognizes a wider range of errors that indicate that the specified LDAPserver is unavailable and, if configured, the server will retry to establish a connection.

2799921 (1098128)• The MFDS GUI and the ESFADMIN utility now display the pages with LDAP query results.

2681539 (1092705)


RM/COBOL

Back to the list

• The RM File Manager for Visual COBOL now provides a mechanism for avoiding RM indexed filecorruption while debugging in managed code.

In Visual COBOL for Eclipse, to avoid file corruption, you need to manually set the environment variableRMFM_PRETEND_FORCE_CLOSED to YES in the Debug Configuration.

Visual COBOL for Visual Studio is preconfigured to avoid file corruption. If necessary, you can alsospecify the RMFM_PRETEND_FORCE_CLOSED variable in a project's Application Configuration File(App.config).

See your product help for more details.

2796890 (1096699)

Run-Time System

Back to the list

• The RM/COBOL version of the “SYSTEM” library routine nows supports the return of an exit-code, fornative COBOL applications.

2830238 (1100599)• When using ADIS DISPLAY statements and the RELDECDELIM=0D0A file handler configuration option

on UNIX, you could receive a Run-Time System error during process termination.

2829860 (1100601)• On UNIX platforms, if the Audit Manager process is recycled, dependent processes will continue to

pass events to it after it's recycled; previously, these processes would hang.

2810770 (1098085)• An error in generated code when initializing comp-2 data items from fractional literal values has been

fixed.

2800938 (1096960)• The tunables default_cancel_mode and subsystem_cancel_mode both have a new setting, which

enables programs to remain in memory after they are canceled; this is opposed to the default behavior,which physically removes .dll files and shared objects from memory when they are canceled.

2690881 (1096628)

Setup

Back to the list

• A problem with the product setup file handling install locations has been fixed.

2802386 (1097065)

SQL: COBSQL

Back to the list

• The COBSQL preprocessor generated an error when it encountered a host variable declared as "01 HVPICTURE S9(9) VALUE ZERO COMP."

2826093 (1100163)• COBSQL now honors the position of the $SET statements in copybooks that are expanded inline in the

editor by the CP preprocessor.

2825364 (1100308)


• COBSQL examined hostvars in commented lines, causing compilation errors.

2824211 (1099928)• CCOBSQL now processes COPY... REPLACING COBOL data items' level correctly.

2813839 (1098531)• The COBSQL preprocessor inserted a NULL character in front of each non-printable character, causing

errors when processing Pro*COBOL (i.e., when COBSQLTYPE=ORACLE8).

2809551 (1097939)• COBSQL did not always correctly handle COPY... REPLACING with text exceeding the 72 column.

2809404 (1097890)• COBSQL incorrectly handled COPY... REPLACING when the level numbers of data items in the

copybook were being replaced.

2807898 (1097765)• COBSQL was not recognizing the DECLARATIVES statement in some scenarios.

2804183 (1097346)• COBSQL now processes COPY...REPLACING statements correctly.

2779818 (1094538)

SQL: DB2 ECM

Back to the list

• The DB2 ECM incorrectly generated code to process SET CURRENT PACKAGE PATH, resulting inSQLCODE -4952 when executed.

2817342 (1098963)• HCO incorrectly handled .bnd files. The new DB2(BINDDIR) directive resolves this issue.

2815734 (1098893)• The DB2 ECM preprocessor incorrectly generated COBDB0103S errors when a fixed CHAR host

variable was defined as greater than 254 characters.

2803193 (1097169)• When FILLER was used in group host variable structure, the DB2 ECM raised an SQL4914 error.

2802547 (1097091)

SQL: HCO for SQL Server

Back to the list

• The OpenESQL pre-compiler no longer incorrectly swaps a colon and blank inside a literal if compiledwith HCOSS directive SQL(DIALECT=MAINFRAME), which was resulting in a -305 SQL error whenexecuted.

2822809 (1099757)• The OpenESQL preprocessor generated incorrect connection information when compiling with the

SQL(INIT) AND CHARSET(EBCDIC) directives.

2814325 (1098596)• The OpenESQL preprocessor sometimes erroneously returned SQLCODE error code 1, NULL value

returned but no indicator variable supplied, when it encountered a stored procedure call.

SQL: OpenESQL

Back to the list


• For managed-code projects, PF_RO_CURSOR and other BEHAVIOR primitive directives were notavailable from the User Interface.

2833926 (1101049)• Some problems related to using ASSOCIATE with the Host Compatibility Option for SQL Server where

the stored procedure name was supplied in a host variable have been fixed.

2831480 (1100747)• HCO with SQL Server (HCOSS) using the ADO.NET run-time system exhibited a problem retrieving

result set locators on the second call and subsequent calls to a stored procedure.

2830688 (1100659)• The SQL CLR wrapper program generated by the Generate SPD File tool caused errors during

deployment when it contained one or more data types exceeding 8000 bytes in size. To eliminate theseerrors, the Generate SPD File tool now generates the SQL CLR wrapper program with MAX SIZE = -1.

2830545 (1100650)• PIC X host variables passed to the server as variable-length data with trailing blank suppression

sometimes caused OpenESQL to return different query results than some earlier versions of thisCOBOL development product.

2829810 (1100685)• When generating a COBOL wrapper program, the Generate SPD File tool did not support the passing

of all parameters for a SQL CLR Stored Procedure definition routine as fixed length. To resolve this, anew option, GENFIXEDLENGTH, has been added.

2829499 (1100629)• A number of issues with PostgreSQL record logic and error handling have been fixed in OpenESQL's

run-time systems for ODBC and ADO.NET.

2828058 (1100338)• When the SQL(PROCOB) directive is set, OpenESQL for ADO.NET now supports anonymous PL/SQL

blocks and the following host variable types: SQL-CURSOR SQL-ROWID SQL-BFILE SQL-BLOB SQL-CLOB SQL-NCLOB

2825199 (1100003)• When compiling with the SQL(PROCOB) directive, the OpenESQL preprocessor sometimes generated

incorrect SQL code when a host variable reference in COBOL was split over multiple lines.

2825194 (1099997)• When using the SQL(CHECK) directives with SQL TYPE CLOB host variables, compilation sometimes

failed.

2819480 (1099342)• The insertion of more that 8000 characters into a SQL Server VARCHAR(MAX) column from a PIC X(n)

host variable caused a data truncation error.

2814679 (1098675)• When SQL(TARGETDB=ORACLE) was set and the FOR UPDATE clause was used to enable row

locking, this combination could sometimes trigger a runtime failure. SQL(TARGETDB=ORACLE) is nolonger required to enable row locking via FOR UPDATE clauses on queries.

2814613 (1098624)• A 114 error on DISCONNECT sometimes occured due to a long-standing bug in Oracle ODBC drivers.

This release provides a workaround. The ODBC specification states that the ODBC row status array isan array of 2-byte integers, but some Oracle ODBC drivers from Oracle 11 onwards have beenobserved to use either 4-byte or 8-byte integers. The OpenESQL runtime for ODBC now automaticallydetects the element size used by the driver when an Oracle connection is opened, and adapts itsbehavior accordingly.

2813428 (1098480)


• OpenESQL now supports OUTPUT clauses in SQL Server INSERT, UPDATE, and DELETEstatements. HCO for SQL Server now supports the DATA-CHANGE-TABLE-REFERENCE clause.

2812940 (1098424)• An SQLCA error message occurred when inserting a record into a table using a SQL CLR stored

procedure with a VARCHAR (max) column where the host variable was more than 8000 bytes.

2812261 (1098390)• The OpenESQL preprocessor incorrectly generated a COBES0100 error when compiling code that

contained GEN-GV-FROM-GROUP and the same host variable used multiple times in same SQLstatement.

2811682 (1098231)• The OpenESQL preprocessor reported an error for LOCK TABLE statements encountered when using

an Oracle database with the SQL(CHECK) compiler directive option.

2808579 (1097797)• When using the SQL compiler directive option to compile a program that contained no SQL statements,

a 153 trap occurred when the OpenESQL preprocessor encountered SQLCODE defined as COMP.

2808076 (1097758)• The OpenESQL preprocessor sometimes generated a "COBCH0302 IF....ELSE or scope-delimiter

mismatch" error if a program defined SQLCODE separately as COMP.

2807937 (1097702)• The OpenESQL preprocessor sometimes generated a STOP RUN rather than a GOBACK at the

program end, which sometime caused improper termination for subroutines not coded with one or moreGOBACK statements.

2807272 (1097624)• The OpenESQL preprocessor produced a COBES0125 or COBES0112 error message when it

encountered indicator variable arrays used with non-host array variables.

2805207 (1097457)• COBOL SQL CLR stored procedures can now open connections to other databases using EXEC SQL

CONNECT statements. For type 6 CONNECT statements, this requires using a post-deployment scriptto alter the connection string for the OpenESQL runtime such that it runs with EXTERNAL_ACCESSprivilege. For other CONNECT statement formats, INSAFE privilege is required. Use SQL Serverauthentication rather than Windows authentication for external connections.

2804010 (1097230)• In some situations, the OpenESQL pre-compiler incorrectly generated a COBES0125 error, "<variable>

should be defined with an OCCURS clause".

2802029 (1097036)• The ODBC ECM incorrectly generated swap logic for COMP fields on singleton SELECTs in managed

applications which could result in field corruption if the variable was used in a WHERE clause.

2801806 (1097049)• The OpenESQL Assistant generated copybooks using the same size for DATETIME2 columns

regardless of their definitions. The OpenESQL Assistant now generates PIC X(26) for DATETIME2(6),and PIC X(29) for all other DATETIME2 definitions.

2799778 (1096776)• A problem that affected the use of 'select *' in OpenESQL subqueries has been fixed.

2799720 (1096751)• A problem with array fetches into PIC N NATIONAL host variables has been fixed in the ODBC run-time

system for OpenESQL.

2799002 (1096790)


• The OCI run-time now handles the NULL indicator correctly when running in 64-bit mode.

2792566 (1096149)• OpenESQL for JDBC now supports positioned updates with PosgreSQL.• The THREAD SQL compiler directive option mishandled threads in certain scenarios.• In certain scenarios, OpenESQL incorrectly handled host variables defined as SQL TYPE DBCLOB

when inserting or fetching DBCS data.• OpenESQL for JVM now supports spaces between the start of an ODBC, JDBC, date, time or

timestamp escape marker and its associated date, time or timestamp literal string when theSQL(DETECTDATE) directive is set.

• Use of the tinyint (pic s99 comp-5) host variable sometimes resulted in bad code generation for someOpenESQL runtime systems. Tinyint is now fully supported on all OpenESQL runtime systems.

• The OpenESQL run-time now truncates DBCS character strings cleanly at a whole character boundary.• Using CHARSET(EBCDIC) in a DBCS locale caused problems with the OpenESQL runtime systems for

ADO and JDBC. This has been corrected by changing the behavior to be consistent with the ODBCruntime. In particular, SO/SI characters are now correctly inserted and removed for EBCDIC and ASCIIdata respectively.

• The one-phase ODBC switch module now handles commit and rollback API calls from applications anduses DSNRLI correctly, together with handling of global temporary tables by HCOSS applications.

XML Extensions

Back to the list

• The XML model file must be accessible to the XML extensions run-time environment. To make the fileaccessible, either add it to the system path, or move it to the directory from which the program is run.

2822399 (1099702)

XML Support

Back to the list

• XMLPARSE no longer reports an error if a prefix is not properly declared and no validation is specified.

2823420 (1099786)• The Compiler no longer errors preprocessed lines containing non-ASCII characters in the indicator

area. Previously, this could cause user programs using the htmlpp preprocessor to fail to compile.

2805067 (1097977)• The XML I/O run-time used to read the whole document into memory which caused an out-of-memory

error.

2801337 (1096999)• The namespace prefix in the namespace declaration is now handled correctly when the element itself

does not contain a prefix.

2799691 (1098150)


Updates and SupportLineOur Web site gives up-to-date details of contact numbers and addresses.

Further Information and Product SupportAdditional technical information or advice is available from several sources.

The product support pages contain a considerable amount of additional information, such as:

• The Product Updates section of the Micro Focus SupportLine Web site, where you can download fixesand documentation updates.

• The Examples and Utilities section of the Micro Focus SupportLine Web site, including demos andadditional product documentation.

• The Support Resources section of the Micro Focus SupportLine Web site, that includes troubleshootingguides and information about how to raise an incident.

To connect, enter http://www.microfocus.com in your browser to go to the Micro Focus home page, thenclick Support.

Note: Some information may be available only to customers who have maintenance agreements.

If you obtained this product directly from Micro Focus, contact us as described on the Micro Focus Website, www.microfocus.com. If you obtained the product from another source, such as an authorizeddistributor, contact them for help first. If they are unable to help, contact us.

Also, visit:

• The Micro Focus Community Web site, where you can browse the Knowledge Base, read articles andblogs, find demonstration programs and examples, and discuss this product with other users and MicroFocus specialists. See http://community.microfocus.com.

• The Micro Focus YouTube channel for videos related to your product - see https://www.youtube.com/user/MicroFocusIntl.

Information We NeedHowever you contact us, please try to include the information below, if you have it. The more informationyou can give, the better Micro Focus SupportLine can help you. But if you don't know all the answers, oryou think some are irrelevant to your problem, please give whatever information you have.

• The name and version number of all products that you think might be causing a problem.• Your computer make and model.• Your operating system version number and details of any networking software you are using.• The amount of memory in your computer.• The relevant page reference or section in the documentation.• Your serial number. To find out these numbers, look in the subject line and body of your Electronic

Product Delivery Notice email that you received from Micro Focus.

On UNIX, you can use the Micro Focus UNIX Support Scan Utility, mfsupport, to create a log file thatcontains the details about your environment, product, and settings. The mfsupport script is stored in$COBDIR/bin.

To run mfsupport:

48 | Updates and SupportLine

http://www.microfocus.com

1. Start a UNIX shell.2. Set COBDIR to the product with issues.3. Execute mfsupport from a directory where you have write permissions.

This creates a log file, mfpoll.txt, in that directory.4. When the script finishes, send the mfpoll.txt file to your Micro Focus SupportLine representative.

Note:

If COBDIR is set to a location that does not contain etc/cobver, the script outputs the contentsof /opt/microfocus/logs/MicroFocusProductRegistry.dat which keeps a list of theinstalled Micro Focus products.

Creating Debug FilesIf you encounter an error when compiling a program that requires you to contact Micro Focus SupportLine,your support representative might request that you provide additional debug files (as well as source anddata files) to help us determine the cause of the problem. If so, they will advise you how to create them.

Updates and SupportLine | 49

DisclaimerThis software is provided "as is" without warranty of any kind. Micro Focus disclaims all warranties, eitherexpress or implied, including the warranties of merchantability and fitness for a particular purpose. In noevent shall Micro Focus or its suppliers be liable for any damages whatsoever including direct, indirect,incidental, consequential, loss of business profits or special damages, even if Micro Focus or its suppliershave been advised of the possibility of such damages. Some states do not allow the exclusion or limitationof liability for consequential or incidental damages so the foregoing limitation may not apply.

Micro Focus is a registered trademark.

Copyright © Micro Focus 1984-2015. All rights reserved.

50 | Disclaimer

Hub 2.3 Micro Focus Visual COBOL Development › documentation › books › ... · 2015-11-10 ·...

Documents

Transcript of Hub 2.3 Micro Focus Visual COBOL Development › documentation › books › ... · 2015-11-10 ·...