Mainframe Call Generator (MCG) Refresh - Micro Focus
Mainframe Call Generator (MCG) Refresh - Micro Focus
Mainframe Call Generator (MCG) Refresh - Micro Focus
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Mainframe</strong> <strong>Call</strong> <strong>Generator</strong> <strong>Refresh</strong><br />
New messages<br />
New diagnostic messages and tracing messages make it easy to follow the execution of <strong>MCG</strong><br />
programs by reviewing MFA Server’s XDBOUT SYSOUT logging data set. When tracing is not<br />
active, new diagnostic messages are used to record program failures (for example, inability to<br />
load a requested program, ABENDs occurring within a <strong>MCG</strong> program, etc.) and exceptional<br />
conditions. When tracing is activated using the MFA Server "trace on" command, the new trace<br />
messages make it easy to examine the flow and content of client-server RPC data and the<br />
execution activity in the mainframe server.<br />
The new messages are presented here, grouped together with other new messages issued by<br />
the same module. The sample trace in Appendix C provides actual examples for most of the<br />
messages.<br />
Module MD@<strong>MCG</strong>EX messages<br />
This module provides support for <strong>MCG</strong> program execution and logic to interface between the<br />
MFA Server communications task (XDBMFADM) and the <strong>MCG</strong> program execution subtask<br />
(<strong>MCG</strong>EXEC).<br />
Messages for logging exceptional conditions<br />
MFM0128I <strong>MCG</strong> subtask <strong>MCG</strong>EXEC cc xxxxxxxx started for XDBMFADM cc xxxxxxxx<br />
This is a normal operational message to log the fact that a new subtask was started for <strong>MCG</strong><br />
program execution.<br />
MFM0128E <strong>MCG</strong> Non-zero return from IGZERRE set call; rc=ddd<br />
The IBM IGZERRE module was called to establish a COBOL runtime environment but has<br />
indicated there is a problem by returning with a non-zero return code. See Appendix A for a<br />
description of the return code values.<br />
MFM0128E <strong>MCG</strong> Module IGZERRE is not available for set call<br />
This message indicates that the IBM IGZERRE module was not loaded during startup and could<br />
therefore not be called to establish a COBOL runtime environment.<br />
MFM0128E <strong>MCG</strong> Non-zero return from IGZERRE reset call; rc=ddd<br />
The IBM IGZERRE module was called to terminate a COBOL runtime environment during <strong>MCG</strong><br />
cleanup but has indicated there is a problem by returning with a non-zero return code. See<br />
Appendix A for a description of the return code values.<br />
MFM0128E <strong>MCG</strong> No IGZERRE COBOL environment found for reset<br />
The <strong>MCG</strong> cleanup service found that no COBOL environment was previously established for the<br />
<strong>MCG</strong> session that is ending.<br />
Trace messages<br />
<strong>MCG</strong> COBOL environment set; IGZERRE rc=ddd<br />
The IBM IGZERRE module was successfully called to establish a COBOL runtime environment.<br />
Confidential - 14 - December 2004<br />
Randy Witek<br />
<strong>Micro</strong> <strong>Focus</strong> Development