Rocket® Enterprise Suite

Created On:  02 July 2012 Problem: While building a customer IMS/CBl/ASM Mainframe Express application into Enterprise Developer for Visual Studio, the following error is displayed and the build fails: ********************************************MM370ANM  Micro Focus Assembler Option Debugger                                                                                                                 &n

Created On:  29 June 2012 Problem: This article applies to Enterprise Server 2.0 on Windows Server 2008 and Windows 7 systems.The Fileshare Service can be started manually, but when it is set to start automatically upon reboot, it does not happen. It can be started manually after reboot with no problems and no errors. Checking the system's Event Viewer, this is seen: A timeout was reached (30000 milliseconds) while waiting for the Micro Focus Fileshare Service: FSSRV service to connect. The Micro Focus Fileshare Service: FSSRV service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. What can be done to have the Fileshare service start automatically upon reboot? Resolution: On Windows, right-click on the Task Bar located at the bottom of the Desktop.  Select "Start Task Manager". Select the Services tab. then double-click the Services button at the lower-right-hand corner. A list of the services

Created On:  20 June 2012 Problem: The following error message was displayed when a user tried to open a Mainframe Express project that had been created by another user on a different machine: The specified catalog is not the proper version. Use project settings to correct the catalog name or location. Resolution: The project had been created using the most recent version of Mainframe Express 3.1, but the user trying to open it was running an older version of the product. The problem was resolved when the user applied the latest Mainframe Express WrapPack. Incident #2575659 Old KB# 36024#MFDS#EnterpriseDeveloper

Created On:  18 May 2012 Problem: After starting Visual Studio, I cannot see the Enterprise Server Regions in Server Explorer to be able to connect to.  Additionally, the Micro Focus Servers heading is not displayed either. Resolution: This is a problem that occurs when the installation of MicroFocus Studio 6 does not always quite work correctly after installing Microsoft Visual Studio.  To correct this open a Net Express command window.  Change directory to Visual Studios IDE directory, on Windows 7 the default is "C:\\Program Files (x86)\\Microsoft Visual Studio 9.0\\Common7\\IDE\\".Next type devenv.exe /resetskippkgs, this will start Visual Studio and correct the error. Old KB# 35955#VisualStudio#serverexplorer#EnterpriseDeveloper#MFDS

Created On:  04 May 2012 Problem: When you create a table with a record length greater than 4000 bytes you get the error: X139: Record size exceeds the maximum Resolution: The problem here is not the length of the field, but the size of the page which in this casemeans that you have exceeded the size of the page 4,000 bytes. The table is obviously greater than 4000 bytes so creating a tablespace with a buffer pool which is greater will solve the problem. To do this you will need to create a tablespace for a bigger buffer: CREATE TABLESPACE TSPC32K BUFFERPOOL BP32K; You can then go on to test this by creating a test table (or even your own table) by including the IN TSPC32K; in your create table statement: CREATE TABLE TEST ( F1  CHAR (254),  F20  VARCHAR (6000))IN TSPC32K; Incident #2570511 Old KB# 35929#EnterpriseDeveloper#COBOL#MFDS

Created On:  01 May 2012 Problem: In our client's production environment, they want to disable the ESMAC CONTROL JCL Submit function for a series of users. However, they also have a CICS application (TSO CLIST replacement) that submits JCL to the INTRDR via a CASSUB command. They want the same set of users that don't have ESMAC CONTROL JES submission authority to have CASSUB authority for the CICS application. How do we configure the security for this type of environment? Resolution: To allow users to issue the cassub command or API and not submit via the JES SUBMIT button, set the CN=cassub,CN=OPERCMDS,CN=Enterprise Server Resources to read access. Incident #2565214 Old KB# 35922#EnterpriseServer#Enterprise#Server

