Rocket® Enterprise Suite

Problem: A Panvalet library is not showing up as Panvalet in the Drag & Drop GUI display when double clicking on the name, error 'record format not supported' appears Resolution: Right-click on the name of the Panvalet library select Source Control > Panvalet The 'type' information immediately preceeding the dataset name should now read 'PAN' click on the ' ' to display the list of Panvalet elements Old KB# 2482#MFDS#EnterpriseDeveloper

Problem: Customer is running the Accessing Mainframe Files Sample Session in MFE 3.0: I was able to run the JCL. It completed with a COND CODE 0000. That was good, but the next step in the tutorial says to run it again with the catalog entry removed for the host dataset. Now whenever I run the JCL it errors out with a 139 on record length or Key data inconsistency on OPEN INPUT INQUIRY Resolution: The record length in the COBOL program is 535 bytes, so the LRECL should be 535 4 bytes = 539. The printed material is 534 and the online doc is only 539 in one place (and 534 in another).  If you redo the project with an LRECL of 539 instead of 534 then everything should play both ways. So, when you created the mainframe dataset (in the Uploading and Downloading files chapter) here's what's in the doc: To create a sequential data set: Click Sequential dataset on the Allocate menu. A dialog box appears for you to define the data set y

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: Wenn ich Revolve über das Tools Menü von Mainframe Express starte, wird Version 6.2 ausgeführt und nicht 7.0. Wie kann ich dies ändern? Resolution: Bitte editieren Sie den Eintrag unter HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths\\revolve.exe , so daß er auf die aktuelle Version des Produktes zeigt. Old KB# 2481#MFDS#EnterpriseDeveloper

Problem: In JCL, it is possible to use DCB=AMODEL. as below... //DD1      DD DSN=YR&PHASE..&BUS..AA.&ZONE..YRAA1405.FATERR, //            DISP=(,CATLG,DELETE), //            UNIT=&PACK, //            SPACE=(TRK,(1,1)), //            DCB=AMODEL, //            RECFM=FB, //            LRECL=80 What does this parameter do..? and how can it be used in Mainframe Express..? Resolution: The DCB parameter used as DCB=AMODEL, will create a dataset in the MFE catalog with the same file attributes as a file called AMODEL. For this to work correctly,the file with

Problem: The user wants to convert the catalog path to a relative path. Resolution: Example: Change the directory C:\\mfuser\\projects\\projectname\\data to <CatalogFolder>\\data Old KB# 2505#MFDS#EnterpriseDeveloper

Problem: Cobol Anwendungen nutzen das Tabellensystem TABEX von BOI auf dem Mainframe. Können diese Programme unter Mainframe Express weiterentwickelt und gewartet werden? Resolution: BOI bietet TABEX auch auf anderen Plattformen an, unter anderen auf Windows Plattformen, sodass dann Cobol  Programme TABEX auch auf dieser Plattform aufrufen können. BOI bietet aber auch die Möglichkeit, direkt auf die Mainframen TABEX Daten zuzugreifen. Old KB# 2467#MFDS#EnterpriseDeveloper

Problem: We are trying to use MFA (Mainframe Access) Drag and Drop to transfer files between the host and the PC, but we keep getting this error message: MFDAS01: Mainframe access problem. Reason: Record exceeds internal length limit What is causing this? It was working previously. Resolution: The MFA translation switch being set in the incorrect position can cause this error. With Drag and Drop open, go to its main menu and select 'Configure' then 'Options'. Notice the switch in the upper right hand corner labeled EBCDIC/ASCII Translation. What is not obvious is that regardless of the switch setting when one is downloading PDS members from the host to the PC, we will do the character set translation. In addition, when uploading from a PDS member to a host PDS (if MFA Drag & Drop starts from within the MFE project and the MFE Catalog was expanded to show the projects datasets) we will also do character set translation. However, if a download starts f

Problem: Customer has some large VSAM files that they wish to leave on the mainframe while debugging in MFE. Resolution: Dataconnect offers the ability to access VSAM data files on the mainframe. Another option might be to download a subset of the data file using drag and drop with keyrange filtering. Old KB# 2484#COBOL#Enterprise#ServerExpress#netexpress#MFDS#EnterpriseDeveloper#MainframeExpressandMFE

Problem: open a cobol program. got view -- analysis option and all items are grayed out. Resolution:    Open a project. Goto project-> project settings. Select General tab. Select the Build tab from Project. Check Enable Analysis Option. Optionally, check Automatically Update on Build, to rebuild the analysis option information whenever a Mainframe Express build is done. Old KB# 2490#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: Documentation for Micro Focus products is visible on the web site www.microfocus.com, under Support --> Product Documentation.  It is in HTML form and can be viewed in a web browser. But some customers want to print it out; more than just one page at a time.  How can this be done? Resolution: It is first necessary to login to the Supportline page.  If you don't have a login, call Supportline and request one.  You can find out the phone number for Supportline, for your geographic area, from the website www.microfocus.com.  You need to have a valid serial number with active maintenance. Once logged in, there is an option named "PDF Formats" on the left-hand menu pane, under Documentation, near the bottom.  Click this "PDF Format", then on the next screen, look for the section named "BookShelf - PDF/printable format".  Below this are links to downloadable zip files for each Micro F

