CICS transactions - IBM Mainframe

CICS transactions can be grouped into general categories according to their functions. The most common types of on-line processing belong to a small number of categories. Identifying the characteristics of each category will be useful during the design and development of an application. The categories are:

  • Inquiry Transactions
  • Data Collection Transactions
  • Update Transactions
  • Browse Transactions
  • Menu Transactions

Inquiry Transactions

An inquiry transaction provides the terminal user with the opportunity to examine a record from a file or database. It is the on-line equivalent of a simple report program, but is more accurate and will reflect the latest file changes. The user usually supplies the key of the desired record.

Data Collection Transactions

This transaction allows the terminal user to enter data and have that data validated and collected for future processing. In many cases a batch program does the processing. When this is the case the data collection transaction is used to create a transaction file, which will be later taken up by the batch program. The user supplies the data to be collected. The system validates the inputs and gives error messages if necessary. Thus it is ensured that only valid data is entered.

Update Transactions

An update transaction allows the terminal user to make actual file modification on-line. This is desirable when changes must be reflected in the file immediately. An update transaction supports the following functions:

  • Addition
  • Deletion
  • Modification

Browse Transactions

A browse transaction processes a file sequentially. It is similar to the inquiry transaction but allows the user to examine a group of records rather than a single record. This transaction is usually used for searching a file or database based on some criteria. And the transaction will display all the records that meet the specified criteria.

Menu Transaction

Most on-line applications are composed of many separate functions. Each function can be implemented as a separate transaction. A menu transaction allows the terminal user to choose one of the several functions from a single transaction. Rather than entering the transaction ID of each transaction, the user has only to enter the transaction ID of the menu and from there he can choose the required functions from the menu. After the end of the transaction the control is returned to the menu transaction.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Mainframe Topics