In this session you take an application that includes CICS and contains some Assembler programs and get it working on Mainframe Express.
You need to have read the chapter Start Here for the Tutorials and worked through the sessions Using Mainframe Express, CICS Applications, and Assembler Applications , before you do this session.
You need to have installed CICS Option and Assembler Option to do this session. We assume you are familiar with CICS and Assembler on a mainframe.
This session shows you how to get a CICS application that includes Assembler modules working on your PC.
The demo application used in this session is an Assembler version of the application that you used in the chapter CICS Applications. In this session, you get it working on your PC. It consists of several Assembler programs and one BMS mapset. The supplied project includes a transaction AACT that starts the first program.
This sample application uses the resources defined in the resource definition file supplied with Mainframe Express. You do not need to make any changes to the resources to get this application working.
If you have closed Mainframe Express, open it as before. If any project window or other windows are open, close them.
In this sample session you:
To create the project:
You now get a page asking which of the installed options this project uses.
Because you have said this project uses CICS, you get the pages that relate to CICS.
Leaving this unchanged means you will use the resource definition file supplied with Mainframe Express.
To add your Assembler source files to the project:
The files are added to the project.
Assembler Option automatically recognises EXEC CICS statements in an Assembler program and sets some compiler directives to indicate this, including settings for the standard CICS prolog and epilog macros. However, since all the Assembler programs contain EXEC CICS statements and use the standard macros, you can set these directives at project level:
A setting in the properties of the BMS mapset controls whether Assembler or COBOL code is produced when you compile the mapset. Let's look at this:
A BMS Painter window opens displaying the first map of acctset.bms.
This displays the Mapset Properties dialog box.
To build the project:
As you saw in the chapter Using Mainframe Express, the correct compiler is automatically called for each source file - in this case, for the Assembler (.mlc) files and the BMS (.bms) file. Each Assembler module is linked to create six load modules.
The build finishes with "Build finished with no errors".
Because there is no COBOL in this application, Run and Start Debugging have the same effect.
To run the application:
A 3270 Terminal Emulator opens in the Application Output window. Messages appear, showing the application starting up. You are taken into the Assembler debugger.
This takes you to a screen showing the application's first map (If the Application Output window is undocked, its title bar changes to "Single Tasking Region (ACCT)".)
Hide the Application Output window.
Close the project. If you want to take a break before going on to the next session, you can close Mainframe Express.
Return to the Tutorials Map in the chapter Start Here for the Tutorials and choose which session to go on to next, depending on your interests.
Comments on the books? Click Send Us Comments.
Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.