Created On:  24 April 2012 Problem: I have a COBOL program which is trying to create an indexed file. I named the file: xyz.dat, but when the COBOL program runs it creates a xyz.dat file and a second file with an extension of IDX named xyz.dat.idx but on my other machine it is as expected; the filenames are xyz.dat and xyz.idx, not xyz.dat.idx. What is causing this? Resolution: In our case we had two environments. One worked, one failed. When creating an Indexed file the index name was being created as xyz.dat.idx when it failed, but in the working environment the new file was named xyz.idx.  The answer is to use an EXTFH.CFG with the option of IDXNAMETYPE=0. The working environment was checked and it did use an EXTFH.CFG file with IDXNAMETYPE=0 but the failing environment did not have an EXTFH.CFG file.  Also, the REBUILD utility gave the same results. This is because REBUILD, like the Cobol program, has its I/O request processed by the Micro Focus File

Created On:  24 April 2012 Problem:  We are getting compiler errors when using a dialect of Enterprise COBOL in a Report Writer program. We are seeing these error messages: 'COBCH0501S Feature is part of an optional module - Report Writer' and 'COBCH0502S This entire section is part of an optional module - Report Writer'.  Is there a means past these errors? Resolution: This can be accomplished by one of two means:  - use a dialect of entcobol and add the directive:      changemessage(0287 w 501 w 502w)  - use the translated output from the PC Report Writer    vendor, usually it is from www.spc-systems.com Please bear in mind that the IBM OS/VS COBOL Compiler provides support for Report Writer that is based on the ANSI68 COBOL Standard even when the mainframe compiler option of LANGLVL(2) was used - which normally requests ANSI74 support. But there are many cases in which the IBM Compiler actually supports a cross between

Created On:  25 April 2012 Problem: When building programs in Visual COBOL 2.0 or Enterprise Developer 2.0 you may see an error due to an invalid value for COBOLDir parameter. The error would look similar to: C:\\Program Files\\MSBuild\\Micro Focus\\Visual COBOL\\v1.0\\MicroFocus.COBOL.targets(253,13): error MSB4030: "C:\\Program Files\\Micro Focus\\Enterprise Developer" is an invalid value for the "COBOLDir" parameter of the "COBOL" task. The "COBOLDir" parameter is of type "System.Boolean". [C:\\TestClient\\work\\P578421_20120317040115898\\p578421\\Cobol\\Cobol.cblproj] Resolution: Cause: Visual COBOL and Enterprise Developer use a new COBOLDIR parameter, and this is conflicting with an Environment Variable of the same name, that you may have set. The conflict occurs because the Environment Variable you set is a string and the Parameter in the Product is Boolean based. Resolution: Is to unset your COBOLDIR Environment Variable, or Choose a different name for your COB

Created On:  24 April 2012 Problem:  We are using dfconv to convert files from EBCDIC to ASCII. After the dfconv conversion, characters inside the ASCII range are stored in 1 byte, but characters outside the ASCII range are stored in 2 bytes, e.g. hex 00 gives 00 00 but 41 gives 41 ('A'). This often happens for COMP fields in our data files. We are using a structure file when doing the conversion. Why does dfconv use 1 byte for valid ASCII characters and 2 bytes for anything else? Resolution: From a command line (either Mainframe Express, Net Express or Studio), use these commands:       set cobsw=-n       run dfconv profilename inputfile outputfile This runtime switch will remain active for the duration of the Command Prompt session you are using. By default, Micro Focus will add an extra x'00' to hexadecimal values lower than x'1F'. By setting the -n switch the extra x'00' is not added to the file. Incident #21

Created On:  16 April 2012 Problem: Can XDB  support a 2TB db for testing? Resolution: That seems a bit large; 2TB is larger than necessary for testing. XDB can support a maximum table size of 200GB. If they won’t exceed that, they are welcome to try. However, a 2TB location would seem to imply a production RDBMS. I would recommend against using XDB in that scenario. Incident #2569384 Old KB# 35824#MFDS#COBOL#EnterpriseDeveloper

Created On:  04 April 2012 Problem: After adding new items in the configuration, they are not able to be added to or used in the workspace. Resolution: Always upgrade the workspace after making changes to the configuration, this should enable use of the features added to the configuration. Incident #2554842 Old KB# 35754#Workspace#SupportTip#configuration#EnterpriseAnalyzer

