Problem:
We have installed MFE3.1 and need to understand the differences between the following three datasets:
cics.MFENTMAP.DAT - we use this
MFENTMAP.DAT - we do not use this
default.MFENTMAP.DAT - we use this
Also we need to know how to set project options for mfentmap for both cics and batch. We want the ability to redirect the code by having the entry map coded even though the entry point module exits in the loadlib. In the MFE3.0 the batch only used the entry point if a load did not exist, and the cics looked first in the entry point table and then the loads.
Currently, we are getting a RTS198, load failure, mfentmap mapping error alias *xxxx* exists on disk.
Resolution:
The customer originally reported a runtime error RTS198, load failure. Having a program of the same name as the entry point in another load module caused this. After defining the mfentmap.dat properly, the runtime error was resolved.
Explaining this functionality requires more detail than allowed here, so we have attached two sample projects and a Readme.Txt file explaining the details.
This Knowledge Base article includes both a batch project and an online CICS project with details about using each of the mfentmap.dat files in Mainframe Express v3.1. The additional support mentioned in the Readme.Txt file for defining an alias was added starting with MFE30 ALL09. The projects are re-locatable and can be unzipped to any directory for review.
Attachments:
#MFDS
#EnterpriseDeveloper
