T

table

1) An IDD entity type used to define edit and code tables. Edit and code tables are used during automatic editing to validate and encode/decode data values in map data fields. 2) A CA IDMS/DB data table. See also data table. 3) Any collection of data in tabular form.

table data area

In ASF, the area in which table data is stored, as opposed to the table definition area in which table definitions are stored. Table definitions and data should not be stored in the same area. See also area, IDMSR- AREA2.

table definition area

In ASF, the area of a CA IDMS/DB database used to store definitions of data tables, as opposed to the table data area in which table data is stored. Table definitions and data should not be stored in the same area. See also IDMSR-AREA.

table definition record

In ASF, a record, stored in the table definition area of the database, that contains the definition of a data table. The definition record is stored separately from the actual data for that data table.

table ID

A numeric identifier assigned to a base table to uniquely identify its rows within an area.

table procedure

The entity created by a CREATE TABLE PROCEDURE statement.

tabular data

See data table.

tailored diagram

A data structure diagram as it appears after you have used at least one optional CA IDMS Schema Mapper parameter statement to modify the layout or format of the diagram that is generated by default (use of the PROCESS statement only).

target node

In a DC/UCF communications network, the DC/UCF system that is identified to service a database request by the host node. See also host node, server node.

target page

The database page that the DBMS uses when trying to store or access a particular record.

task

1) The basic unit of work under DC/UCF that consists of the execution of one or more programs. A task is identified to the system by its task code (such as MAPC). 2) An IDD entity type used to document teleprocessing system tasks.

task application table (TAT)

In CA ADS, the table that contains a list of all task codes and the applications they activate. The TAT is updated in the data dictionary by the application compiler and is used at runtime. The TAT can be built and migrated by using the ADSOTATU utility. See also ADSOBTAT, ADSOTATU.

task code

The unique name that identifies a task to DC/UCF. The user types the task code in response to the DC/UCF system prompt. Task codes are defined at system generation or by using a DCMT VARY DYNAMIC TASK command.

task control element (TCE)

The control block that ties together all of the resources of a task, indicates the status of the task, and provides a stack of system working storage and user registers.

task definition element (TDE)

The DC/UCF control block that specifies general task characteristics. Task definition elements are assigned either at system generation or by using the DCMT VARY DYNAMIC TASK statement.

task identifier

The unique identifier (numeric) assigned to the execution of a task or a task thread.

task thread

A particular execution of a task.

TAT

See task application table (TAT).

TCE

See task control element (TCE).

TCF

See transfer control facility (TCF).

TCP

See transmission control protocol.

TCP/IP stack

An instance of a TCP/IP implementation.

temporary table

A table created by an SQL session that exists only for the duration of the transaction in which it is created. The table can be populated and that table data can be manipulated within the transaction.

terminal I/O

The input/output operations between main storage and a user terminal. Terminal I/O is controlled by a teleprocessing monitor.

terminating task data transfer

A means of data transfer from program storage to a terminal or device using CA IDMS UCF to pass the data and control serially between a CA IDMS UCF front end and back end. The front end initiates a task on the back end system and waits until the task is complete to return the requested information. See also non-terminating task data transfer.

test mode

The mode of DC/UCF that you use to execute test versions of programs. You specify test modes by using the DCUF TEST command. For CA ADS Batch applications, you specify test modes by including the test control parameters in the job stream.

With test mode in effect, DC/UCF first searches for programs whose version number matches that specified by the DCUF TEST command. You can specify version numbers for dictionary load modules. Additionally, z/OS users can specify test load libraries in the startup JCL by using Vnnnn DD statements, where nnnn corresponds to the test version number.

third normal form

See normalization.

threshold task

A task to be invoked when a queue contains a certain number of entries (records). When the specified number of entries is reached, the system initiates the task, which processes the records in the queue.

ticker interval

The frequency with which the DC/UCF system checks for time-related events (such as runaway tasks).

TIME checkpoint record

The checkpoint that marks the initialization of the journal buffer. The date and time values for this checkpoint are supplied when the journal buffer is written to the journal file.

top-level session