Created On:  03 March 2012 Problem: At the end of the Modernization Workbench installation process, a run-time error 53 is encountered, with the message that RntServ.dll could not be found. Resolution: Use setup.exe by right-clicking on it and selecting "Run as Administrator" if using Windows Vista/7/Server 2008 or by simply double-clicking on it for older versions of Windows.This problem is caused by trying to run the MW.msi file instead of setup.exe to install Modernization Workbench. Incident #2567405 Old KB# 35750#SupportTip#Installation#install#Run-timeError53#MW.msi#EnterpriseAnalyzer#RntServ.dll

Created On:  11 April 2012 Problem: When trying to open a workspace or create a new workspace the ORA – 12514 TNS:Listerner does not currently know of service requested in connect descriptor error is sometimes reported. Resolution: The problem is that the Oracle client and server are using different service names. The simplest thing is to change the service name used by the client to match the one defined at the server. To find out the name of the service on the server, based on the standard MWB Oracle install, run the following command from a command prompt: lsnrctl status On windows this displays the following information: LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 05-APR-2012 11:02:33 Copyright (c) 1991, 2010, Oracle.  All rights reserved.   Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521))) STATUS of the LISTENER ------------------------ Alias             &n

Created On:  13 April 2012 Problem: When installaing the Oracle provided with the Workgroup and Desktop Editions on Windows 7, Server 2008, or Vista, Error 1720 is recieved as the installation finishes. Resolution: This error is generally caused by not right-clicking on the installer and selecting "Run as Administrator" even when using an account with administrative privileges. Incident #2551728 Old KB# 35809#SupportTip#Oracle#EnterpriseAnalyzer#ODBC#Error1720

Created On:  13 April 2012 Problem: Running XDB compacting works in the command line, but when scheduled to run in Windows Scheduler, it hangs and does not finish. Resolution: When starting the XDB server under control of the task scheduler, by default, the task scheduler gives the XDB server a background process priority. This is not the case in Windows 7, so this needs to be changed. In order to create a compact backup using the task scheduler in Windows 7 follow these steps: 1. Create the task2. Right click on the task and "export" it3. Edit task.xml that you just exported4. You will find a line similar to 75. Change the value to a normal priority (between 4-6). A table of potential values are here6. In the task scheduler, delete the task you initially created7. In the task scheduler, in the action area, import the task from the XML file Incident #2542195 Old KB# 35813#COBOL#EnterpriseDeveloper#MFDS

Created On:  30 March 2012 Problem: Under certain circumstances, when upgrading an MW 3.2 workspace, an error is received during the upgrade process relating to the PBAttribute table. Resolution: Be sure that you are using HF10 or higher for MW 3.2.  The latest is always available on the "Product Updates" page on the SupportLine website. Incident #2543789 Old KB# 35741#Workspace#Upgrade#EnterpriseAnalyzer#PBAttribute#SupportTip

Created On:  12 April 2012 Problem: I have a COBOL program that will read a copybook and then generate statements for a new program. I need to read the copybook that is used by both this program and a normal compile. How do I code JCL statements for local PC file instead of the catalog in my project? I do not want to keep two source files, one in ASCII and another in EBCDIC. Resolution: We do allow you to keep one copy of your copybooks in ASCII in a PC directory yet access them for compiles or JCL jobs using either character set.   The latest maintenance levels of MFE and Studio will do character set translation on the fly for a PDS. So one can use a PDS in the MFE or Studio Catalog as a repository of source files or control cards for SORT, IDCAMS, SQL, etc. and depending on the character set of the program issuing the OPEN, our File Handler will present the file in its native character set meaning you can reference the PDS from JCL and the physical PC directory

Created On:  04 April 2012 Problem: Can the license server for legacy products (like Net Express 5.1) and the license management server for Studio 6.0 products co-exist on the same box?How is it managed and configured for what appears to be 2 distinct licensing products on a centralized license server? Resolution: To achieve this you should do the following: Net Express uses URK type licensing and has its own License Server. Please be aware that this is now a very old product and special steps need to be taken when installing on more recent operating systems such as Windows Server 2003 and Windows Server 2008 (notably IIS settings). License Server 4.0 is only available for Windows platforms. It is activated by the installation of a Response Key on the back of the customer generating a Request Key. Studio Enterprise Edition uses SafeNet licensing. When you install this product you always automatically install the license manager which acts as a local license management tool.

