Product Overview

The Transaction Processing System (TPS) is a library of transaction processing procedures that gives a centralized definition of transactions that all programs can access. TPS also controls input transactions accessing the database so that synchronized recovery can be applied in the event of a system interruption.

A new level of functionality is provided for application systems when you implement TPS with Enterprise Database Server for ClearPath MCP. Centralized accessing techniques through the use of libraries reduce the complexity of application programs that require database information. You can accomplish reduced program maintenance by having to change only the centralized update library routine as opposed to every program that uses the routine. Standardization of transaction definition provides better control of the programs accessing the database. You achieve a high level of coordination of transaction processing and recovery when multiple application programs that execute concurrently update the same database. Comprehensive recovery capabilities simplify the restart logic required in application programs.

General Features

Programs that are written in a transaction-oriented database environment must contain logic relative to the user’s application. Logic is also required to access the database that might be specific to the application but not to the individual program. An installation might want to divide and separate those general functions that are not necessarily program specific but are database dependent.

A transaction history journal audits transactions applied to the database. In recovery mode, input transactions can then be reapplied to the database after Enterprise Database Server recovery is complete. Transactions are serialized to ensure properly synchronized recovery. Database access code is centralized into isolated, highly modularized units of code called transaction processing routines. These routines are located in the update library accessed through the transaction library.

Transactions are centrally defined for an environment in the transaction description file. An input transaction record determines which routine in the update library is to be used in accessing the database. An output transaction record is used to return the results of processing by the routine that was selected. A restart transaction record can be specified in the routines to aid the application in the event that a recovery operation is required. The Transaction Formatting Language (TFL) is used to define all transaction records.

You can use a remote library on a remote system to allow your programs to access the database on a host system. No changes in your programs are needed to run the database on the remote system.

Tank journals are provided for batching transactions that are held for future processing.

Ordering Information

Source code is available for this product. You can license it separately.

Product Information

Refer to the Enterprise Database Server TPS Programming Guide (8807 6138) for more information.