R

Glossary for CA IDMS › R

R

radix

See database-key format.

RBB

See record buffer block (RBB).

RCE

See resource control element (RCE).

RCM module

A module that contains the SQL statements embedded in an application program. You create an RCM by precompiling the program that contains the embedded SQL statements. See also access module

READY

The database access function that tells CA IDMS/DB which areas of the database the application program will access and in which ready mode.

ready mode

See area ready mode, default ready mode.

realtime monitor

The component of the CA IDMS Performance Monitor that captures and displays information describing the use of specific system resources at the time of the request.

record

1) An IDD entity type used to document records, reports, and transactions. Typically, records are collections of related elements. Reports are hard-copy records. Transactions are collections of functions or processes. 2) A synonym for record type and for record occurrence. 3) The internal implementation of the rows of an SQL table.

record block

A representation of a CA IDMS record in a CA IDMS Schema Mapper data structure diagram. Record block descriptions can also be listed in the Cross-Reference Report. A record block contains various record fields.

record buffer

The space in memory that is allocated at runtime to hold the data values of a record. The size and layout of a buffer correspond to the definition of that record in the data dictionary. See also buffer, database buffer, journal buffer.

record buffer block (RBB)

In CA ADS, the storage block dynamically allocated by the runtime system for subschema, database, work, and map records used by a dialog. An application can have one primary RBB and as many secondary RBBs as needed. The size of the RBB is specified by the PRIMARY POOL and SECONDARY POOL parameters of the ADSO system generation statement.

record element

1) A logical subdivision of a record, also called an element or a field. 2) In IDD, the entity used to associate an element with a record. See also element.

record ID

A number that uniquely identifies each record type in the database. Record IDs are assigned explicitly by the DBA or automatically by the schema compiler.

record lock

Under the central version, a lock placed on a record occurrence to prevent access to and/or update of that record occurrence. Record locks are used to protect the integrity of database records (for example, preventing concurrent updating of an occurrence by two or more transactions). Record locks are never maintained for transactions operating in local mode since concurrent update is prevented by physical area locks. See also locking.

record occurrence

A collection of related data element values accessible as a unit through CA IDMS/DB. A record occurrence corresponds to a row in a data table.

record prefix

The part of a record occurrence that describes the set relationships for the record. The prefix contains pointers to the next, prior (if applicable), and owner (if applicable) records in all sets in which the record participates.

record type

In CA IDMS/DB, a defined category of information in the database, representing a group of similar record occurrences. (For example, the DEPT record type provides a template for data about all departments within the organization.)

record-type diagram

A graphic representation used to define the characteristics of a record type in the database. A record-type diagram contains such information as record name, id number, and length. Record-type diagrams are used within a data structure diagram to define the entire database. See also data structure diagram.

recovery

The process of restoring the contents of the database when an error occurs that corrupts the database or disk journal file. Recovery procedures restore altered areas to their original state.

recovery unit

The part of a transaction that falls between two checkpoints.

reentrant pool

The storage space in memory into which reentrant programs and tables are loaded for execution. Reentrant pool specifications are part of a system's definition.

reentrant program

A program that dynamically acquires all variable storage and does not modify its own code.

referenced table

The table in a referential constraint that contains the primary key. To assure referential integrity between two tables, a row in the referenced table cannot be deleted or have its primary key altered if the primary key value exists as a foreign key in the referencing table.

referencing table

The table in a referential constraint that contains the foreign key. To assure referential integrity between two tables, a row can be inserted in the referencing table only if the value of its foreign key exists as a value in the primary key of the referenced table.

referential constraint

A constraint that defines a relationship between two tables. A referential constraint identifies a foreign key in the referencing table whose value must exist as a value in the primary key of the referenced table.

referential integrity

In CA IDMS/DB, the data integrity rule that guarantees consistency between tables that share a common column value. For instance, referential integrity would ensure that customer order information is not added to the database unless the customer has already been added. See also integrity, recovery.

reflexive join

A generic relational operation that yields a result table comprised of columns from different rows of the same table. Reflexive joins are used to implement bill-of-materials structures.

registered user

A user who is permitted to access and/or update an entity occurrence in the data dictionary.

relational DBMS

A database management system based on the relational model. See also relational model.

relational key

In IDD, a user-defined keyword that relates entities of the same type. User-defined nests are implemented through relational keys.

relational model

A data model in which data is represented in data tables consisting of rows and columns. Data tables can be manipulated with the three relational operations: select, project, and join. See also relational DBMS.

relational table

See data table.

RELOAD utility statement

Reloads the database using input created by the UNLOAD utility statement.

relocatable storage

Storage within the DC/UCF region/partition that is eligible to be written to scratch across a pseudo-converse. In CA ADS, storage used for currency blocks, CA ADS control blocks (OTBs), OTB extensions, and variable dialog blocks (VDBs) can be designated as relocatable. Relocating storage makes more efficient use of the storage pool but increases I/O to the scratch area. See also fast mode threshold, relocatable threshold.

relocatable threshold

The point at which DC/UCF transfers CA ADS relocatable storage to the scratch (DDLDCSCR) area across a pseudo-converse. The relocatable threshold is expressed as a percentage. For example, if the relocatable threshold is 75, DC/UCF only transfers inactive storage from the storage pool to the scratch area when the storage pool is more than 75% full. See also fast mode threshold, relocatable storage.

relocated record

In CA IDMS/DB, a record that is moved from its home page to another page by the RESTRUCTURE SEGMENT utility statement, the migration utility (RHDCMIG1 and RHDCMIG2), or as a result of processing an SQL DDL statement. A relocated record is considered an SR3 system record and the line index created for the record on the new page contains a record id of 3. When CA IDMS/DB accesses the record, it can return the record to its home page if there is space available. See also SRn system record.

