Rocket® Enterprise Suite

Problem: When using MFEEE 3.0, a strange compilation error occurs when using the follow SQL syntax...            EXEC SQL                UPDATE EMPLOYEE                    SET STREET = CONCAT(:ASTRING, SUBSTR(STREET,1,20))                WHERE E_NO = 1            END-EXEC When this code is compiled then  the following erroris produced: COBSQ0999E -084 UNACCEPTABLE SQL STMT - ILLEGAL SYMBOL 'CONCAT'   : The item STREET is defined as 20 characters long, and the host variable ASTRING is defined as 4 bytes, with a fixed value of 'ST. '. This only appears when Validate is on and the fol

Problem: From Mainframe Express 3.1 WS01 compiling a DB2 application returns errors regarding missing entry points in DB2AGAPI.DLL ; this includes an RTS173 error against "hcgetenv". If working with DB2 UDB Version 8, you may encounter issues compiling applications with the DB2 compiler directive. This issue does not occur when using DB2 UDB Version 8 FixPak 15, nor with DB2 v9 or later. Resolution: Due to changes implemented to the DB2 support from Mainframe Expess 3.1 WS01, you may find that compiling applications using DB2 UDB Version 8 will fail. To resolve this, you will need to upgrade your DB2 installation to the latest IBM FixPack. You can access downloads from the IBM website (currently at http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg21256059 ). Having applied this FixPack, compilation and execution will then work as expected. Old KB# 2545#MFDS#EnterpriseDeveloper

Problem: I'm getting a precompile error when I try to generate a program with AMB 6.0 that generates fine with AMB 5.0.  AMB 6.0 doesn't handle the continuation of the literal shown below. SCOBOL:               ---- ----1---- ----2---- ----3---- ----4---- ----5---- ----6---- ----7--               DISPLAY 'EXCEPTION FILE IS EMPTY.JOB ENDED NORMALLY WITH                 ...     ' RETURN-CODE 0002'                                Precompile error generated by AMB 6.0               DISPLAY 'EXC

Problem: Having installed Mainframe Express you may encounter this error message.  If so, please follow the steps in the resolution below. Resolution: The easiest and most efficient way is to uninstall and delete everything from the registry and then reinstall. Otherwise you can edit the paths (for the system, tutorial and maintain locations) by using a hex editor so that they point to the true locations.  However, this is somewhat dangerous as it can corrupt the XDB Server locations if done incorrectly.  A hex editor is essential. The problem only occurred in Mainframe Express 2.5 and was later resolved in version 3.0. Old KB# 2485#EnterpriseDeveloper#MFDS

Problem: Problem with FBA record length. In current mainframe we have a batch job which is generating report. Same job we have migrated in micro focus, we have file record lenth 133 in mainframe. When the record length in proc and the Cobol program are same i.e 133 then the Microfocus jobs is aborting When the same length is changed to 134 the same executes successfully The only difference in the out file reports is the extra column inclusion after the page/line break numbers Resolution: As stated this is a mainframe migration program so it is using a mainframe DIALECT by default we will use ADV as the default behaivour envn though when you lookup the ADV directive you will see NOADV is the default. Because the DIALECT will set the ADV directive the NOADV directive must be added after the DIALECT directive. Example DIALECT(ENTCOBOL) NODAV If you are using PCOMP(PCOMMAIN.DLL) USE($PCOMDIR) frin the mainframe migration tool kit you wo

Problem: In the scenario that Mainframe express has been in stalled into C:\\PROGRAM FILES\\MFE and the MFUSER folder into D:\\MFUSER, an error may occur when trying to use the SQL Wizard with the XDB Server running like a Service. The error is... "X001: Cannot perform 'find' on file 'D:\\mfuser\\config\\system\\*.DD?'"   If the XDB Server is run as a "blue screen" server, the error is not visible. How can this be avoided..? Resolution: The problem is being caused by a  service / permissions problem. Follow   START >CONTROL PANEL > ADMINISTRATIVE TOOLS > SERVICES Right click on the  Micro Focus XDB Server for MFE 3.0 services, and choose PROPERTIES. Open the LOG ON tab. The  LOCAL SYSTEM ACCOUNT option should be checked on. Change this, by checking on THIS ACCOUNT. Enter a valid domain/network ID and password, with the correct access to  mfuser\\config\\system\\*.

