Transaction processing system

From Wikipedia, the free encyclopedia - View original article

Jump to: navigation, search

Transaction processing is a style of computing that divides work into individual, indivisible operations, called transactions.[1] A transaction processing system (TPS) or transaction server is a software system, or software/hardware combination, that supports transaction processing.


The first transaction processing systems was American Airlines SABRE system[citation needed], which became operational in 1960. Designed to process up to 83,000 transactions a day, the system ran on two IBM 7090 computers. SABRE was migrated to IBM System/360 computers in 1972, and became an IBM product first as Airline control Program (ACP) and later as Transaction Processing Facility (TPF). In addition to airlines TPF is used by large banks, credit card companies, and hotel chains.

The Hewlett-Packard NonStop system (formerly Tandem NonStop) was a hardware and software system designed for Online Transaction Processing (OLTP) introduced in 1976. The systems were designed for transaction processing and provided an extreme level of availability and data integrity.

List of transaction processing systems[edit]

Processing types[edit]

Transaction processing is distinct from other computer processing models — batch processing, time-sharing, and real-time processing.[9]

Batch processing[edit]

Main article: Batch processing

Batch processing is execution of a series of programs (jobs) on a computer without manual intervention. Several transactions, called a batch are collected and processed at the same time. The results of each transaction are not immediately available when the transaction is being entered;[1] there is a time delay.

Real-time processing[edit]

Main article: Real-time computing

"Real time systems attempt to guarantee an appropriate response to a stimulus or request quickly enough to affect the conditions that caused the stimulus."[9] Each transaction in real-time processing is unique; it is not part of a group of transactions.


Main article: Time-sharing

Time sharing is the sharing of a computer system among multiple users, usually giving each user the illusion that they have exclusive control of the system. The users may be working on the same project or different projects, but there are usually few restrictions on the type of work each user is doing.

Transaction processing[edit]

Transaction processing systems also attempt to provide predictable response times to requests, although this is not as critical as for real-time systems. Rather than allowing the user to run arbitrary programs as time-sharing, transaction processing allows only predefined, structured transactions. Each transaction is usually short duration and the processing activity for each transaction is programmed in advance.

Transaction processing system features[edit]

The following features are considered important in evaluating transaction processing systems.[9]


Fast performance with a rapid response time is critical. Transaction processing systems are usually measured by the number of transactions they can process in a given period of time.

Continuous availability[edit]

The system must be available during the time period when the users are entering transactions. Many organizations rely heavily on their TPS; a breakdown will disrupt operations or even stop the business.

Data integrity[edit]

The system must be able to handle hardware or software problems without corrupting data. Multiple users must be protected from attempting to change the same piece of data at the same time, for example two operators cannot sell the same seat on an airplane.

Ease of use[edit]

Often users of transaction processing systems are casual users. The system should be simple for them to understand, protect them from data-entry errors as much as possible, and allow them to easily correct their errors.

Modular growth[edit]

The system should be capable of growth at incremental costs, rather than requiring a complete replacement. It should be possible to add, replace, or update hardware and software components without shutting down the system.

Types of transaction processing[edit]

Processing in a batch[edit]

Transactions may be collected and processed as in batch processing. Transactions will be collected and later updated as a batch when it's convenient or economical to process them. Historically, this was the most common method as the information technology did not exist to allow real-time processing.

Processing in real-time[edit]

This is the immediate processing of data. It provides instant confirmation of a transaction. It may involve a large number of users who are simultaneously performing transactions which change data. Because of advances in technology (such as the increase in the speed of data transmission and larger bandwidth), real-time updating is possible.

Databases for transaction processing[edit]

Main article: Database

A database is an organized collection of data. Databases offer fast retrieval times for non-structured requests as in a typical transaction processing application.

Databases for transaction processing may be constructed using hierarchical, network, or relational structures.

A hierarchical structure.
A network structure.
A relational structure.

The following features are desirable in a database system used in transaction processing systems:

Backup procedures[edit]

Main article: Backup
A Dataflow Diagram of backup and recovery procedures.

Since business organizations have become very dependent on transaction processing, a breakdown may disrupt the business' regular routine and stop its operation for a certain amount of time. In order to prevent data loss and minimize disruptions there have to be well-designed backup and recovery procedures. The recovery process can rebuild the system when it goes down.

Recovery process[edit]

