Previous Topic: Collecting Database StatisticsNext Topic: Run Units


Run Units, Locks, and Database Transactions

A run unit is a database session through which a CA IDMS database can be accessed using navigational DML requests. A run unit is associated with a database transaction that represents the recoverable work done by its associated sessions. Run units can share their database transactions with other database sessions.

Record locks and area in-use locks ensure data integrity by preventing concurrent update of database records by other applications. Additionally, your program can specify area usage modes to ensure a particular level of control over database areas to be accessed. You should be familiar with these locks and usage modes, their uses, and their effect on the run-time system, particularly when running under the CA IDMS central version.

Navigational programs that maintain efficient run units help to maximize the resources of a run-time system. Well-managed record locks, area locks, and database transactions are major considerations in maintaining efficient run units.

This section contains the following topics:

Run Units

Sharing Run Units Between Programs

Record Locks

Area Locks

Area Usage Modes

Database Transactions

Sharing Transactions Among Sessions