Created On:  30 March 2012 Problem: User wishes to know the difference between a locked object and a dead object on the HyperCode Convertor queue for Modernization Workbench. Resolution: Locked records means the HCC ran into errors while processing the particular object.  In this case, the error probably resides with the file itself. Dead records means the HCC failed in the middle of processing an object.  This can happen if the tool crashes, or the connection to the database is lost during the processing.  In this case, the error likely resides in the environment. In either case, the recommendation is to delete the locked/dead entries from the Queue and then re-verify them in order to place back into the Queue for processing by the HCC. Incident #2566868 Old KB# 35740#SupportTip#EnterpriseAnalyzer

Created On:  13 April 2012 Problem: User receives error message when attempting to perform any query into the database of a Modernization Workbench.  Some actions are Clipper query or Apply Filter from Change Analyzer.  Error message is:Run-Time error IBM CLI DRIVER DB2 SQL The result of a sclaer fullselect, SELECT INFO statement, or VALUES INTO statement is more than one row: SQLSTATE 21000 Resolution: Message is related to duplicate rows in the SQL database.  Running "Cleanup HCSources Table" from the Modernization Workbench Administration window will resolve the issue. Incident #2558856 Old KB# 35811#SupportTip#EnterpriseAnalyzer

Created On:  30 March 2012 Problem: The screen to start a JES region comes up with "currently logged-on administration user" as the default startup UserID. When shutting down, this caused invalid password attempts for the user trying to log on, causing microfocus-MFDS-User-LoginAttempts to exceed the alotted number and suspending the logon (microfocus-MFDS-User-AllowLogon=FALSE) due to excessive invalid password attempts (signon attempts=6), leaving user unable to log on. Resolution: Set the  "MFDS_SYSTEM_USER" environment variable to "Y" before Starting MFDS. The MFDS_SYSTEM_USER needs to be set before Starting MFDS for this to work, it cannot be set in the region configuration area.Then the default Enterprise Server credentials selected by the GUI for Enterprise Server instance start and stop requests is "default #System group user" (instead of "currently logged-on administration user").This was changed in MFDS 1.14.04 onwards. ex. "MFDS_SYSTEM_USER = Y Incident #25

Created On:  30 March 2012 Problem: I have /IMS set as default tran for when a terminal connects. When I connect I get a violation that CICSUSER can't run /IMS./IMS is under Enterprise Server Resources > TCICSTRN with deny:*:execute; allow:ALLUSER group:read.Under Enterprise Server User Groups, ALLUSER lists SAFU, PLTIUSR, mfuser, CICSUSER and SYSAD as members.CICSUSER is found under Enterprise Server Users. Do I need to add him to ADAM Users or fully qualify him under Enterprise Server Groups? Resolution: The short answer is "no."This an IMS only system (as in no CICS) and the  Init Tran in the SIT set to /IMS. When a 3270 connects it fails with CICSUSER not permitted to run/IMS.Change the definition of /IMS in the RDT to a "Cat3" (like CESN). You will no longer get the error message. Incident #2532715 Old KB# 35736#Enterprise#Server#EnterpriseServer

Created On:  26 March 2012 Problem: User attempts to use Include Referenced operation on objects to create new Project.  User does not receive any results and no objects are included into the new Project. Resolution: For "include" objects such as copybooks, DDLs, and JCL procedure files, Include Referencing needs to be used, rather than Include Referenced.  Include Referencing will include the objects that include the seed objects and return results.  Include Referenced should be used for seed objects like Programs. Incident #2558647 Old KB# 35691#EnterpriseAnalyzer#SupportTip

Created On:  26 March 2012 Problem: When the configuration program "srvc40n" is used to configure XDB Server, it's impossible to choose DB2 V9.  The error reported is: Invalid value DB2V9 for option EngineOptions.DB2Version Resolution: Instead of using:srvc40n EngineOptions.DB2Version=DB2V9 Instead use: srvcmfe EngineOptions.DB2Version=DB2V9 srvc40n is an old executable not used for DB2 V9. Incident #2553204 Old KB# 35689#MFDS#EnterpriseDeveloper