Rocket® Enterprise Suite

Symptoms If logged in to the ES Admin GUI as SYSAD, then logging out and logging back in as SYSAD, if one browses to the ESMAC page then selects anything on that page, SYSAD becomes mfuser and group to ALLUSER. This has been seen to occur when using the Chrome or Microsoft EDGE internet browsers. For example, using the Chrome browser: Have a server and region setup to use external security such as ADLDS Login as SYSAD or any other user which has access to the region Open ESMAC for the region taking note of the user/group in the upper right Use the reource drop down to change to another user Notice in the upper right your user has changed to mfuser and group to ALLUSER. Diagnosis It was noted that this issue only occurs with the browsers Chrome or Microsoft Edge. This behavior has occurred under ED 2.3 U2, using Chrome Version 67.0.3396.62 (Official Build) (32-bit) and earlier. This does not happen under ED 4.0 even with Chrome Version 67.0.3396.62 (Official Build) (32-bit) or with

Hello,The ODBC driver that are in use with Microfocus Enterprise Analyzer are old and we are not able to connect to SQL Server using them.We have the right drivers that we tested by creating User/System DSN and they are working. Please let us know how can we use those drivers to connect to SQL Server in Microfocus Enterprise Analyzer.?#MSSQL#SQLserver#MFEAwithMSSQL#EnterpriseAnalyzer

  Reported:   The following error is occurring after running the "build odbc" command to compile the ODBC RM switch module ESODBCXA.CBL:   Error building ODBC switch module. Ensure that the Windows SDK LIB directory is included in the setting of the LIB environment variable, and that you have WRITE permission to the current directory.   Solution:   Setting the LIB environment variable to point to the Windows SDK LIB subdirectory that contains odbc32.lib resolved the error#EnterpriseDeveloper#MFDS

  Problem:   After the execution of the following CICS code, and then selecting Session > Quick Keys > Clear from the Reflections menu, the keyboard becomes locked:          EXEC CICS SEND TEXT                                                                    FROM (EXIT-MSG)                                                        LENGTH(80)

  Problem:   COBSQ0999E -204 TUTORIAL.PACCY1 IS AN UNDEFINED NAME and COBSQ0125E Cursor not found error when using Jenkins CI software to compile programs Solution:   The Jenkins service was accessing the system xdb.ini file instead of the user specific xdb.ini and was therefore connecting to the wrong location. The error got resolved after adding the below command in Jenkins:   bopt40n /iC:\\ProgramData\\Micro Focus\\Enterprise Developer\\mfsql\\cfg\\xdb.ini /pConnection CSCEHDBB.CurrentLocation=XDB10553 #EnterpriseDeveloper#MFDS

    Problem:   S422 File not found error running a jcl that is trying to access a file on the mainframe.   Solution:   Resolved by going into the Mainframe Access configuration > node tab and putting the full mainframe hostname in the "logical server name" field of the node and then disconnecting/reconnecting  the MFA server connection in the Remote Server Explorer.   #MFDS#EnterpriseDeveloper