A database session that has no encompassing session. See also database session, encompassing session, subordinate session, peer session.

TP-monitor program

A program that executes under a teleprocessing (TP) monitor other than CA IDMS/DC. TP-monitor programs use central version operations to access CA IDMS/DB databases.

trace

Under CA IDMS Dictionary Migrator, to identify an entity, its related entities, its related components, and all of the connections among these entities and components.

trace facility

Any debugging tool used to record a sequence of runtime commands, programs, or modules. CA IDMS provides the following trace facilities: batch trace facility, database trace facility, system trace facility, user trace facility, and CA ADS batch trace facility.

transaction

1) A database transaction. 2) The series of tasks that perform one logical activity. For example, a transaction typically includes all tasks that display, retrieve, and process data on a single map. Note, this type of transaction is different than a database transaction, which CA IDMS/DB uses to manage resources and control recovery. See also database transaction. 3) An IDD entity type used to document collections of functions or processes.

transaction branch

A portion of a transaction that is a separately identifiable unit of work within which deadlocks cannot happen. Each database session that does not share its transaction with another session causes a new transaction branch to be created. A hierarchy of transaction branches can be created. The target of a commit or backout operation is always a single transaction branch, but the operation includes all subordinate branches of the target.

transaction branch identifier (BID)

A 16-byte value that uniquely and globally identifies a transaction branch. It is composed of the 8-byte node name of the local central version and an 8-byte hexadecimal value. Once assigned to a transaction branch, the BID never changes even if the branch participates in serially-executed transactions.

transaction lock

A lock set and examined by CA IDMS/DB in order to control access to individual records and areas. See locking.

transaction manager

A software component that directs commit and backout processing. In a distributed transaction, multiple transaction managers can be involved in a single commit or backout operation. If so, their actions are coordinated to achieve a consistent result. Every central version contains a transaction manager as a component.

transaction sharing

A facility that allows two or more database sessions to share a single transaction in order to eliminate inter-session deadlocks.

transaction state

The state in which an SQL session can access data. READ ONLY means the session can read, but not update, data. READ WRITE means the session can read and update data.

transaction statistics

Statistics collected by DC/UCF for a transaction.

transfer control facility (TCF)

The CA IDMS software tool that enables the terminal user to transfer from one CA IDMS online tool to another without having to return first to DC/UCF.

Transfer File

An output file that reflects the layout and format of a CA IDMS Schema Mapper data structure diagram. The Transfer file contains parameter statements. You can use it as a time-saving device, as input, when recreating or modifying a CA IDMS Schema Mapper data structure diagram.

TRANSIENT READ isolation level

An isolation level in which CA IDMS/DB places no locks on rows accessed by the session and prevents the transaction from performing updates. This isolation level provides no protection from the effects of concurrent database transactions; that is, it allows a session to read uncommitted data and allows other transactions to update the data. See also CURSOR STABILITY isolation level, isolation level.

transient retrieval area status

The status of an area in which database transactions executing under the central version retrieve data using no record locks. A local mode application or another central version can concurrently update the area.

transient retrieval ready mode

A retrieval ready mode set automatically if the area has a transient retrieval status or the isolation level of an SQL session is transient read. Under this ready mode, other transactions executing concurrently under the central version can ready the area in any mode.

transmission control protocol (TCP)

A reliable, connection-oriented IP protocol.

transparency

In IDBCOMM, a process of data transmission that prevents data from being mistaken for control characters and from being converted improperly during transmission.

When transparency is not requested, data tables are sent as is and binary data is sent in 4-bit format. Data is grouped into 4-bit chunks during the conversion process.

When transparency is requested and the type not specified, the default is 6-bit format. Data is grouped into 6-bit chunks during the conversion process.

TUNE INDEX

The Tune Index Utility walks a sorted index in order to cause the adoption of orphaned indexed records. An orphaned indexed record is a record whose index pointer does not point back to the index record (SR8) which contains the record's index entry.

two-phase commit

1) A protocol that is used to achieve a coordinated commit for a distributed transaction. 2) A commit operation that uses a two-phase commit protocol.