Tutorial: Assembler Support

Provides step-by-step instructions that walk you through the process of building a sample Assembler application in Enterprise Developer, configuring an enterprise server region on which to run the application, and testing the application in TN3270 mode.

Restriction: This topic applies to Windows environments only.

Assumptions

This tutorial is written from the perspective that all of the following is true. Specific instructions for setting your environment to adhere to these assumptions is found in the Before you begin this tutorial section that follows:

Windows File Explorer is set to show file names and extensions.
You are running the latest version of Micro Focus Enterprise Developer, which has been installed on your local machine using default installation settings, including the Rumba+ Desktop option.
Enterprise Developer is started on your local machine, and the appropriate Perspective and View are open..
Eclipse options are set to build projects automatically.
You are using the Rumba+ Desktop TN3270 emulator when instructed to run the AACT transaction in TN3270 mode. If you choose to use an alternative emulator, adjust the instructions to accommodate your software.
You have addressed all of the items in the Before you begin this tutorial section below.

Before you begin this tutorial

Before beginning this tutorial, be sure you have addressed each of the following items:

Set Windows File Explorer options

These tutorials assume that your Windows File Explorer options are set to use the Details layout, and to show file name extensions. See your Windows documentation for more information.

Start Enterprise Developer

Start Enterprise Developer using the default workspace, which is c:\users\username\workspace where username is your operating system login ID. If you need instructions to get Enterprise Developer started on your local machine, see To start Enterprise Developer.

Open the appropriate Perspective and View in Eclipse

When you start Enterprise Developer for the first time, the Team Developer perspective starts automatically by default, and shows the Application Explorer view. If this is not the case, open the Team Developer perspective as follows:

From the Eclipse IDE, click Open Perspective .
On the Open Perspective dialog box, select Team Developer (default), and then click OK.

In addition, the Enterprise Development Projects system should be loaded in the Application Explorer view. To confirm this:

In the Application Explorer view, you should see the Enterprise Developer system. If the system is not shown, to load it:
1. Right-click in the Application Explorer view, and then click Add System(s).
2. In the Add System(s) dialog box, select ED System and click OK.
3. Expand the top-level Enterprise Developer entry in the Application Explorer view.
4. Right-click Enterprise Developer Projects; then click Load Application.
Otherwise, expand the Enterprise Developer system. An entry titled Enterprise Development Projects should appear indicating that the system is loaded.

Set Eclipse to build automatically

By default, the Eclipse Build Automatically option is turned on, which means that Eclipse builds a project automatically each time a change is made. To ensure that this Build Automatically is turned on:

From the Eclipse Main Menu, click Project.
Do one of the following:
- If the Build Automatically menu option has a check mark to its left, it is already turned on. No further action is required.
- If the Build Automatically menu option does not have a check mark to its left, click the option to turn it on.

Set Rumba+ TN3270 options

In Eclipse, click Window > Preferences; then expand Micro Focus > Enterprise Server, and click TN3270.
In the right frame, ensure that Rumba (Embedded Version) is selected, and that Connect automatically is checked.
Close the Preferences page.

Demonstration Application - AACT

The AACT demonstration application is the Assembler version of the standard example application that IBM supplies with CICS systems. Enterprise Developer provides the following Assembler executables, BMS, and copybook files:

asmacct00.mlc: The program associated with the ACCT transaction. It displays a menu screen for the on-line account file application, which prompts the user for input. Transaction AC01 is invoked when that input is received.
asmacct1.mlc: The program associated with the AC01 transaction. Analyzes all requests, and completes those for name inquiries and record displays. For update transactions, it sends the appropriate data entry screen and sets the next transaction identifier to AC02, which completes the update operation. For print requests, it starts transaction AC03 to do the actual printing.
asmacct.mlc: The program associated with the AC02 transaction. It completes requests for account file updates (adds, modifies, and deletes), after the user entered the update information.
asmacct.mlc: The program associated with the AC03 transaction. It completes a request for printing of a customer record, which was processed initially by transaction AC01.
asmacct.mlc: The program associated with the AC04 transaction. It is a general purpose error routine that is invoked by other programs in the online account file application when an unrecoverable error has occurred. It sends a message to the input terminal describing the type of error and prompts the operator to report it. It then exits, backing out any updates made in the uncompleted transaction.
AACTSET.bms: The BMS mapset used by the AACT application.
ACCTREC.cpy: The record definition for the AACTFIL VSAM file used by the application.
AACTSET.cpy: Contains the record definitions for the BMS mapsets.

Sequence

To complete this tutorial, progress through these topics in the order presented here. The bottom of each topic provides Next topic and Previous topic navigational links to help you proceed in the proper sequence: