DC/UCF System Generation › Data Dictionary Entities

Data Dictionary Entities

A DC/UCF system is represented in the data dictionary by entity occurrences associated with one another through set relationships. When you define a DC/UCF system, the system generation compiler stores the following entities in the system dictionary:

• System
• Program
• Task
• Teleprocessing network entities
• Destination
• Queue

System Entity

The system entity identifies the system and its operating environment and defines system resource allocations and runtime characteristics. One system entity occurrence exists for each DC/UCF system.

In the data dictionary, extensions of the system entity contain:

• Definitions of the runtime environment for CA ADS, CA IDMS Mapping Facility, and CA OLQ
• 3270-type terminal control-key assignments for online components and for line-mode I/O
• Definitions of secondary 24-bit and 31-bit storage pools
• The default usage mode for IDD DDDL compiler access to the data dictionary
• Autotask definitions
• Alternative map tables for runtime mapping operations
• Load lists
• Information on predefined run units for system services such as security enforcement program loading and message access
• Information on resources and nodes located on remote DC/UCF systems
• Definition of an SQL Cache for caching of dynamic SQL statements.

Program Entity

The program entity identifies each program available to the system and defines runtime characteristics for the program (for example, whether the program can be used by multiple tasks at the same time). A program can be a CA-supplied program, a user program, a CA ADS dialog, a subschema, a database procedure, a map, an edit or code table, or an access module. One program entity occurrence exists for each program associated with a system.

Task Entity

The task entity defines a logical unit of online processing. A task is associated with one or more programs. One task entity occurrence exists for each task associated with a system.

Teleprocessing Network Entities

The teleprocessing network entities define the components of a teleprocessing network:

• The line entity identifies and defines runtime characteristics for a group of hardware devices (physical terminals) that use the same access method (for example, VTAM). One line entity occurrence exists for each line associated with a system.
• The physical terminal entity defines a teleprocessing device, such as a CRT terminal, a printer, or a teletypewriter. One physical terminal entity occurrence exists for each physical terminal associated with a line.
• The logical terminal entity defines processing characteristics for a physical terminal. One logical terminal entity occurrence exists for each physical terminal entity associated with a line (except DDS lines).

Destination Entity

The destination entity represents a group of users, logical terminals, or printer terminals as a single logical destination for messages or reports. One destination entity occurrence exists for each destination associated with a system.

Queue Entity

The queue entity defines a disk work area used to store records for subsequent processing. One queue entity occurrence exists for each queue associated with a system.

Entities can exist independently in the data dictionary (that is, not associated with a system). You can use the system generation compiler to copy unassociated entities into a system definition.