Previous Topic: Products

Glossary

accessor ID (ACID)

(1) An accessor ID designates a user in SQL. This is a user ID, not a schema authorization ID. (2) An accessor ID, in security products such as CA Top Secret, is a unique character-string identifier by which the product identifies the security record (user characteristics, authorities, and so on) of a user.

address space (z/OS)

For information about an address space in z/OS, see the definition of region.

alias

An alias in CA Datacom Datadictionary is an alternate name for an entity-occurrence.

alternate key

An alternate key in a CA Datacom/DB table created through SQL is any unique key other than the primary key. See key, foreign key, and primary key.

area

In CA Datacom/DB, an area is an operating system data set that can consist of one logical table or multiple logical tables. Each database consists of one or more index areas (IXX or Inn) and one or more data areas.

authorization identifier (AUTHID)

In SQL, an authorization identifier (AUTHID) is what identifies a schema. Every table, view, plan, and synonym in SQL is contained in a schema. A fully qualified object name includes the AUTHID of the schema containing the object.

CA Datacom Datadictionary

CA Datacom Datadictionary is a central, integrated, and active control facility that provides the basis for shared and consistent system resource management in the CA Datacom/CA Ideal environment. It is the repository of descriptive data for CA Datacom/DB and other CA products and is a component of CA Datacom/DB.

CA Datacom DB2 Transparency

CA Datacom DB2 Transparency is a software conversion tool that provides applications and data to the CA Datacom/DB environment.

CA Datacom DL1 Transparency

CA Datacom DL1 Transparency automates the reengineering of DL/I and IMS data to the CA Datacom/DB environment, then provides an application transparency which preserves the use of existing DL/I applications.

CA Datacom TOTAL Transparency

CA Datacom TOTAL Transparency automates the reengineering of TOTAL data to the CA Datacom/DB environment, and then provides an application transparency which preserves the use of existing TOTAL applications.

CA Datacom VSAM Transparency

CA Datacom VSAM Transparency allows VSAM applications to execute after VSAM files have been defined to CA Datacom Datadictionary as CA Datacom/DB tables and the data has been transferred to these tables.

CA Datacom/AD

CA Datacom/AD is a subset of the CA Datacom product line that provides for the access and storage of data for various CA using products (application products) while providing significant enhancements to performance and ensuring data integrity.

CA Datacom/DB

CA Datacom/DB is a high-performance relational database management system (DBMS) used to organize, store, update and retrieve your corporate information.

CA Datacom/DB Reporting Facility

CA Datacom/DB Reporting Facility generates customized reports from data stored in CA Datacom/DB.

CA Dataquery

CA Dataquery is a query product designed to access, manipulate, and report mainframe data. Provides personal databases and supports its own language (DQL mode) and SQL language (SQL mode). CA Dataquery requires CA Datacom/DB.

CA Ideal

CA Ideal is a CA fourth-generation programming language.

column

(1) In CA Datacom/DB, a column is a vertical set of data in a table. Each column has a name and a specific data type. All the values in a column have the same characteristics. Each row in a table is defined to contain the same columns in the same sequence. (2) In CA Datacom Datadictionary, a column is defined as a FIELD entity-occurrence.

commit

In CA Datacom/DB, a commit frees locks so that data which has been changed by an application or user can be referenced by other applications or users. When data has been committed and a new commit point is established, committed data cannot be rolled back.

commit point

In CA Datacom/DB, a commit point is the point at which data is considered to be consistent.

CXX

See Directory.

database

(1) In CA Datacom/DB, database is a collection of data and an index for finding data that can be accessed according to data values. (2) When conforming to the CA Datacom Datadictionary CA Datacom/DB Model, a database is a component of an information base, where a DATABASE entity-occurrence is composed of one or more TABLE entity-occurrences where data is stored.

Database Administrator

A Database Administrator is a person responsible for administering the operation of the CA Datacom system. A Database Administrator's responsibilities include maintaining data integrity, maintaining accessibility of data, and monitoring performance.

database management system (DBMS)

A database management system (DBMS) is a layer of software used to manage and access databases. A DBMS shields users from hardware-level detail and provides a higher-level view of databases. For example, CA Datacom/DB is a DBMS.