Problem: In Mainframe Express you can remap the 3270 keys to mappable keys on the PC keyboard enabling you to choose which key on the PC keyboard will represent a 3270 key.  This means you can define a keyboard layout that is familiar to you, rather than having to learn an unfamiliar one.  You control this remapping with the configuration file, dfh3270.cfg. However, when another user accesses your PC with his/her own USERID, the configuration of these keys is lost because they are linked to the USERID of the original user.  Is it possible to maintain the personalised mapped keys or port them from one user to another? Resolution: This kind of configuration is actually linked to a key in the Windows registry of the machines concerned.  The key can be found in the Ide folder.  To export this go to the registry by running: regedit > HKEY_CURRENT_USER > Software > MicroFocus > Mainframe Express &gt

Problem: On Vista machines with UAC enabled, UAC must be disabled before uninstalling MFEEE 3.1 WrapPack #001 The error shown during the uninstall is a 'Program and Features' dialogue box with "Fatal error during installation".  Clicking OK will close the dialogue box, and stop the uninstall. Resolution: To remove the WrapPack by disabling UAC on Vista: 1. Navigate through Control Panel > User Accounts 2. Select 'Turn User Account Control on or off'.   3. Uncheck the check box and click OK.   N.B. You will have to reboot your machine before uninstalling MFEEE 3.1 WrapPack #001. To remove the WrapPack without turning off UAC (Administrator only): 1.  Ensure you are logged in with Administrator privileges, and open an Administrator command prompt. 2.  Use the following command-line to uninstall the WrapPack, and log the uninstall information to MFE31WS01uninst.log: start /wait msiexec /i {1A0B

Problem: When requesting batch generation of an OX program through DGS, is it posible to make one DGS request to go from APSEXPS to COBOL in one DGS call or do you have to request an APSEXPS -to APSPROG generation then request a second APSPROG to COBOL pass? Resolution: Yes - if you want to generate the APSPROG file as well as the COBOL program you can set your program type to APSEXPSF. Program Type  APSPROG Generate an Online Express or Program Painter program   APSSRC Generate a program coded in APSSRC (not implemented) APSEXPS Generate an APSPROG file from an Online Express program APSEXPSF Creates an APSPROG file from an APSEXPS file and then generates the COBOL program Old KB# 2571#EnterpriseDeveloper#MFDS

Problem: Can a silent install of MFE 3,1 be done, using the MSI installation technology.? Resolution: This information is on the MFEEE CD.  From the README, go to System Administration, then open  SILENT INSTALL To install the base GA MFEEE, you need to run the following statement, or something like it.. (it is assumed that D drive is the CD drive of the machine used for install) d:\\SETUP\\MFEEE\\CBP3260000142.exe /S /V"/QN /L*VX d:\\INSTALL.LOG ADDLOCAL=MFE,MFANSYS,AMB,MFASM,MFCICS,MFIMS,SQL INSTALLDIR=d:\\MFE31 MFUSER=d:\\MFUSER31" ========================================= d:\\SETUP\\MFEEE\\CBP3260000142.exe - is the MSI installation program for MFEEE /S - run in silent mode /V"    "  - parameters used by the MSI installation. The breakdown of the parameters is as follows.... /QN  - start parameter /L*VX - to specify the directory for the install log

Problem: We are getting this error in MFE when trying to compile any program:    Load error : file 'IDELINK_GetDestInt'    error code: 173, pc=0, call=1, seg=0    173     Called program file not found in drive/directory    IDEID1003S Non-zero return code from compiler. We also have Net Express and it fails with: Rebuilding         C:\\Documents and Settings\\My Documents\\Micro Focus\\Net Express 5.0\\WORKAREA\\mypgm.cbl COBCH0916S Internal error - Error opening cdi2 handle.  : "C:\\Documents and Settings\\My Documents\\Micro Focus\\Net Express 5.0\\WORKAREA\\mypgm.cbl"(56,7) Rebuild complete with errors What is wrong? This used to work. Resolution: The IDELINK.DLL module exists only in Mainframe Express. Somewhere in the environment there is another module being picked incorrectly. We have see

