Transaction management systems on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


Transaction systems for the mainframe

Transaction management systems on z/OS

Transactions occur in everyday life, for example, when you exchange money for goods and services or do a search on the Internet. A transaction is an exchange, usually a request and response, that occurs as a routine event in running the day-to-day operations of an organization.

Transactions have the following characteristics:
  • Small amount of data is processed and transferred per transaction
  • Large numbers of users
  • Are executed in large numbers.
  • What are transaction programs?
    A business transaction is a self-contained business deal. Some transactions involve a short conversation (for example, an address change). Others involve multiple actions that take place over an extended period (for example, the booking of a trip, including car, hotel, and airline tickets).
  • What is a transaction system?
    Transaction systems must be able to support a high number of concurrent users and transaction types.
  • What are the typical requirements of a transaction system?
    A transaction system must comply with atomicity, consistency, isolation, and durability.
  • What is commit and rollback?
    In transaction systems, commit and rollback refers to the set of actions used to ensure that an application program either makes all changes to the resources represented by a single unit of recovery (UR), or makes no changes at all. The two-phase commit protocol provides commit and rollback. It verifies that either all changes or no changes are applied even if one of the elements (like the application, the system, or the resource manager) fails. The protocol allows for restart and recovery processing to take place after system or subsystem failure.
Related information

Go to the previous page   |   Go to the next page

Notices | Terms of use | Support | Contact z/OS



Copyright IBM Corporation 1990, 2010