remote task

In a DC/UCF communications network, a task that uses CA IDMS UCF to execute at a target node rather than at the host node. The host node performs terminal I/O operations. The target node executes the program and either performs database I/O or routes the request through CA IDMS DDS to yet another node. In this case, both the CA IDMS UCF front end and the CA IDMS UCF back end are DC/UCF systems.

requestor lock table (RLT)

In CA IDMS/DB, the lock table created for each transaction with longterm locks.

required field

A field for which the terminal operator must supply input data.

reserved word

A keyword in command syntax that cannot be used for any other purpose. For instance, a reserved word cannot be used where the syntax calls for a user-supplied value.

resident program

A program that is loaded at DC/UCF system startup and remains in the system region/partition for as long as the system is running. Resident programs are loaded into the appropriate program or reentrant pool. You designate resident programs by using the system-generation PROGRAM statement.

resource

1) A component or service used by the DC/UCF system at runtime. Resources include CPU time, program pools, storage pools, tasks, queues, buffers, journals, RLEs, RCEs, DPEs, EREs, database-key locks, the log, the loader, and system service calls. 2) Within the security facility, entities in your environment to which you control access. 3) An object to which requests are routed. See also database resource, global resource, resource name table, system resource.

resource control element (RCE)

The control block created when a task acquires a resource. The RCE contains pointers to the task identifier and to the resource being used.

resource link element (RLE)

The control block that links all resources being used by a task.

resource manager

A software component that controls access to and the state of one or more recoverable resources such as a database. A central version is an example of a resource manager.

resource manager interface (RMI)

A software component that facilitates communication between a transaction manager and a resource manager. The RMI forwards requests from the transaction manager to its corresponding resource manager and returns the results of the operation.

resource name table

A table created by CA IDMS from the RESOURCE TABLE system generation statement. The resource name table identifies the nodes on which resources in your DC/UCF communications network are located. DC/UCF uses the resource name table at runtime to identify the location of resources required to satisfy database requests.

resource timeout interval

The amount of time the DC/UCF system permits a terminal to be inactive before it invokes a resource timeout program. Terminal activity occurs when the user presses a control key (such as ENTER or PF1) that passes data to the system. See also resource timeout program.

resource timeout program

The program invoked by the DC/UCF system when the resource timeout interval expires. See also resource timeout interval.

resource type

Within the security facility, entities in your environment to which you control access. See also global resource, system resource, database resource.

resource, securable

A CA IDMS/DB entity to which you control access. For example, securable resources are users and system profiles.

response

See application response, global response, internal response, local response, valid response.

response field

The special 1- to 32-character map field in which terminal operators can enter a response field value (for a response process or application response) to select the next processing to be performed. The $RESPONSE map field or the AGR-MAP-RESPONSE field of the ADSO-APPLICATION-GLOBAL-RECORD can be used as the response field.

response field value

In a dialog, the field value associated with a specific response process in the dialog. At runtime, the user can enter the response field value in the map's response field to execute that response process.

response process

An optional component of a CA ADS dialog. A response process is executed after the end user presses a control key (such as PF1 or ENTER) in response to the dialog's map. A given dialog can have any number of response processes.

A response process is defined as a standalone process module in the data dictionary. You make a process module a response process for a dialog by using the dialog compiler.

RESTORE utility statement

The utility that restores one or more areas in a database by copying back the contents of a file created by the BACKUP utility statement.

restructure

The process of reorganizing the structure (records, sets, areas) of an existing non-SQL defined database. Restructuring is usually performed to improve database efficiency or to meet changing data management requirements.

See the RESTRUCTURE utility statement.

RESTRUCTURE CONNECT utility statement

The utility that connects new prior and owner pointers in existing sets.

restructure schema compare utility

See IDMSRSTC utility.

RESTRUCTURE utility statement

The utility that modifies record occurrences to match new schema specifications.

RESYNCHRONIZE STAMPS utility statement

In an SQL-defined database, the utility that compares and updates synchronization stamps. The comparison is made between the stamps that reside in an area of an SQL-defined database and their counterparts that reside in the catalog. The utility can update either set of stamps.

retrieval area status

The status of an area defined to the runtime DMCL in which database transactions executing under the central version can retrieve but not update data in the area; a local mode transaction or another central version can update the area.

retrieval path

The logical-record path (defined in a subschema) that carries out the OBTAIN logical-record function requested by an application program. See also OBTAIN path group.

retrieval ready mode

An area ready mode in which the readying transaction can retrieve, but not update, data in the area.

RHDCMAP1

A batch component of the Mapping Facility. See also RHDCMPUT.

RHDCMIG1 and RHDCMIG2 utility programs

Utility programs that convert the DDLDML area of release 10.0 dictionaries to the DDLDML area of a release 12.0 dictionary.

RHDCMPUT

A batch component of the Mapping Facility. See also RHDCMAP1.

RHDCOPTF

A module loaded at CA IDMS startup that identifies the optional functionality activated for the system. This load module is created by assembling and linking the source version of the RHDCOPTF module. The specific optional functionality to be activated is set by using the #DEFOPT macro.

RHDCSMIG utility program

A utility program that converts user, task, and program security definitions from a release 10.2 dictionary to preliminary release 12.0 security definitions and authorizations.

RLE

See resource link element (RLE).

RLT

See requestor lock table (RLT).

RMI

See resource manager interface.

role

In a subschema, an identifier used when a database record occurs more than once in a single logical-record definition. Roles are typically used to process bill-of-materials structures.

ROLLBACK