A TPS may fail for many reasons such as system failure, human errors, hardware failure, incorrect or invalid data, computer viruses, software application errors or natural or man-made disasters. As it's not possible to prevent all failures, a TPS must be able to detect and correct errors when they occur and cope with failures. A TPS will go through a recovery of the database which may involve the backup, journal, checkpoint, and recovery manager:

If a checkpoint is interrupted and a recovery is required, then the database system must start recovery from a previous successful checkpoint. Checkpointing can be either transaction-consistent or non-transaction-consistent (called also fuzzy checkpointing). Transaction-consistent checkpointing produces a persistent database image that is sufficient to recover the database to the state that was externally perceived at the moment of starting the checkpointing. A non-transaction-consistent checkpointing results in a persistent database image that is insufficient to perform a recovery of the database state. To perform the database recovery, additional information is needed, typically contained in transaction logs. Transaction consistent checkpointing refers to a consistent database, which doesn't necessarily include all the latest committed transactions, but all modifications made by transactions, that were committed at the time checkpoint creation was started, are fully present. A non-consistent transaction refers to a checkpoint which is not necessarily a consistent database, and can't be recovered to one without all log records generated for open transactions included in the checkpoint. Depending on the type of database management system implemented a checkpoint may incorporate indexes or storage pages (user data), indexes and storage pages. If no indexes are incorporated into the checkpoint, indexes must be created when the database is restored from the checkpoint image.

Depending on how the system failed, there can be two different recovery procedures used. Generally, the procedures involves restoring data that has been collected from a backup device and then running the transaction processing again. Two types of recovery are backward recovery and forward recovery:

Types of back-up procedures[edit]

There are two main types of Back-up Procedures: Grandfather-father-son and Partial backups:


This procedure involves taking complete backups of all data at regular intervals— daily, weekly, monthly, or whatever is appropriate. Multiple generations of backup are retained, often three which gives rise to the name. The most recent backup is the son, the previous the father, and the oldest backup is the grandfather. This method is commonly used for a batch transaction processing system with a magnetic tape. If the system fails during a batch run, the master file is recreated by restoring the son backup and then restarting the batch. However if the son backup fails, is corrupted or destroyed, then the previous generation of backup (the father) is used. Likewise, if that fails, then the generation of backup previous to the father (i.e. the grandfather) is required. Of course the older the generation, the more the data may be out of date. Organizations can have many generations of backup.

Partial backups[edit]

This technique is normally used in conjunction with regular complete backups. The master file is backed up at regular intervals. In between backups are made only of records that have changed. For example a full backup could be performed weekly, and partial backups taken nightly. Recovery using this scheme involves restoring the last full backup and then restoring all partial backups in order to produce an up-to-date database. This process is quicker than taking only complete backups, at the expense of longer recovery time.

Backup plus journal[edit]

This technique is also used in conjunction with regular complete backups. The master file is backed up at regular intervals. Completed transactions since the last backup are stored separately and are called journals, or journal files. The master file can be recreated by restoring the last complete backup and then reprocessing transactions from the journal files. This will produce the most up-to-date copy of the database, but recovery may take longer because of the time required to process a volume of journal records.

See also[edit]


  1. ^ IBM Corporation. "CICS Transaction Server for z/OS, Version 3.2 Transaction processing". Retrieved Nov 12, 2012. 
  2. ^ "Terminals Help Manage Aluminum Firm's Production". Computerworld. July 26, 1976. Retrieved November 14, 2012. 
  3. ^ UNISYS Corporation (2012). Transaction Server for ClearPath MCP Configuration Guide. 
  4. ^ Digital Equipment Corporation (1989). VAX ACMS Guide to Creating Transaction Processing Applications. 
  5. ^ Bell, Gordon. "Digital Computing Timeline (1985)". Retrieved November 15, 2012. 
  6. ^ Van Vleck, Thomas. "Multics Glossary -T-". Retrieved November 15, 2012. 
  7. ^ Transarc. "Corporate Overview". Retrieved November 16, 2012. 
  8. ^ IBM Corporation. "TXSeries for Multiplatforms". Retrieved November 16, 2012. 
  9. ^ a b c Schuster, Stewart A. (June 15, 1981). "In Depth: Relational Data Base Management". Computerworld. Retrieved November 16, 2012. 

Further reading[edit]