Not all mainframe programs are suitable for remote execution using the Mainframe Call Generator. Before using the Mainframe
Call Generator for an application, check that the application does not use any of the following features:
- MVS control blocks, passing back a control block to
Enterprise Developer on the calling Windows machine will result in unexpected behavior.
- Multiple programs invoked in a multi-step JCL stream. Each program calls a subroutine (Assembler) to detect in which step
it is running. If the Assembler subroutine is the remote program (that can not be offloaded to the Windows machine), this
will result in unexpected behavior, as the JCL on the mainframe will be a task started by the Mainframe Access Server, rather
than the JCL started by
Enterprise Developer.
- Allocation of OS/390 data sets. Allocations made in
Enterprise Developer do not translate to allocations in the remote subroutine that is run by the task started by the Mainframe Access Server.
Only those allocations available to Mainframe Access Server are available to the subroutine.