Rocket® Enterprise Suite

Problem: If your DBA is providing DCLGEN copylib members and placing them in the program group copylib folder, these members can be overlaid when a subschema is generated that has the same copylib name in use. Resolution: To allow the subschema to be regenerated without overriding the existing copylib members, a new field has been added to the AMB options. You can redirect the copylib files to another folder and thus not override the ones provided by the DBA. To set this, go to the options, user preferences, environment tab and locate the  Alternate SQL copylib path field and put a temporary folder name. Old KB# 2879#MFDS#EnterpriseDeveloper

Problem: MFA can be configured to automatically drag any copylib members for COBOL programs and samples are provided. Do you have any examples of how to do this for AMB program syntax? Resolution: These samples are specific to APSPROG members and should not negitively impact the way COBOL members are parsed because COBOL would not have any APS keywords. This is for all includes. [0-9\\t ]*\\COPYLIB[\\t '("]*([A-Z0-9]*) COPY; This is for all copy commands. [0-9\\t ]*\\COPY[\\t '("]*([A-Z0-9]*) %INCLUDEs not on the same line; This is for includes on the same line as the WS01. ^[0-9\\t ]*\\%INCLUDE COPYLIB[\\t '("]*([A-Z0-9]*) %INCLUDEs on the same line; This is for includes on the line after the WS01. ^[0-9A-Z\\t .]*\\%INCLUDE COPYLIB[\\t '("]*([A-Z0-9]*) APSDATA DS This is for  APSDATA members with DS in column 4 ^[A-Z\\t .]*\\DS  [\\t '("]*([A-Z0-9]*) APSDATA DS## This is for  APSDATA members with DS## i

Problem: Synchronisation monitor within MFA (Drag & Drop) can be used to download 2 unique PDS's on the mainframe into 1 unique PC directory. When ALLOW WORKSTATION DELETES is used, the first PDS download will complete successfully, placing all members into the PC directory.   When the second download starts, all of the members downloaded by the first download will be deleted from the PC directory before the members from the second PDS are processed. Is there a way to use the same folder to download two partitioned dataset with the option ALLOW WORKSTATION DELETES? Resolution: To workaround this, set an environement variable SET MFDA_NODELETE_FOREIGN=Y before running syncmon, to stop syncmon deleting files in a directory that are not referenced in the current step. This allows separate steps to sync to a common PC directory, but will not delete any files that are not referenced in any of the steps ( e.g. that are copied there

Problem: I have a question about the DGSLOG.txt that gets created out of AMB.  Our production DGS log appears to randomly "purge" itself.  One minute it will be 100k in size and then suddenly it is 5k in size and the oldest message written out there is about 5 minutes old. The DGS service itself is not being restarted. The log just randomly contains truncated information. I'm just wondering if we have a setting incorrectly set up on our log. Resolution: New features have been added to the DGS server configuration. The size, location, backup location for the DGS log file is set from the Options/Distributed Generation Server Options menu. If a size limit and backup is not specified, the DGS log file will automatically be purged and resized. Old KB# 2882#EnterpriseDeveloper#MFDS

Problem: Customer has the XDB Server started but can not connec tusing SQLWizard.  Get the error XU005:  which can either say unable to get error code or filename not found. Resolution: This problem usually occurs because there is more than one xdb.ini file and the one being used is not pointing to the correct paths for the product. Old KB# 2627#EnterpriseDeveloper#MFDS

Problem: The AMB How TO Help document states: TO LOAD AND BUILD A SQL SCHEMA INTO A DATABASE VIEW 1. Copy the SQL DDL sources that contain the tables you want to reference in your SQL schema to the SQLDDL directory of your project/group. Does this mean that the DDI process in AMB does not reference the Work Group? Resolution: The Database View does support workgroups. The documentation points out that your DDI sources need to be in the current AMB project location if you intend to edit them. However, you can also include or browse sources from other DDI locations that you set up in your workgroup. Once a workgroup is set up, you will see the additional paths in the pulldown provided in the database view edit panel. Old KB# 2601#MFDS#EnterpriseDeveloper

Problem: The statement in a macro is labeled as invalid:   ACTR  10000 The current limit for the number of macro instructions has been exceeded. The macro generation statement   ACTR  nnnnn allows to raise the limit of macro instructions above the default of 4096. ACTR is a security limit, in order to avoid loops caused by  .AGO and .IF Resolution: Any ACTR limit fitting into 32 bit will be accepted by the Assembler. However, if the default limit of 4096 is actually exceeded, the ACTR error message is issued. The .IF macro statement must be changed, so that no more loops than 4096 are executed. Old KB# 2610#MFDS#EnterpriseDeveloper

Problem: This was available in MFE 2.5 and MFE 3.0 Resolution: The file CREATENV.BAT in ..\\BASE\\BIN shows how the environment is set for the MFE command prompt. The programs CBLPROMP.EXE and XDBPROMP.EXE have replaced MFEENV.EXE but they essentially do the same job so just change to use the new programs. Old KB# 2603#EnterpriseDeveloper#MFDS

Problem: In this case customer was using special characters in DFHDMF label names and was getting errors, like: BMSCH1011E Unexpected scanning error on öKTKE  DFHMDF POS=(1,46),LENGTH=26,JUSTIFY=(LEFT,BLANK),ATTRB=(ASKIP,* BMSCH1014E Unexpected verb ERROR_TOKEN found, remainder of macro discarded : C:\\mfuser\\BMSbug\\Source\\MS992.BMS(15) Resolution: By default BMS compiler rejects special characters in DFHDMF definitions like ö or ä, for example MSöKTKE  DFHMDF POS=.... If you are using such characters in the BMS macro, you must use the additional BMS directive NAMES in order to allow these characters. For example: /NAMES=öä ....  and the BMS will be compiled without errors. This is the according extract from Online Help: NAMES Specifies additional NLS (National Locale Support) characters that are to be allowed in macro labels. Syntax: >>--/----NAMES=nls-characters------------->< Parameters:

Problem: A query from UDB tables may issue a wrong sort sequence, if characters and digits are involved in the order by column. Alphanumeric values are ordered in the ASCII collating sequence, digits before letters. The ordering does not correspond with host DB2 data retrieved by UDB DB2 Connect. Resolution: The collating sequence can be specified while creating a UDB location with HCO Create Database. The collating sequence must be set to MFE = EBCDIC in Options - Codepage - Mainframe Express. Old KB# 2607#MFDS#EnterpriseDeveloper

Problem: When I select debug, start debugging, select CICS, then enter the transaction code, the application output window comes up without my CICS map. If I try to enter the transaction, the message appears in the window: " TXKC0000E Invalid transaction ID, please re-submit". And the following messages appear: TXSE0009I Region is running with Resource security disabled. 14:41:19 TXSI1719I Loading single process system 3270 support (Ver TX 3.0.00) 14:41:19 TXSI9009I Debug initialization for ALL successful 14:41:19 TXSI1738I Assembler Option support loaded successfully 14:41:19 TXSI1600I Server initialization completed successfully 14:41:19 TXSI5001I PLTPI - No PLT Specified 14:41:19 I was able to do this before I got ghosted and had to reinstall. I did rebuild my project without any problem. Also I imported my Resource Definition File. Any ideas on how to correct or what is happening? Resolution: This can happen if the group containing your trans

Problem: Can we use MFTSO.EXE in a batch file to run a CLIST? We can use MFJCL.EXE for batch JCL submission, but can not find a way to do this for TSO. Here is the syntax for running our JCL:    MFJCL.exe c:\\mfeprojs\\RSO\\RSOXKE.JCL  /submit We have included the CLIST contents and the commands we tried. Resolution:   The supplied documentation for this question included a MFDAS IMPORT BINARY Command followed by a MFTSO.EXE command naming a CLIST (.TSO extension) as the parameter for MFTSO. The .TSO file contained the DB2 DSN RUN command naming a database and a program to run.     The correct method is to use MFJCL.EXE from a command line (.bat file). If one goes to the Mainframe Express Command Prompt, then types:   mftso    a DOS Window asking for a userid is presented. It will then start a live TSO session in Mainframe Express. The MFTSO interface is not d

Problem: The source has been newly compiled, and Debug JCL started. The load libraries are including only one folder. This folder contains new .int and .idy as just created. Resolution: The compilation outputs .int and .idy have been deleted. Removed the source from the project, and added it again. This solved the problem, without affecting any other module. Old KB# 2611#COBOL#MFDS#ServerExpress#netexpress#EnterpriseDeveloper#Enterprise#MainframeExpressandMFE

Problem: An Entry point is not found when a PL/I program calls subroutine. The PL/1 program is executed from JCL: PGM01.pli calls PLIPROG calls entry point ENTPROG in assembler program ASMPROG. Returns: 173, ENTPROG not in found... MFENTMAP (in <ProjectFolder>\\LOADLIB: [ENTRY-POINT]  ENTPROG      [PROGRAM-NAME]  PLIPROG      [SUBPROGRAM-NAME]  ASMPROG Resolution: The solution is: tick in project settings: Search mfentmat.dat before file system Then the Assembler entry ENTPROG is successfully invoked. Old KB# 2613#MFDS#EnterpriseDeveloper

Problem: In this case customer installed Mainframe Express (MFE) under VMWARE emulating XP Operating system. Resolution: This issue was resloved after installation of latest MFE Websync. Please ensure to have the latest Fixpacks installed. Old KB# 2597#MFDS#EnterpriseDeveloper

Problem: The following error has occured X120: Cannot find location name in SYSXDB.SYSLOCALS table. An attempt was made to perform an operation on a location not found in the SYSXDB.SYSLOCALS table. Check the location path or location name specified in your command. When a location is created using the CREATE LOCATION command, an entry is inserted into the SYSXDB.SYSLOCALS table. If you are using a location that was not created with the CREATE LOCATION command, you may use the INSERT command to insert a record into the SYSXDB.SYSLOCALS table for the location. Resolution: This is because there is a mismatch between SYSTABLES and SYSLOCALS Please do the following: File>New>sql In the SQL type the following: SELECT * FROM SYSTEM.SYSXDB.SYSLOCALS; Scroll to the left and look for the column DBPATH.  This is where the log files will be kept. What you are going to want to do first is go to control panel > xdb server and shut down

Problem: Does "zeroload" work on remote mainframe IMS databases ? Resolution: The simple answer is no. The functionality of the IMSDBU "zeroload" does not work against remote mainframe IMS databases. It was designed to work only on the local IMS databases. Old KB# 2646#EnterpriseDeveloper#MFDS

Problem: What is the quickest way to import a PC text file to the MFE Catalog to be used by my programs? We currently allocate a new dataset in the MFE Catalog and then use Cut and Paste. Resolution:   You have several choices on how to place an ASCII Text file into the Mainframe Express Catalog. - Allocate a dataset then copy/paste it as you have done previously.    This works for both a QSAM dataset or for a PDS member.    - Use the Data File Converter to copy a .txt file into a Catalogued dataset - Create the PC file then make a Catalog entry pointing to that PC file The easiest means for you is probably to create your text file (using Windows Notepad or the MFE IDE Editor), then Allocate it in the MFE Catalog. To do this, follow these steps: - Create the ASCII text file - Go into your MFE project, in the Project View window select the    'Catalog' tab - Right-click in a blank a

Problem: Abend 999 in A2TABL with Serena Changeman product interface to APS. Resolution: Serena will need to supply older versions of their code to allow interface to work. Old KB# 2614#MFDS#EnterpriseDeveloper

Problem: When trying to access mainframe locations using SQLWizard or Migrate, users can invalidate their mainframe userid by trying to log on with a bad password 3 times in a row.   This can be resolved by using Global Security in the SQL Option Server. Resolution: Abstract The Micro Focus SQL Option Server provides access to data residing in z/OS DB2 regions and local SQL Option locations.  A valid z/OS user ID and password are required for access to z/OS DB2 regions.  Ideally, a single user ID and password should be used for access the SQL Option Server whether accessing z/OS DB2 regions or local SQL Option locations. The maintenance of the security information on the SQL Option Server should be minimized as much as possible.  When the password changes on the z/OS environment, the SQL Option Server should immediately accept the new password.  Users denied access to the z/OS environment should also be denie

Problem: We are running a host application and get a runtime error of 173 'program not found' looking for IGZEDT4. Is there a Mainframe Express equivalent? Resolution: This IBM Runtime module (from VS Cobol II but carried on in LE) can be emulated by using a PC version of the IGZEDT4 function. These programs illustrate such an implementation:        Identification Division.        Program-Id.  GETY2K.        Author. Lorince        Y2K? Because Centuries Happen!        Environment Division.        Data Division.        Working-Storage Section.        1   CurrentY2K-Date   Pic 9(8).        Procedur

Problem: - SQL Target   (Defaults to HCO) - Allow Mixed Case   (Defaults to Yes) - Generate Redefines   (Defaults to Yes) How can I change the defaults so our desired values are always used. Resolution: This can be coded right in the skeleton.  Assuming you have one set of options you'd like to enforce for all? Probably XBD, NO, NO? A suggestion would be to edit the SSMDDG member in the ISPSLIB folder and do a VSET for the values you want. For example:       #VGET  $SSMREDEF     SSMREDEF       #VSET  $SSMREDEF     NO Doing the VSET right after the VGET will force the NO value for the redefines regardless of the value in the properties panel set by the end user. Old KB# 2615#MFDS#EnterpriseDeveloper

Problem: MFE requires the DBDs have extensions of DBD and the PSBs have extensions of PSB. AMB doesn't have  any problem with PSBs having extensions, but AMB does not use the DDI if the DBDs have extensions of DBD. We would like an enhancement to allow AMB to process properly using DBDs with extensions. Resolution: When DBD members are migrated from the mainframe to AMB on the PC the DBD members will not contain an extension. This causes usabilty issues when attempting to use the DBD files in MFE because MFE expects an extension of .DBD. This limit has been removed in the AMB product and the enhancement will be available in MFE-EE fixpack 03. Old KB# 2618#MFDS#EnterpriseDeveloper

Problem: Customer whom is setting up MFE 3.1 on a machine and noticed a few file changes. We noticed that mfeenv.exe was not located in the bin director though was in the 3.0 bin. Resolution: mfeenv.exe has been replaced by cblpromp.exe and xdbpromp.exe. If modifying the file that was created by mfeenv.exe then the same can be created by cblpromp.exe and xdbpromp.exe. Old KB# 2632#EnterpriseDeveloper#MFDS

Problem: On http://publibfi.boulder.ibm.com/cgi-bin/bookmgr/handheld/BOOKS/IGYPG202/2.3.3.49.2?SHELF=&DT=19980323044041&CASE= you can find a detailled description of TRUNC Compiler directive on Mainframe. What are the according parameters in Mainframe Express ? Resolution: MFE                             Mainframe NOTRUNC                   TRUNC(BIN) TRUNC                        TRUNC(OPT) TRUNC"ANSII"             TRUNC(STD) Old KB# 2622#EnterpriseDeveloper#MFDS