dataview

A dataview is a logical user view of the data, independent of the area in which the data is stored. Used by CA Ideal and CA MetaCOBOL+, a dataview provides improved insulation of user requests from the physical location of the data.

Directory (CXX)

The Directory (CXX) is the CA Datacom/DB information base used to store definitions of the databases, areas, tables, fields, keys, and elements. It acts as a high-speed directory when data access is requested. CXX definitions are maintained through the CA Datacom Datadictionary.

domain

In SQL, the domain is the range of possible values for a column in a table.

DQL mode

DQL mode provides CA Dataquery features that differ in varying degrees from the version of CA Dataquery accessible to users operating in SQL mode and using interactive SQL commands.

element

All data in CA Datacom/DB is defined as a component of an element. An element is defined as the smallest logical grouping of data that can be accessed by CA Datacom/DB commands. An element consists of a single field or a group of contiguous fields defined to a single table or a record.

element list

In CA Datacom/DB programming, an element list specifies which data elements to retrieve, update, or add.

embedded SQL

Embedded SQL is defined as SQL statements embedded in a host language program that are prepared during the program preparation process before the program is executed. After it is prepared, the statement itself does not change, although values of host variables specified within the statement could change.

field

(1) In a CA Datacom/DB table, a field is the logical portion that contains a value. (2) Columns specified in SQL processing are defined as FIELD entity-occurrences in CA Datacom Datadictionary. See the CA Datacom Datadictionary documentation for discussions of fields as defined by CA Datacom Datadictionary. (3) In most cases, CA Dataquery uses the term column unless referring to a unique CA Datacom Datadictionary characteristic. Also see column, compound field, entry field, and repeating field.

Force Area (FXX)

The Force Area (FXX) contains logging-related information that has been forced from the Log Area (LXX). The FXX is used in conjunction with the LXX for startup recovery. The FXX is paired with the LXX in that it must have the same physical and logical block size.

foreign key

In SQL, a foreign key is a key defined to hold the same values as the primary key of a related table for the purpose of ensuring referential integrity of related data.

FXX

See Force Area.

Index Area (IXX)

In CA Datacom/DB, the Index Area (IXX) is the area of the database that contains the index for tables in that database.

index-only processing

In CA Datacom/DB, retrieving data from the index without reading the related record.

information base

The information base is the total collection of databases operational under one copy of CA Datacom/DB.

IXX

See Index Area (IXX).

JCL

Job Control Language. A problem-oriented language designed to express statements in a job that are used to identify the job or describe its requirements to an operating system.

JES

JES stands for Job Entry Subsystems.

key

(1) A key is a value stored in an index with pointers to its position in the physical database. A key is used to locate a row quickly. (2) A key is composed of one or more columns of a table, where its logical significance depends upon its type. See alternate key, foreign key, Master Key, Native Key, and primary key. (3) A key is reserved for referencing logical concepts which impact functionality as opposed to "index," which is reserved for referencing physical addressing mechanisms which impact performance.

key value

A key value is the actual contents of a key at a given time.

Log Area (LXX)

In CA Datacom/DB, the Log Area (LXX) is a data set used as a temporary storage area for transactions. When the Log Area reaches a user-defined spill point, it is written to the Recovery File (RXX), which can be used to restore the database. The LXX used with the pipeline feature prevents data loss. All updates are logged directly to the LXX. See also pipeline and Force Area (FXX).

logging

In CA Datacom/DB, logging is the building and writing of log records when a CA Datacom/DB maintenance function is performed or when specific log commands (such as LOGCP and LOGIT) are issued.

logging cycle

In CA Datacom/DB, a logging cycle is a logical division on the Recovery File (RXX) consisting of a cycle start record, log data records, and a cycle end record.

LPAR

LPAR stands for logical partition. Dynamic logical partitioning allows hardware resources to be shared by more than one independent operating environment. This is accomplished by dividing a single server into several independent virtual servers or LPARs (logical partitions).

LXX

See Log Area.

Master Key

Each table must have one of its keys designated as the Master Key. This key is the key (a) for which a value always exists in the index (even when the value is blanks or zeroes) and (b) which can be defined as nonduplicatable and nonupdatable.

Master List

