Mainframe Call Generator (MCG) Refresh - Micro Focus

Mainframe Call Generator Refresh
The solution is to manage the execution of each active MCG process in a subordinate z/OS task.
This new MCG task is dedicated to one user’s MCG activity, but only for the duration of the user’s
MFE-to-MFA Server MCG connection. The MCG user program executes as a separate z/OS
work unit where program loops, excessive CPU consumption, long waits, etc. have little or no
effect on other user activity. This also isolates the IBM COBOL runtime environment and/or DB2
attachment for the user in that same task. Subordinate z/OS tasks are created on demand, one
for each concurrent MCG user. When MCG activity for a user is completed, the subtask remains
active, but waiting, to service the next MCG requester.
This new design allows Mainframe Access Server Version 3 to support all of the MCG processing
previously possible in Mainframe Access Version 2. In addition to merely supporting the old
functionality, Version 3’s new design also improves the MCG feature with selectable DB2
attachment, termination of looping and waiting MCG programs, improved diagnostic messaging,
and detailed tracing of MCG activity. The FixPack maintenance description for this change
summarizes the above discussion:
Mainframe Call Generator (MCG) refresh (RPI 1054397)
--------------------------------------------------------------------
The Mainframe Call Generator (MCG) feature is corrected and enhanced
with the following changes:
- Maintaining a mainframe COBOL runtime environment across multiple
remote calls to, possibly, multiple program load modules
- Execution of MCG programs under a separate z/OS Task Control Block
- Formatted dumping to SYSUDUMP/SYSMDUMP for user program failures
- Termination for user programs that may be looping or stuck in
a WAIT that cannot be satisfied.
- Ability to perform detailed tracing of MCG program activity
- Ability to select either Call Attach Facility (CAF) or the
Recoverable Resource Attachment Facility (RRSAF) as the
DB2 connection type for SQL processing.
*** SPECIAL NOTE ***
The new parameter MFA_MCG_DB2CONNECTION can be used to explicitly
select the DB2 connection type for SQL processing. The valid
values for this parameter are RRSAF or CAF. The default value
is RRSAF.
*** SPECIAL NOTE ***
You will need to add a SYSUDUMP or SYSMDUMP DD statement to each of
your Mainframe Access Server started task JCL procedures to enable
the dumping support for user program ABENDs.
The remainder of this document describes the MCG refresh in detail. Appendix B provides a
handy checklist for MCG program preparation. The annotated sample trace in Appendix C
contains excellent tutorial information that may be useful to technical support and customer
personnel.
Confidential - 4 - December 2004
Randy Witek
Micro Focus Development