Problem: When using the MFA browser login, the login boxes do not appear, showing just a small recross in the corner, and an error message is displayed: "Applet LGAPPLET notinited" Resolution: Changing the version of Java in use to Microsoft Virtual Machine (MSVM) solves this problem. (From the original article at http://java.com/en/download/help/jvm_applet_issue.xml) "Some websites have applets written exclusively to run on the Microsoft Virtual Machine (MSVM). They may not work on any other virtual machine. MSVM is based on an old implementation of the Java platform specification 1.1 whereas the Sun Java Virtual Machine (JVM software) is based on the latest Java platform specification. " Old KB# 2558#MFDS#EnterpriseDeveloper

Problem: With MFE 3.1, there can be three XDB.INI files which may be used by a single user application.  The vast majority of our clients should not be modifying their XDB.INI files without using our GUI utilities or under the direction of SupportLine for specialized tracing.  Furthermore, the configuration utilities should be run from the MFE menu rather than an MFE command prompt so they can ascertain the environment properly.   Resolution: The first XDB.INI file that may be used is project specific.  In MFE, the user can have a project specific XDB.INI file by selecting "Project uses its own client-side settings".  When this is set, an XDB.INI file within the project root directory will be used when invoking a program (COBOL or PL/I) from within the IDE or invoking an XDB utility from within the IDE while the project is open. The second XDB.INI is stored in the MFUSER\\CONFIG directory.  This

Problem: At JCL compile time, we want to be able to report standards violations as errors. Resolution: What we found is that the SCAN button in the IDE does not have knowledge of the loadlib in the workgroup. If you do a debug, the exit program is found in the loadlib but if you click on scan, it is not found unless the executable is in the MFE product folder. You can get the program to execute when you do a scan by moving the idy and int code to Micro Focus base\\bin product folder. I compiled this program as non-mainframe, moved it to the base\\bin, selected a JCL member in the IDE and clicked scan. The sample mfjuxit that I will attach to this incident will emit "info" to the build tab when using the IDE "Scan".   Old KB# 2574#MFDS#EnterpriseDeveloper

Problem: Statement was select count(creator) from sysibm.systables; Error was X212: Function not available under current compatibility setting. Resolution: Changed the XDB Server version from V6 to V7 and the statement now runs successfully. Old KB# 2471#MFDS#EnterpriseDeveloper

Problem: We have a need to use a mixture of quotes and apostrophes in a character string. How can this be done? Resolution: The following program illustrates how this can be done:         Identification Division.        Program-Id.  LORINCE.       *  Yes, one can mix quotes and apostrophes       * expected output from this program:       *       * this uses apostrophes       * that's a hit       * that's a hit       * this uses quotes       * the "s are out       * this uses specials ... ,,,       *        Environment Div

Problem: The MFA client patches have moved or been renamed. Do I need to install this patch if I am using MFE 3.0 or MFE 3.1? Resolution: The MFA client patches have been moved to the bottom of the page and they are titled 'Mainframe Access'. These patches are only to be installed if you are using MFA outside of MFE for example as part of a migration or with Revolve. If you have installed MFE or MFE-EE you should apply the MFE websync and not install the patches for Mainframe Access Client. Old KB# 2573#EnterpriseDeveloper#MFDS

Problem: The latest version of the Mainframe Access client side fixpack for Mainframe Express 3.0 - MFD05ALL which is part of the ALL12M30 wrappack is not compatible with Mainframe Access Server v3.0.   Attempting to start Drag and Drop will result in error: MFDAS01: Mainframe access problem: A catalog error was detected. Resolution: Upgrading to Mainframe Access v3.1 (available from the SupportLine website) will resolve this issue and is the recommended course of action. If this is not practical for your installation, there is a hot fix available for this issue - please contact your local SupportLine office and request this hot fix - please quote Support Incident 2182510. This hot fix will be included in the next Mainframe Express 3.0  wrappack due Autumn 2008. Old KB# 2537#EnterpriseDeveloper#MFDS

Problem: There is a concern about dragging & dropping modules from Endevor onto the workstation and being put into the wrong folders. We would like to have an automated process that, when pulling from Endevor, it will put the modules into the correct folders. It is likely that the developer will have more than one project folder. Is ther anything that can do this currently?What alternatives do we have to do this? Resolution: There is no process to ensure you Drag & Drop anything from the mainframe to the correct folder on the PC.  You could, however, run from a command line to actually enter the path where you want the file. Below is an example.  Go to the MFE command prompts and type the following: C:\\mfuser30\\projects>mfdas import binary c:\\temp\\PGM222.cbl FROM END ENV 'MVSTEST' SYS 'ADMIN' SUB 'UTILS' MEMBER PGM222 STG '1' TYPE=COBOL CCID=REC COMMENT=comment This will download the PGM222 Cobol member to the c:\\temp d

Problem: Is it okay to run MFE 3.0 client desktops against a MFA 3.1 application server. The specific uses for our server include services for  Fileshare, XDB, MFA. Resolution: Yes, MFE 3.0 is capable with running against a MFA 3.1 mainframe application server. Old KB# 2559#EnterpriseDeveloper#MFDS

Problem: When adding PRC and JCL files to our Mainframe Express project we are getting errors saying  "procedure not found". Why is this happening? Resolution: Procedure files, those with a .PRC file extension, are called from JCL files. As these types of files are added to a Mainframe Express project, we do a JCL scan on them trying to resolve all the PROC and INCLUDE statements. It is always best to first add the .PRC files and then the .JCL files to the project. If you are defining your own PROCLIB PDS's with JCLLIB statements, then add the .PRC files to their appropriate PDS so they will be found by the JCL scan. If you are letting Mainframe Express default to use its own PROCLIB, then it will create a default MFE.PROCLIB.Lnn (a number from 1 to 99) and when the .JCL files are added to the project, we will find the PRC files in that PDS.   Old KB# 2547#MFDS#EnterpriseDeveloper

Problem: MFA client is unable to establish a connection to the MFA server. Both the client and server are new installations. The server is up and running, no error messages in the log. The client information is correctly configured for node, port, catalog search criteria, userid and password. Customer can telnet to the MFA port successfully. Port is not blocked by the firewall. Resolution: A wireshark (www.wireshark.org) protocol trace revealed no requests were being sent from the client machine. The MFE installation was corrupted, and the MFA client was not functioning correctly. Reinstalling MFE resolved the issue. Old KB# 2522#MFDS#EnterpriseDeveloper

Problem: Micro Focus used to supply their own Source File Comparison addpack for Workbench.  However, this is no longer available generally for Mainframe Express 3.0. Resolution: A third party product called Beyond Compare from Scooter Software http://www.scootersoftware.com/ can be used instead. Old KB# 2465#MFDS#EnterpriseDeveloper

Problem: customer does not wish to use MFA's Data Connect feature, and has no need for the Data Connect server to run Resolution: Comment out the ASGROUP=MFAS section in the SERVERS member to prevent MFAS from being started.  '*' in col 1 makes the line a comment: *<ASGROUP=MFAS> *ASPROC=MFAS *ASJOB=* *ASSERVER=MFARSC00 *ASMINIMUM=1 *ASMAXIMUM=1 *ASGROUPID=0 *<END> Also turn off Data Connect in the PARMS: MFA FEATURE = NO Old KB# 2454#MFDS#EnterpriseDeveloper

Problem: MFDAS01 error at the MFA client Customer is also unable to telnet to the MFA port The MFA server is active and listening on the specified port (2020) with no apparent error messages Resolution: Port 2020 is blocked by the customer firewall allow ip traffic through this port Old KB# 2470#MFDS#EnterpriseDeveloper

Problem: We are moving catalogued datasets from one location to another and need to be able to update the Mainframe Express Catalog with the new entries. We have many datasets and doing this manually is too time consuming. What can we do? Resolution: The following write-up describes our how mvspcrn can be used to update Mainframe Express Catalog entries. Be aware that the parameters are case sensitive.      Bulk Update of Catalog If you move a number of datasets from one place on your PC or PC network to another - from one directory to another, from one network server to another, or from the control of one Fileshare server to another - you need to make sure each one's catalog entry shows the new path in the physical filename. If the catalog and the datasets reside together on the same path, there is no problem. By default, paths in the catalog are stored as relative paths (although they are expanded before being displayed), so the re

Problem: A copy of the Readme file is attached to this article. Resolution: Attachments: Readme for Mainframe Express v3.0 ALL11M30.zip Old KB# 2488#EnterpriseDeveloper#MFDS

Problem: We tried to open the .PDF file included on the Host Connectivity CD, but it will not open. Is this corrupted? Is there anything important on it? Resolution: This is .PDF file but it's not an Adobe file as one might expect. As part of our Microsoft install and SMS support we supply .PDF files that are really Microsoft SMS files and only Microsoft SMS can view/use them. But if you try to view them in Windows, Adobe tries to open them and says it can't. There are several of these files. The one you found, MFA32MSI.PDF in the Setup directory of the Host Connectivity CD. and on the MFE31 CD, we have the ATK32MSI.PDF (for the Administrator Toolkit) and we have the CBP32MSI.PDF for MFEEE itself. Old KB# 2563#EnterpriseDeveloper#MFDS

Problem: How do you export specific data from XDB tables? Resolution: Within the SQL Wizard, select File -> New -> Export, and change the format to dsntiaul. Select the table, and add a where clause as appropriate. This will only export the data which meets the condition specified within the where clause, and will allow the data stored in the output .dsn file to be imported elsewhere. Old KB# 2489#EnterpriseDeveloper#MFDS

Problem: Definition of Paging Commands (Page Previous / Page Next) Resolution: Please define the Paging commands (usually F7/F8) in your SIT as shown in hardcopy attached. Attachments: paging.jpg Old KB# 2450#EnterpriseDeveloper#MFDS