This chapter explains what Mainframe Transaction Option is and how you use it.
Mainframe Transaction Option is a facility available with Net Express, Server Express and Enterprise Server that enables CICS, IMS and JCL applications that have been migrated from the mainframe to be maintained, developed and deployed on Windows or UNIX platforms.
Micro Focus or third-party systems integrators use the Migration Toolkit to migrate the application from the mainframe environment to the Windows or UNIX environment.
You use Net Express with MTO for maintaining your CICS, IMS and JCL applications. If you are working with CICS, you can edit and compile BMS maps, and also compile the CICS programs, using the Micro Focus CICS preprocessor, which translates the CICS commands into native code. If you are working with IMS, you can edit and generate your DBDs, MFSs and PSBs, and compile your IMS programs. If you are working with JCL, you can edit and create JCL, and build projects containing the programs that the JCL references. When the application is ready to run, you then deploy it to Enterprise Server with MTO.
The Mainframe Transaction Option in Server Express (Server Express MTO) offers an alternative environment for the compilation of CICS programs and programs controlled by JCL jobs.
Net Express MTO is always the first choice for maintenance and development regardless of the platform to which the application will be deployed.
You use Enterprise Server with MTO for running your CICS, IMS and JCL applications, for testing and for production use. Enterprise Server with MTO also provides facilities for monitoring and controlling your applications and for other tasks such as maintaining CICS resource definitions and viewing the system catalog and spool queues.
For information about development licensing, see your Net Express License Management System User's Guide or your Server Express Development Licensing Guide. For information about deployment licensing (that is, Micro Focus Server licensing), see your Deployment License Management Guide.
Once the application has been migrated, developers take over. The development process using Net Express as the development environment running alongside Enterprise Server is as follows:
Steps 3 through 6 need to be repeated as required to get the application working correctly.
Developers need to have some familiarity with running programs in Enterprise Server and the facilities provided therein specifically for monitoring CICS, IMS and JCL applications.
Once the application is working correctly, administrators look after the running and monitoring of the application in Enterprise Server for Windows or Enterprise Server for UNIX. They need to:
The administration tool ESMAC, Enterprise Server Monitoring and Control, provides facilities for maintaining resource definitions and monitoring and controlling CICS, IMS and JCL applications. Many of its facilities are also available for non-MTO applications running in Enterprise Server. For detailed information about running CICS, IMS and JCL applications in Enterprise Server, see the chapters Administering MTO-enabled Enterprise Servers for CICS, Administering MTO-enabled Enterprise Servers for IMS and Administering MTO-enabled Enterprise Servers for JCL.
You also need to use facilities in the main Enterprise Server interface. For more information see the main Enterprise Server Configuration and Administration Guide
The JCL support in Mainframe Transaction Option includes an event manager, which provides support for third-party products such as schedulers.
When an enterprise server is started, it can call a user exit program, which on this first call can register an interest in particular types of events (for example, abends). Then whenever an event of any of the registered types occurs, the event manager will call the user exit program to process it. This user exit program can be a third party tool, such as a scheduler.
For further information, please contact your sales representative.
Copyright © 2006 Micro Focus (IP) Ltd. All rights reserved.