Transaction processing system

List of transaction processing systems

• IBM Transaction Processing Facility (TPF) – 1960. Unlike most other transaction processing systems TPF is a dedicated operating system for transaction processing on IBM System z mainframes. Originally Airline Control Program (ACP).
• IBM Information Management System (IMS) – 1966. A joint hierarchical database and information management system with extensive transaction processing capabilities. Runs on OS/360 and successors.
• IBM Customer Information Control System (CICS) – 1969. A transaction manager designed for rapid, high-volume online processing, CICS originally used standard system datasets, but now has a connection to the IBM Db2 relational database system. Runs on OS/360 and successors and DOS/360 and successors, IBM AIX, VM, and OS/2. Non-mainframe versions are called TXSeries.
• Tuxedo – 1980s. Transactions for Unix, Extended for Distributed Operations developed by AT&T Corporation, now owned by Oracle Corporation. Tuxedo is a cross-platform TPS.
• UNIVAC Transaction Interface Package (TIP) – 1970s. A transaction processing monitor for UNIVAC 1100/2200 series computers.
• Burroughs Corporation supported transaction processing capabilities in its MCP operating systems using GEMCOS (Generalized Message Control System of 1976). As of 2012 UNISYS ClearPath Enterprise Servers include Transaction Server, "an extremely flexible, high-performance message and application control system."
• Digital Equipment Corporation (DEC) Application Control and Management System (ACMS) – 1985. "Provides an environment for creating and controlling online transaction processing (OLTP) applications on the VMS operating system." Runs on VAX/VMS systems.
• Digital Equipment Corporation (DEC) Message Control System (MCS-10) for PDP-10 TOPS-10 systems.
• Honeywell Multics Transaction Processing. Feature (TP) – 1979.
• Transaction Management eXecutive (TMX) was NCR Corporation's proprietary transaction processing system running on NCR Tower 5000-series systems. This system was used mainly by financial institutions in the 1980s and 1990s.
• Hewlett Packard Enterprise NonStop system – 1976. NonStop is an integrated hardware and software system specifically designed for transaction processing. Originally from Tandem Computers.
• Transarc Encina – 1991. Transarc was purchased by IBM in 1994. Encina was discontinued as a product and folded into IBM's TXSeries. Encina support was discontinued in 2006.

Processing types

Transaction processing is distinct from and can be contrasted with other computer processing models, such as batch processing, time-sharing, and real-time processing.

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; there is a time delay.

Real-time processing

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

Transaction processing

A Transaction Processing System (TPS) is an information system that collects, stores, modifies, and retrieves the data transactions of an enterprise. Transaction processing systems also attempt to provide predictable response times to requests, although this is not as critical as 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, and each transaction's processing activity is programmed in advance. It is an MIS model.

Transaction processing system features

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

Performance

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

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

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

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

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

Processing in a batch

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

Processing in real-time

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 systems and networking bandwidth), real-time updating is possible.

Databases for transaction processing

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.

• Hierarchical structure: organizes data in a series of levels. Its top-to-bottom-like structure consists of nodes and branches; each child node has branches and is only linked to one higher level parent node.
• Network structure: network structures also organizes data using nodes and branches. Unlike hierarchical structure, each child node can be linked to multiple, higher parent nodes.
• Relational structure: a relational database organizes its data in a series of related tables. This gives flexibility as relationships between the tables are built.

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

• Good data placement: The database should be designed to access patterns of data from many simultaneous users.
• Short transactions: Short transactions enables quick processing. This avoids concurrency and paces the systems.
• Real-time backup: Backup should be scheduled between low times of activity to prevent lag of the server.
• High normalization: This lowers redundant information to increase the speed and improve concurrency, this also improves backups.
• Archiving of historical data: Uncommonly used data are moved into other databases or backed up tables (files). This keeps tables small and also improves backup times.
• Good hardware configuration: Hardware must be able to handle many users and provide quick response times.

Backup 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 well-designed backup and recovery procedures must exist and be adhered to. The recovery process can rebuild the system when it goes down.

Types of back-up procedures

There are two main types of back-up procedures: grandfather-father-son and partial backups:

Grandfather-father-son

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 drive. 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.

Partial backups

Partial backups generally contain only records that have changed. For example, a full backup could be performed weekly, and then 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.

Advantages

• Batch or real-time processing available
• Reduction in processing time, lead time and order cycle time
• Reduction in inventory, personnel and ordering costs
• Increase in productivity and customer satisfaction