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, MFPreload, has been introduced to remove these delays.

MFPreload enables you to force Mainframe Express to preload a number of system files by using configuration (.cfg) files to specify the programs' location. Removing the need for Mainframe Express to search for these programs significantly speeds up the programs' initial load times.

How MFPreload Works

----------------------------

When MFPreload is in effect, preloading is used for the following system files:

dfhecicg.exe

mftso.exe

mfims.exe

mfjcl.exe

mfjclw.exe

mfjxe00.gnt

For each of these system files there is a corresponding .cfg file. In most cases the .cfg file has the same basename as the system file. The exception to this is dfhecicg.exe, whose .cfg file is mvsecicg.cfg.

When Mainframe Express starts with preloading enabled, it reads the .cfg files to establish the locations of the system files, and when the system files are required Mainframe Express loads them from the locations specified in the .cfg files without the need for search paths.

The ..cfg files are installed by Mainframe Express into \\mfe\\mfide\\bin by default.

Enabling MFPreload

-----------------------

To enable MFPreload for dfhecicg.exe, mfims.exe, mftso.exe, mfjcl.exe, mfjclw.exe and mfjxe00.gnt you set the MFPRELOAD_USE environment variable to any value.

Specifying the Location of the .cfg Files

To specify the location of the .cfg files you use the MFPRELOAD_CFG_FOLDER environment variable. The .cfg files are installed into drive:\\mfe\\mfide\\bin by default, so you should set MFPRELOAD_CFG_FOLDER to specify this folder.

Writing a Log File

---------------------

If you were experiencing time delays due to search paths containing folders on remote machines, configuring Mainframe Express to use MFPreload should result in an immediate significant improvement in performance. If you have enabled MFPreload and do not see an improvement in performance you can create a log file to help you establish where the problem lies.

To create an MFPreload log file you specify a fully-qualified filename using the MFPRELOAD_LOGNAME environment variable. The log file produced is a line-sequential text file that you can view in any text editor and contains information on any problems that were encountered when trying to preload the Mainframe Express system files.