A Master List is a definition of the system environment in which an application program is to be executed.

Native Key

Each table must have one of its keys designated as the Native Key. This key is the key used to sequence the records when the table is unloaded. When the table is loaded, the records are therefore loaded in the Native Key sequence.

object

An object is anything that can be created or manipulated with SQL, for example, tables or views.

partition

(1) For distributed database management system, see partitioned database. (2) For z/OS environments, see partitioned table. (3) For z/VSE environments, see region.

partitioned database

In CA Datacom/DB, a partitioned database is a physical database composed of one or more tables, the records of which are limited to those with Native Key values within a range specified by partitioning criteria defined to CA Datacom Datadictionary. Each partition of the logical parent database has its own index and can be distributed to a different location for local access. However, the logical parent of the partitions can still be accessed as a single image.

partitioned table

In CA Datacom/DB, a partitioned table is a table whose rows are stored in table partitions located in multiple data areas. The table is partitioned based on user-defined partitioning criteria specified in a CA Datacom Datadictionary PARTITION-COLUMN-VALUE entity-occurrence.

partitioning

The term partitioning is synonymous with horizontal partitioning, that is, dividing a logical database into two or more discrete, physical databases according to Native Key ranges defined for each individual partitioned database.

partitioning criteria

Partitioning criteria is criteria for partitioning a database into two or more databases based on a high-order part of the Native Key values of its records, as defined in the CA Datacom Datadictionary PRT table.

password

A password is a unique string of characters that are supplied at sign-on to meet security requirements. A password may be but is not necessarily always required.

pipeline

The CA Datacom/DB pipeline feature caches database updates to reduce DASD activity and increase database access speed.

plan

A plan is the control structure produced during the bind process and used by CA Datacom/DB to process SQL statements encountered during application execution. The plan contains information about SQL statements. Each program containing embedded SQL statements must have a plan before being executed.

positioned operations

In SQL, positioned operations are operations performed on the row of a table identified by the positioning information maintained with the cursor control structure, such as the SQL FETCH, positioned UPDATE, and positioned DELETE statements.

primary exclusive control

A task gains primary exclusive control over a record when that task acquires the record for update or deletion. Once the update or delete has taken place, primary exclusive control is dropped over that particular record. Primary exclusive control may also be dropped by the RELES and RELFL commands and for online programs, a program exit. See also secondary exclusive control.

primary key

Defined to a CA Datacom/DB table through SQL, a primary key is the one required unique key that provides a guaranteed method of addressing each row of the table by using the data value of all participating columns. See alternate key, foreign key, and key.

primary table

In CA Dataquery, the primary table is the table read first when more than one table is to be read in the search for data. If the primary table is to be joined to another database table for this search, it must share a key or column with that table.

privilege

A privilege defines what kind of access (SELECT, INSERT, UPDATE, DELETE) is authorized for a particular resource. You must be granted the necessary privilege to execute specific commands, or to grant privileges to other users. The CA Datacom/DB Security Facility must be installed before privileges may be defined.

record

(1) A record is a collection of fields. (2) In CA Datacom Datadictionary, a record is the substructure in the CA FILE Model within a FILE structure. The RECORD substructure contains fields and can contain ELEMENT and KEY substructures. Also see row.

record-at-a-time (RAAT)

In CA Datacom/DB, record-at-a-time programming is an access technique in which records are selected by specifying a previously defined key name and a key value.

recovery

The recovery process restores a database to its last known point of stability. This process can mean the reconstruction of a database from a previous backup copy and a Recovery File (RXX) that contains all updates (forward recovery), or it can mean reversing the effect upon the database (backward recovery) of one or more jobs.

Recovery File (RXX)

The Recovery File (RXX) is the history file of logged data records.

set-at-a-time (SAAT)

In CA Datacom/DB, the set-at-a-time (SAAT) commands access a set of rows (records) that are defined based on the data values contained in the table. Individual rows of the set or a count of the rows in the set can be accessed. The set is selected by specifying a search condition. The rows of the set are returned based on a user-specified sequence of columns in the row, either ascending or descending or as selected by CA Datacom/DB, if no user sequence is requested.

SQL

SQL is a database sub-language which can be used to define, manipulate, and control data in a database.