Tutorial: CICS Support

Provides step-by-step instructions that walk you through the process of setting up a CICS project in Enterprise Developer, configuring an enterprise server region on which to run the application, running the application in TN3270 mode, and debugging the application.

In this tutorial, you learn how to perform the essential steps required to set up an Enterprise Developer project for a CICS application, including creating the project, importing CICS application source files into the project, setting project properties specific to creating, maintaining, and compiling CICS applications, and building the project into an executable application. This tutorial then walks you through the steps required to use Enterprise Server to create and configure an enterprise server region on which to run the CICS application. Once the application is running, you interact with the running application in TN3270 mode to add VSAM data, and then debug the application in Enterprise Developer to retrieve the VSAM data.

Prerequisite

Review the Assumptions and Before you begin sections in the Tutorials: CICS topic to ensure that your environment is set up properly.

Demonstration application - ACCT

The ACCT demonstration application is the standard example application that IBM supplies with CICS systems. It includes the following source code files, supplied with Enterprise Developer:

ACCT00.cbl
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.
ACCT01.cbl
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.
ACCT02.cbl
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.
ACCT03.cbl
The program associated with the AC03 transaction. It completes a request for printing of a customer record, which was processed initially by transaction AC01.
ACCT04.cbl
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.
acctset.bms
The BMS mapset used by the ACCT application.
ACCTREC.cpy
The record definition for the ACCTFIL VSAM file used by the application.

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:

  1. Set up the ACCT Project
    Guides you through the process of creating, populating, and configuring the ACCT project.
  2. Set up the ESACCT Enterprise Server Region
    Provides step-by-step instructions for creating the ESACCT enterprise server region.
  3. Run the ACCT Application
    Takes you through the steps necessary to start the ESACCT enterprise server region, access the region using the Rumba+ Desktop, initialize a VSAM file, and interact with the ACCT application.
  4. Debug the ACCT Application
    Walks you through the steps required to set Enterprise Server options and create a debug configuration in Eclipse; then debug the ACCT transaction from Eclipse.
Parent topic: Tutorials: CICS