E

E-R diagram

See entity-relationship (E-R) diagram.

ECB

See event control block (ECB).

edit table

A list of single values or ranges of values that are valid for a data field. Edit tables are defined through the DDDL compiler and are used during automatic editing of maps.

element

1) The smallest meaningful unit of data within an organization. Elements are also known as fields or data items. 2) An IDD entity type used to define group or elementary data elements. Elements can participate in records built by the DDDL compiler, by the CA IDMS/DB schema compiler, or in maps built by the DC/UCF mapping compiler. They can also exist independently in the data dictionary. 3) The database records that participate in a logical record. See also record element.

ELEMENT selector

In LRF, a SELECT clause descriptor that associates a logical-record element with a particular path. At runtime, the path is selected when a program WHERE clause requests any field in the named element.

emulated APPC

CA IDMS emulating software for the PC and mainframe that allows CA ADS dialogs executing on a PC with a 3270 emulator card to emulate advanced-program-to-program communication (APPC) with the DC/UCF system.

encompassing session

A database session under which a subordinate session is initiated. See also database session, subordinate session, peer session, top-level session.

ENDJ checkpoint

A journal checkpoint that marks the successful completion of a transaction branch. An ENDJ checkpoint is written to the journal file during a commit operation. See also COMT.

entity

1) A particular category or type of item in the data dictionary (such as a record, user, program, map, or dialog). 2) An item or idea from an application environment that is represented in the database by a record type.

entity occurrence

A collection of data that conforms to the template provided by an entity type. For example, user WXE is an occurrence of the USER entity type.

entity type

An IDD-defined category of information in the data dictionary that provides a template for similar data. Examples of entity types are PROGRAMS, RECORDS, and USERS.

entity-relationship (E-R) diagram

A graphical description of two or more entities in a database that share a relationship.

entry point

1) An IDD entity type that describes program entry points. 2) The entity that serves as a gateway for CA IDMS Dictionary Migrator to the entities that are to be extracted from the source dictionary. You specify the entry point in the EXTRACT statement.

entry sequencing

In CA IDMS/DB, a method for storing rows in sequential order in the database, based on an index.

ERASE

The navigational database access function that deletes a record occurrence from the database and, where appropriate, deletes records subordinate to it.

ERASE logical record

The LRF database access function that deletes a logical-record occurrence from the database.

ERASE path group

A collection of paths (predefined in a logical-record subschema) designed to service application programs that request an ERASE logical-record function.

ERE

See external request element (ERE).

error-status code

See status code.

ERU

See external request unit (ERU).

EUR date/time format

A date/time format that complies with the IBM European standard: DATE as dd.mm.yyyy and TIME as hh.mm.ss.

EVALUATE command

In LRF, a command that determines whether an expression is true or false. Based on the result, you can direct LRF to perform specific path logic.

event control block (ECB)

A control block used to control the sequencing of events within the DC/UCF system. At runtime, DC/UCF associates an internal ECB with each resource in use by a task. The ECB is used when one task requests a resource in use by another task. The requesting task must wait until the using task posts the ECB to indicate that the resource has been freed. An external ECB is posted by the operating system.

exclusive lock mode

A logical lock mode placed on both areas and record occurrences to protect transactions from accessing data that is being updated by the issuing transaction. An exclusive lock placed on an area implies an exclusive lock on all records in the area. See also share lock mode, null-lock mode.

EXIT

The debugger command that leaves the debugger control blocks intact when returning control to DC/UCF.

EXPAND PAGE utility statement

The utility that increases the page size of an area by transferring a database file to a new file with an expanded block size.

explain

The act of describing the strategy used to access data in an SQL table by issuing an EXPLAIN SQL statement against an access module.

explicit checkout

In ADSA, ADSC, and MAPC, a checkout that allows the application developer to control an entity across repeated definition and compilation sessions. The checkout is not released until this action is explicitly taken by the developer. See also checkout, implicit checkout.

explicit record locks

Record locks set by an application program to preserve a lock that would otherwise be released following a change in currency. See also record lock.

explicitly connected session

An SQL session initiated by a CONNECT statement. See also SQL session.

exploded structure

The expansion of a bill-of-materials structure that traces all records under a given record.

export

An IDMSRADM utility function that moves data from the database to a sequential file.

extended run unit

In CA ADS, a run unit that is kept open (in certain cases) when a dialog passes control to another dialog or to a user program. See also run unit.

external cursor

A global cursor declared in one program that is shared by another program, where both programs are included in the same access module. You define an external cursor using the DECLARE EXTERNAL CURSOR statement. See also cursor, global cursor, shared cursor, updatable cursor.

external picture

The format of data as displayed on the terminal screen or in printed output. An external picture can be defined in a record element through the DDDL compiler, or defined dynamically through CA OLQ or MAPC. Among other places, external pictures are used during automatic editing of maps.

external procedure

See external SQL procedure.

external request element (ERE)

In a DC/UCF system, a control block used to handle processing requests that initiate from outside the DC/UCF region/partition. EREs are used by external request units, the CA IDMS UCF front-end program, and nodes that communicate with the system through a CA IDMS SVC.

external request unit (ERU)

A request for DC/UCF system services that originates outside the DC/UCF address space and uses the SVC to communicate between the application and the DC/UCF system. External request units are initiated for: CA IDMS batch and CICS programs requesting database services, programs requesting DC/UCF services using CA IDMS UCF front end modules, and DC applications requesting services from a different address space within the same mainframe (DC-to-DC communication). See also bulk external request unit.

external routine

An SQL routine written in PL/I, COBOL, or assembler. All user-defined SQL routines are external routines. See also SQL routine.

external security

In CA IDMS centralized security, an external security system, such as CA ACF2 and CA Top Secret, to which you can route a request for a security check. See also internal security.

external SQL procedure

A procedure or a table procedure.

external user session

A logical connection between a DC/UCF system and an application executing outside that DC/UCF system. An external user session is initiated when the application initiates the first request for services within the DC/UCF system and is terminated when the last service initiated by the application is terminated. An external user session can use the following communication methods: external request units, DDS, or LU 6.2.

external wait time

The amount of time the DC/UCF system waits for an external user session to issue a request before assuming that the application has terminated.

extract file

1) In CA ICMS, data selected from a non-CA IDMS/DB or non-CA ICMS file. 2) The file used by CA Culprit to store data selected for the report(s) in a given run.

Extract Journal utility statement

The utility that extracts the most recent AFTR image for each dbkey recorded on an archived journal file and writes it to an extract file. The extract file can later be used as input to a ROLLFORWARD command for a "quick" recovery of a database area or file.

extract path

The route CA IDMS Dictionary Migrator follows through the dictionary's set connections from the entity specified in the EXTRACT statement to all of its related components.