Created On:  18 November 2011

Problem:

When I run a program generated with Mainframe Call Generator, I receive an abend '006' and the message says that member MFLSCRPC is not found.

On MFA Server the MCGLIB is specified as follows:

MCGLIB  DD  DISP=SHR,DSN=SYS1.CF.DB.PGM.LOAD     
        DD  DISP=SHR,DSN=I1.IM.CD.PGMLIB         
        DD  DISP=SHR,DSN=L0.TO.CA.MFEEE.LOADLIB  

Resolution:

The abend may be caused because one the following steps has not been executed. To ensure that Mainframe Call Generator will work correctly, check that you have configured the following:

1. Enable MCG
Create a Windows user environment variable named MCGADMIN and set its value to any non-blank value

2. Define a NODE and a drive for SourceConnect
Use MFE Options -> Server Access Configuration to define the MFA Server node and a SourceConnect drive that maps to that server node.

3. Build the calling program
Use MFE to build a COBOL program that contains a call to the target mainframe load module.

4. Generate the MCG stub
Use the MFE MCG feature to create a stub that communicates with MFA Server to execute the target mainframe load module when you run the calling program.
Right click on the program.INT file in the Load Libraries folder found in the project’s Workgroup tab, select Mainframe Call Generator… from the menu and use the MCG dialog to create the stub.

5. Make the target mainframe load module available to MFA Server
Add the target mainframe load module to a program library defined to MFA Server using the MCGLIB DD statement.

6. Run the calling program
Use MFE to run the calling program in the usual way.
When a call to the target mainframe load module is encountered, MFE will execute the generated MCG stub. You are prompted for your mainframe userid and password if this is the first access to the mainframe. You are prompted for DB2 connection information if this program uses DB2.

The complete Mainframe Call Generator guide could be found our SupportLine web site in the section with the Product Updates: Host Connectivity 3.1.
Incident #2513640