Problem: We are debugging an application and as we step on a CALL to a sub-program, we get an access violation error. The MFDEBUG.LOG file created shows a RTS114 error and points to a Micro Focus module, CBLINTS.DLL. Do you have any ideas what might have happened? Resolution: We have had a few RTS114 errors (abends) reported in this module as one issues a CALL to a sub-program. One was caused by bad data in a Cobol program. That customer had used cut and paste of non-display fields from the mainframe to MFE (ascii/ebcdic) and the mainframe fields contained invalid data. Another had an Oracle database that was corrupted. Although Mainframe Express does not support Oracle, Sybase and Informix databases, they are mentioned here because this error has also been reported using the Net Express product as well. As a testing method to isolate a bad INT/IDY, one can use a standalone test to see if the sub-program can be displayed in the debugger (or Animator). In MFE,

Problem: Is Borland StarTeam Software Change & Configuration Management tool is integrated with MFE 3.0 in order to do Check In and Check Out file actions,as with Serena PVCS. Resolution: When the Borland Star Team software is installed, MFE should recognise that an SCC is installed from the registry entries it creates, and the source control menu will become active in MFE. Micro Focus do not claim to work with all SCC systems, however, if the package being used is SCCI ( Microsoft Source Control Common Interface ) compliant, then it should interact with MFE without problems. Old KB# 2496#EnterpriseDeveloper#MFDS

Problem: Message is Could not stop the Micro Focus XDB Server for MFE 3.1 service on Local Computer Error 5: Access is denied Resolution: Error 5 is a Windows error; it is an "Access Denied".   The user you log in as needs to have the privilege to stop and start the server as a Service. Old KB# 2569#EnterpriseDeveloper#MFDS

Problem: The Feed_Back Condition code for LE services accepted but not supported is 4. This causes any user application which aborts on a non-zero FC to fail. Resolution: The work around here is to provide a COBOL stub for the CEE routine in question.  In order to get this stub to load ahead of the system LE callable services process, the user needs to use MFPRELOAD. This process is documented in Supplementary Information in the Mainframe Express Readme... Preloading System Files ---------------------------- When you debug or execute an application under CICS, JCL, IMS or TSO, whenever Mainframe Express needs to load certain system files it searches the path used by your application before it searches its own system path. If your application's path specifies a number of different folders, especially folders on remote machines, significant time delays can occur when Mainframe Express searches for some system files. A new system utility, MFPreloa

Problem: The CICS master terminal command CEMT is disabled in Mainframe Express and Enterprise Server. Is this command supposed to be available?   Resolution: Micro Focus cannot use CEMT by agreement with IBM.   Instead, there is CPMT for programs ------------------------------------------------------------------------------------------------------- CPMT - Inquire and Set Program Attributes Displays the current attributes of the specified program for an inquire, and sets the specified program attribute. Syntax: CPMT function program-name Notes: The function is specified as one of: CEdf NOcedf NEwcopy PHasein DPlsubset FUllapi PRivate SHared ENabled DIsabled INquire NAme-inquire For each function except INquire and NAme-inquire, CPMT issues an EXEC CICS SET PROGRAM command for the corresponding system programming API keyword. For the INquire function, CPMT issues an EXEC CICS INQUIRE PROGRAM

Problem: Is there any documentation for Filter Expressions in the SyncMon Advanced Filter Database? Resolution: From Syncmon, go to Configure > Advanced Filter Database > Add >  Help to get a detailed description of the filters. Advanced filter details. The Advanced filter database contains filter rules that can be strung together during the option configuration process. These filters can include and exclude files during the transfer process. The database is held in text format in file called monrule.ini. Rule Name - The name that the rule will be known by. The only restriction on this field is that it cannot contain spaces. Rule Description - Free format field containing a meaningful description of the rule. This description is displayed during the selection of rules during the oprions configuration process. Rule - A free format field containing the rule expression. The rule itself is called a "regular expression". The syntax is s

Problem: We downloaded our host IMS Stage1 definitions, but when trying to load the IMS definitions into Mainframe Express we get NO records loaded. We have valid PSB,  DBD and MFS gens but when producing the extract file of transactions from the download to generate the .DAT, we saw this in the IMS log tab output window    07.08.29/12:07:11 Extracting transactions from a STAGE1 file                    07.08.29/12:07:11 Number of Definitions extracted:                             07.08.29          BMP  : 00000. 07.08.29          QBMP : 00000. 07.08.29         &nbs

Problem: and we are trying to get XDBLINK bind to work and getting error message that XDBCFG2.XDB cannot be opened is there any way I can call you and get this resolved? Resolution: This file is in the mfuser\\config directory and it sounds like permissions may be set up incorrectly.  You need to be able to write to this file during the Link process. Check this by going to the mfuser\\config at the command line and run Attrib This will show the file attributes and if this is read only, there's your problem. Also, if this is running on a network drive and you are running the XDB Server as a Service you need to change the Control Panel - Administrative Tools - Services - Log On tab from the Local System to a real network account that uses the XDB Server or you will get this message as well. Old KB# 2491#EnterpriseDeveloper#MFDS