Problem : Trying to install the product it shows up the following error: install.sh - ExtractFiles - 001 - Failed to extract productPaX tool returned non-zero return code. RC:- 254   Resolution : This is a pax error which means either there is not got enough space available, or pax is not installed correctly, or there are some files missing. This is an Operating System utility and you will need to check what is missing. Verify whether pax is installed by attempting to execute the "pax" command at a shell prompt. Other commands would be for example: pax -helppax -xhelppax -x helpto get a list of valid archive header formats. The pax program is a POSIX standard utility that can read and write a wide variety of archive formats. An RPM package for pax is included with Red Hat Linux. If it is not already installed, copy the pax-* RPM file from your distribution media (CD #1), or download it

Problem : Unable to perform non-root installer with RPM installer as per documentation. Installing without root user permissions -https://www.microfocus.com/documentation/visual-cobol/VC40/DevHub/GUID-BC84C5EB-9B6E-4802-9068-60276006EF15.html Installer - visualcobol_devhub_4.0_redhat_x86_64.rpm [user@slc01 ~]$ cd $HOME[user@slc01 ~]$ mkdir -p $HOME/rpmdb[user@slc01 ~]$ rpm --initdb --dbpath $HOME/rpmdb[user@slc01~]$ rpm --root $HOME --dbpath $HOME/rpmdb --relocate /usr=$HOME \\ --nodeps -i --nodeps --prefix=$HOME/VisualCOBOL visualcobol_devhub_4.0_redhat_x86_64.rpmrpm: cannot use --prefix with --relocate or --excludepath[user@slc01 ~]$ Resolution : The docs are incorrect and will be updated in the next release.   First part is correct.             cd $HOME           mkdir -p $HOME/rpmdb           rpm --initdb --dbpath $

Problem : Trying to run a compile on AIX using cob64 but it getting the following message: * 009-R Ran out of memory during code generation. Split program into smaller unitscob64: error(s) in code generation: TEST.int Compiling the same same source code on Windows and Linux works fine. Resolution : Most likely a ulimit has been exceeded. Check the ulimit settings on AIX. ulimit -a (a=all) will give you everything to look at. Most likely the ulimit to increase: ulimit -d .... (data seg size (kbytes, -d)) or ulimit -m (memory) #EnterpriseDeveloper#MFDS

Hi, We have successfully installed Enterprise developer 5.0 - 32 bit in our machine(OS- Windows7).When tried to start the server, "ESDEMO", we are unable to start and getting the error messages:-1. I got a pop up message stating "MFDS child processing starting.. Micro focus\\Enterprise Developer\\bin\\casstart.exe. This problem occurs when a program is not fully compatible with Windows.Please contact the program or device manufacture(s) for more information.2. When tried to start the server via command prompt for enterprise developer, I am getting a pop up error message "COBOL Application Server module has stopped working".Can anyone help us to fix this issue?Thanks,Sunil#EnterpriseDeveloper

Problem When running an Enterprise Analyzer (EA) Hot Fix, error 2753 (screenshot below) is reported during the running of the EA module rescan. This means that the Hot Fix is not installed on the machine. Resolution In the support line downloads section of the Micro Focus site, it states that the EA Hot Fixes are full installs. What this means is that they use the normal install method when the Hot Fix executable is run. It does not mean that they contain the full product plus the Hot Fix. The Hot Fix requires that the relevant EA product is already installed on the machine before the Hot Fix can be applied. The error reported is that the module rescan.exe which is part of the EA product, but not included in the Hot Fix, cannot be found on the machine. To resolve this, install the relevant base EA product, which can also be downloaded from the support line site and then reapply the Hot Fix. SI # 3193161 #EnterpriseAnalyzer#SupportTip

Question Although it not common, JCL (Job Control Language) files may contain multiple job definitions. If these types of files are loaded into Enterprise Analyzer (EA) will it be able to verify the file and produce information about the different jobs that are defined in the file. Answer EA currently only supports a one to one relationship between JCL file and Job defined in it. This means that a JCL file can only contain one job within it. A JCL module that contains more than one job defined in it, will fail verification and analysis of that file will not be possible. The current solution is to break up the JCL file into multiple files with each file only containing one job in it. This new files can then be loaded into EA and these can then be verified and analyzed.   SI # 3144917 #EnterpriseAnalyzer#SupportTip

Problem After applying Windows security updates Enterprise Analyzer (EA) Administrator GUI and the main Enterprise Analyzer GUI will not start. Resolution It has been found that applying anyone of the following list of Windows updates, on the relevant of Windows environment stops applications written in Visual Basic v6 from running. As all of the EA GUI’s (main tool, admin tool, pre-request checker and Architecture Modeler) are all written in VB 6, they are affected by this.  To resolve this run the relevant optional update for the Windows environment being used.   List of Windows environments and fixes that cause the issue: Windows 7 and Windows Server 2008 R2: KB4512486and KB4512506 Windows 8.1 and Windows Server 2012 R2: KB4512488and KB4512489 Windows 10 version 1507: KB4512497 Windows 10 version 1607 and Windows Server 2016: KB4512517 Windows 10 version 1703: KB4512507 Windows 10 version 1709: KB4512516 Windows 10 version 1803:&

Question Can you provide general information about running the various brave (*.bj) scripts that come with the product. Answer  There are some general points to make about using the scripts. -         The full list of bj scripts that can be used are documented in the ‘Using Batch Scripts’ help topic.-         The scripts can be found in the <EA Install directory>\\Scripts\\BRP directory.-         Ensure that all parameters that are passed to the brave match the documentation as in upper, lower or mixed case as seen within the docs as all of the scripts are case sensitive.-         Ensure that you enclose all parameters with double quotes as spaces will terminate a parameter. This becomes important when passing a spacey name as a parameter.-         You must pass at least 3 pa

PROBLEM   When I access the 5.0 documentation when looking to adapt AWM extension points, I get the following instruction: "The AWM API and extension points are being modified. Contact SupportLine for information on how to extend application behaviour.”   SOLUTION The correct documentation for this topic will be correctly included in the 5.0 Patch Update 2 release. In the meantime, most of the 4.0 documentation is current: https://www.microfocus.com/documentation/enterprise-developer/ed40/ED-Eclipse/GUID-157DDD66-9385-4514-8332-DEB33D17A138.html   The only major part that has been changed is the AWM Java interface IToolExecutor that was referenced by a toolType function package extension, as mentioned in the V4.0 docs here: https://www.microfocus.com/documentation/enterprise-developer/ed40/ED-Eclipse/GUID-DEAB91CE-B0C3-4348-9D17-859062BEDE0F.html   The toolType “class” attribute has been deprecated and a new “toolExecutor” attribute is available, which needs to ref

PROBLEM   When I access the 5.0 documentation when looking to adapt AWM extension points, I get the following instruction: "The AWM API and extension points are being modified. Contact SupportLine for information on how to extend application behaviour.”   SOLUTION The correct documentation for this topic will be correctly included in the 5.0 Patch Update 2 release. In the meantime, most of the 4.0 documentation is current.   #EnterpriseDeveloper#MFDS

I am getting some inexplicable compiler diagnostics in trying to build a suite of programs as part of an Enterprise 4.0 upgrade.  It would be really helpful to see the copybooks inline, like NetExpress used to.  Is there some sort of compiler directive - and how do I set it - environment variables?#msbuild#EnterpriseDeveloper#MicroFocusCOBOL

All - I'm migrating Mainframe application to Micro Focus Enterprise server environment, Enterprise Developer is our build tool. database on Mainframe is DB2 where are in target infrastructure database is RDS Distribution for SQL Server.Date fields in DB2 are in EURO format which is "DD.MM.YYYY" , data migrated to SQL server is in YYYY-MM-DD format.  I have changed SQL Server Default Language to "British English". I have compiled my COBOL DB2 application with HCOS Compile directives to avoid Application layer changes (no queries have been changed due to HCOS). When my program fetches data from SQL server it's in yyyy-mm-dd format.Can I know if some configuration changes are been missed here? Thanks in advance. #EnterpriseDeveloper

 read more at microfocus FIATC realiza la migración completa de su mainframe IBM z/Series a entornos abiertos con Micro Focus Enterprise   FIATC es la segunda mutua de seguros en España, y ofrece seguros a particulares y empresas en todos los ámbitos: salud, vida, ahorro, viaje, coche y empresa entre otros. Necesitaban simplificar una infraestructura de TI compleja y costosa de forma transpa...   #EnterpriseServer#Server#CustomerStories#Enterprisereflection#Casopráctico#Enterprise#EnterpriseDeveloper

Problem: If <product-install>/bin contains mfds32 and mfds64, why is mfds32 run by default when starting mfds ? Solution: mfds will always start using mfds32, as per the content of the mfds script. The script contains... if [ -f "$COBDIR/bin/mfds32" ]; thenMFDS=mfds32elseMFDS=mfds64fi So mfds32 will always be run if it has been installed. The only way to start mfds using mfds64, is to amend the mfds script to read.. if [ -f "$COBDIR/bin/mfds64" ]; thenMFDS=mfds64elseMFDS=mfds32fi Additional information: mfds64 will run as expected, but mfds32 is the one that has been most tested/used, so the historical preference has been to use mfds32. Since the network requests between mfds and other components that rely on it are identical regardless of bitism, there should be no practical difference between using 32 and 64bit   Incident#3145598 #EnterpriseDeveloper#MFDS

Problem : The messageMN1003E Failed to get license for MTO Error[18] No license code is available for feature MTODevelopment on host 127.0.0.1sometimes appears in the console.log. What does it mean and how can it be removed ? Resolution : MTO - Mainframe Transaction Option is a facility available with Net Express, Server Express and Enterprise Server that enables CICS/JES applications that have been migrated from the mainframe to be maintained, developed and deployed on Windows or UNIX platforms. The message is basically a warning to tell you that you do not have an MTO license. The message will continue to be reported/displayed until you do one of the following... 1. You can get an MTO license, but as you don't use CICS, this seems unnecessary 2. You can set MF_MFDS_DISABLE_LICENSING environment and this will stop the license check. The license check in MFDS is not to enforce feature ability, but simply to not display e.g. CICS configuration screens and security features that do not

Problem : When mass-compiling programs using an ANT script, the ANT script ends with BUILD SUCCESSFUL displayed, even when programs fail to compile or link.  How can this be avoided ? Resolution : The solution is to use the command : ant –lib $COBDIR/lib/mfant.jar –f .cobolBuild –DcobolFailOnError -DcobollinkFailOnError When –DcobolFailOnError  and -DcobollinkFailOnError are used, the ant script will only display BUILD SUCCESSFUL if ALL programs build and link successfully   Incident#3127511 #cobolFailOnError#ANT#cobollinkFailOnError#MFDS#EnterpriseDeveloper

Problem : Is it possible to change the order of the Spool Output in Enterprise Server ? Resolution : Currently the output is  sorted in JOBNUMBER (JOBID) order. The ES_JES_SPOOL_ORDER environment variable can be used to control either ascending or descending JES output queue order, but is there any way to change the default of which column the ascending / descending applies. ES_JES_SPOOL_ORDERThe order in which the spool list is displayed when you first open ESMAC. The default spool order is ascending. Setting this environment variable to 1 changes it to descending order - any other value displays it in ascending order. From version 5.0 of our products, extra sorting capabilities have been added.  The change involves the introduction of a new environment variable :  ES_JES_SORT_SPOOL_BY.  This is used to decide which column is used to sort the spool records in casrdo41.    Accepted values are JOBNAME/SUBDATE/JOBUSER. If anything else is spe

Problem : Does Enterprise Analyzer/COBOL Analyzer support Oracle 12 as its repository ? Resolution : Enterprise Analyzer does support Oracle 12g as its repository COBOL Analyzer only supports MS SQL as its repository Incident# 3158958 #12G#Repository#SupportTips/KnowledgeDocs#Oracle#EnterpriseAnalyzer

Problem : Is it possible to install Cobol Analyzer without installing the Administration  Tool functionality ? Resolution : Installation of the Cobol Analyzer Administration tool is not optional. The Administrator tool is always installed. To remove the Administration Tool, delete "C:\\Program Files (x86)\\Micro Focus\\Enterprise Analyzer\\Bin\\RescueAdmin.exe" . This is located in the <installation>\\bin  folder.   Incident# 3139241 #AdministrationTool#CobolAnalyzer#SupportTips/KnowledgeDocs#EnterpriseAnalyzer