CA IDMS™

Glossary r17

This documentation and any related computer software help programs (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2008 CA. All rights reserved.

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Contents 3

4 CA IDMS Glossary

Chapter 1. Introduction

This glossary presents all terms that are used in the CA IDMS™ systemsoftware environment.

The terms are either of the following:

■ Terms that are unique to CA IDMS products

■ Standard terms that have a specific meaning in the CA IDMS environment

This glossary also includes terms for the following facilities and tools:

■ Automatic System Facility (ASF)

■ Command Facility

■ IDD

■ Logical Record Facility (LRF)

■ Mapping Facility

■ Online Debugger

Chapter 1. Introduction 5

6 CA IDMS Glossary

Glossary

abend code. A four-character alphanumeric codeissued by CA IDMS system components to indicatethe abnormal termination of an operation.

above the bar. Under systems that support 64-bitaddressing, using storage addresses greater than 32MB.

above the line. Under systems that supportextended addressing, using storage addressesgreater than 16 MB. Program, reentrant, storage,and buffer pools can reside above the line. See alsobelow the line.

ABRT checkpoint. A journal checkpoint that marksthe abnormal completion of a transaction branch. AnABRT checkpoint is written to the journal file during abackout operation.

ACB. See application control block (ACB).

ACCEPT. 1) The database access command thatretrieves information pertaining to the status of thedatabase. 2) The DC/UCF function that retrievestask-related information.

access. Retrieval and/or update of data.

access mode. See area ready mode.

access module. A load module that contains theexecutable form of the SQL statements that aprogram issues. You create the access module fromone or more RCMs. When you create the accessmodule, the SQL optimizer determines the mostefficient database access strategy for each SQLstatement contained in the access module. It alsovalidates table and column references in thestatements against the dictionary definition. Seealso default access module.

access privilege. Under centralized security, a typeof privilege that allows a user to access specifiedresources at runtime. There are three types ofaccess privileges: execution privilege allows a userto execute an access module, activity, or category;table access privileges allow a user to performselect, insert, update, and delete operations on atable; special access privileges allow a user tosignon to a DC/UCF system or to execute utilities

against a database area. See also administrationprivilege, definition privilege.

access restriction. The security options thatprotect the database from unauthorized or untimelyaccess by application programs. Access restrictionsfor areas, sets, and record types are defined in thesubschema. See also passkey.

activity. Under centralized security, an applicationfunction defined as a resource to CA IDMS security.You assign activity names and activity numbers toapplication functions with the CREATE RESOURCEstatement. You can define up to 255 discreteactivities for an application.

adaptive query management. A feature of theSQL option that automatically recompiles accessmodules in response to changes in a databasedefinition or application program.

ADB. See application definition block (ADB).

ad hoc query. A one-time request for informationas opposed to a report that is run repeatedly.

administration privilege. Under centralizedsecurity, a type of privilege that allows a user togrant and revoke all privileges, DC/UCF systemprivileges, or database privileges. See also definitionprivilege, access privilege.

ADSA. See CA ADS application compiler (ADSA).

ADS/Batch. See CA ADS Batch.

ADSC. See CA ADS dialog compiler (ADSC).

ADSL. The task code that invokes the facility todisplay checkout status for the ADSA, ADSC, andMAPC compilers. See also checkout, ADSM.

ADSM. The task code that invokes the facility tomodify or cancel checkout status for the ADSA,ADSC, and MAPC compilers. See also checkout,ADSL.

ADSO-APPLICATION-GLOBAL-RECORD. In CAADS, the system record used to pass informationbetween functions and the runtime system. Fields

Glossary 7

defined in this record are addressable and can bemodified by dialogs and user programs. See alsoglobal record.

ADSO-APPLICATION-MENU-RECORD. The CAADS system menu record that is included in all menufunctions (defined in the application compiler). Whenthe map for a menu function is to be mapped out,the runtime system moves values into the fields ofthis record.

ADSOBCOM. In CA ADS, the batch dialogcompiler. ADSOBCOM is the batch alternative to theonline dialog compiler. See also CA ADS dialogcompiler (ADSC).

ADSOBPLG. In CA ADS Batch, the batch utilitythat allows users to format and print the contents ofCA ADS Batch application log files.

ADSOBSYS. In CA ADS, the batch utility thatsupplies system-generation and executionparameters for use when running both ADSOBCOMand CA ADS Batch applications. ADSOBSYS buildsa load module (ADSOOPTI) to contain theparameters.

ADSOBTAT. In CA ADS, the batch utility that adds,modifies, and deletes entries in the task applicationtable (TAT). For example, ADSOBTAT can be usedto update the TAT for a dictionary when anapplication is migrated to that dictionary. See alsotask application table (TAT).

ADSOCDRV. In CA ADS, the runtime program thatinitializes and updates theADSO-APPLICATION-GLOBAL-RECORD, performssystem functions (for example, TOP, POPTOP),processes responses entered on the HELP screen,and selects the value for theAGR-CURRENT-RESPONSE field of the systemglobal record.

ADSOOPTI. In CA ADS, the load module thatADSOBSYS creates. ADSOOPTI supplies CA ADSsystem-generation parameters and CA ADS Batchenvironment information for use during batchoperations. ADSOBCOM and the CA ADS Batchruntime system use information specified in theADSOOPTI module.

ADSORPTS. In CA ADS, the dialog and applicationreporter used to request batch reports about dialogsand applications.

ADSORUN1. In CA ADS, the runtime program thatloads the task activity table (TAT), creates an onlineterminal block extension (OTBX), and loads theapplication definition block (ADB) for the applicationbeing executed.

ADSORUN2. In CA ADS, the runtime program thatallocates space for application global records in therecord buffer block (RBB), builds menu records priorto mapping out application menus, and builds andmaps out the runtime HELP screen.

ADSO-STAT-DEF-REC. In CA ADS, thesystem-supplied status definition record for use intesting the outcome of database operations. Thisrecord defines level-88-condition elements thatidentify the most commonly tested CA IDMS/DBerror-status codes.

ADSOTATU. In CA ADS, the online utility thatadds, modifies, and deletes entries in the taskapplication table (TAT). For example, ADSOTATUcan be used to update the TAT for a dictionary whenan application is migrated to that dictionary. Seealso task application table (TAT).

after image. See AFTR journal record.

AFTR journal record. The journal record thatcontains the image of a database record after therecord has been updated.

aggregate function. In SQL programming, afunction whose argument includes one or morecolumns and which operates on one or more rows.The result of an aggregate function is a single value.This value is derived from the sets of values in thecolumns named in the argument. Types ofaggregate functions include AVG, MIN, MAX, SUM,and COUNT.

alternate picture. In IDD, an alternate format for anelement. For example, the primary format is packeddecimal and an alternate format is zoned decimal.

alternate protect key. One of two storage protectkeys (provided by the operating system) thatDC/UCF uses to implement storage protection.When a program executes in user mode, DC/UCFsets all storage and nonreentrant pool pages usedby the program to the alternate protect key. Thisallows the program to modify only those pages set tothe alternate key. See also primary protect key.

8 CA IDMS Glossary

alternative map. In the mapping facility, analternative copy of a map displayed to selected usersbased on an alternative map table. For example,French-language alternative maps can be generatedfor French users of an international application.

alternative map table. In the mapping facility, atable that associates standard application maps withcorresponding alternative maps. Alternative maptables are generated and associated with users atDC/UCF system-generation time. See alsoalternative map.

animation. An online view of actual CA ADSsource execution which allows you to test and debugCA ADS dialogs using CA ADS Alive.

Animation Mode. In CA ADS Alive, one of twomajor animation modes: Interruptable Mode andNon-Interruptable Mode. Within the InterruptableMode, there are two additional modes: STEP Modeand SKIP Mode.

Animation Runtime Session. The CA ADS Aliveanimation subsession during which the actual onlinedialog code compile takes place.

Animation Setup Session. The CA ADS Aliveanimation subsession during which you defineanimation stop (interrupt) points and specify variousCA ADS Alive operating options.

API. See application programming interface.

application programming interface (API). A set offunctions or methods provided to an applicationprogram for requesting services from anothersoftware component.

Animation Stop Points. A point in dialog sourceat which you tell CA ADS Alive to interrupt (or stop)the dialog animation.

application. 1) In CA ADS, a named set offunctions or dialogs used to accomplish a specificbusiness task (for example, general ledger, shopfloor control, inventory control, payroll). Anapplication is analogous to a program. 2) In ASF,the screen formats (maps) and program logic(dialogs) automatically generated to process a datatable.

application activity. See activity.

application components. The application functionsand application responses defined by using theapplication compiler. See also dialog components.

application control block (ACB). In CA ADS, adata area maintained by the runtime system toprovide information on the executing dialog's mapand database access activities. An application caninclude process code to test certain fields in theACB.

application definition block (ADB). In CA ADS,the application load module generated by theapplication compiler for use by the runtime system.The ADB contains the application informationsupplied on the definition screens during an ADSAsession.

application dictionary. An optional dictionary thatcontains information specific to a particularapplication, group of applications, or developmentgroups. It contains application development objects,such as maps and dialogs; it may also containnon-SQL schemas and subschemas, and in itscatalog component, SQL-defined entities.

application function. The basic structuralcomponent of an application defined using theapplication compiler. Each function represents a unitof work to be performed by the application.Functions can be defined as dialog, menu,menu/dialog, program, or system functions.

application levels. In CA ADS, the runtime,hierarchical structure of an application. Levels,implemented by dialog control commands, are usedin the maintenance of currencies and record buffers.

application mode. In CA ADS, the runtime,hierarchical structure of an application. Levels,implemented by dialog control commands, are usedin the maintenance of currencies and record buffers.

application monitor. The part of the CA IDMSPerformance Monitor that captures resource usageinformation about individual programs, tasks, anddialogs. The application monitor has both an onlineand a batch component.

application response. 1) In CA ADS, the actiontaken by the user when pressing a key or entering aresponse code while the runtime system is executingan application. 2) The response that can initiate anapplication function or a dialog's response process.

Glossary 9

An application response is associated with a functionduring an application compiler session.

application thread. In CA ADS, the sequence ofoperative dialogs in an application. The CA ADSruntime system uses the application thread tomanage the flow of control through functions atruntime. See also menu stack, operative status.

archive. To store data offline.

archive journal file. A journal file that has beenoffloaded from disk to tape. See also journal file.

ARCHIVE JOURNAL utility statement. Thearchive journal utility. ARCHIVE JOURNAL offloads,to one or more archive journal files, the entries inone or more disk journal files.

ARCHIVE LOG utility statement. The archive logutility. ARCHIVE LOG offloads, to an archive file,the contents of the DC/UCF system log.

area. A logical subdivision of the database. Anarea consists of a range of contiguous databasepages. Areas are stored in operating system files;each page corresponding to one or more directaccess blocks.

AREA journal entry. The journal entry that marksthe readying of an area. This record is written to thejournal file when an application program readies thedatabase either explicitly with a DML READYcommand or automatically by CA IDMS/DB.

area-file mapping. 1) The process by which thelogical structure of a database, as defined in areas,is related to the physical structure of the files inwhich the database resides. 2) The resultingrelationship of the process.

area in-use lock. See physical area lock.

area ready mode. The mode in which a databasearea is readied for access. Update mode allows thereadying database session to both update andretrieve data within the area. Retrieval mode doesnot allow the readying database session to updatedata in the area. Each area ready mode can bequalified with a shared, protected, or exclusive optionto control access to the area by concurrentlyexecuting database sessions.

area sweep. A process that consecutively retrievesevery record in an area. A selective area sweep

retrieves every occurrence of a given record type inan area.

AREPORTs. In CA ADS, reports that provideinformation about dialogs (and their components)stored in the data dictionary.

ASF. See Automatic System Facility (ASF).

ASF dictionary. A dictionary used by ASF toestablish, maintain, and monitor database andcatalog definitions. It contains the ASF-DDLDMLand ASF-DDLDCLOD areas.

attribute. 1) In IDD, an entity type used to definecharacteristics that can then be assigned to otherentities. Attribute entities are grouped into classes.For example, COBOL is an attribute of a programand can be grouped into a class called LANGUAGE.See also class. 2) In online processing, acharacteristic of a map field. For example, theBRIGHT attribute is assigned to fields that should bedisplayed at brighter than normal intensity. 3) Inlogical database design, the smallest unit of data thatdescribes an entity or a relationship. Synonyms forattributes are: data item, data element, field, andcolumn. 4)In profile definitions, a keyword and valueassociated with a user or system profile.

attribute byte. In maps, a single-character,nondisplayable byte that begins each map field atruntime. The contents of the attribute byte determinethe characteristics of the field (such as protection orintensity).

authority. The ability to access a resource in aparticular way. Within centralized security, authorityis classified as access, definition, and administrationprivileges. runtime, definition, and administration.

authorization identifier. Under CA IDMScentralized security, an ID that represents a user orgroup which you can authorize to access resources.

automatic editing and error handling. Optionalfeatures in maps and applications that can be usedto perform editing and error-handling services for adialog or program at runtime. When used, thesefeatures can compare input/output data with internaland external pictures, validate data against edittables, and encode/decode data through code tables.

automatic file converter. A program that acceptsCOBOL file descriptions as input and produces CACulprit REC and INPUT parameters.

10 CA IDMS Glossary

AUTOMATIC membership. A membership optionthat determines how member record occurrences areconnected to the set. When a record has automaticmembership in a set, the STORE functionautomatically connects occurrences of that record.

automatic program definition. The automaticdefinition of a subschema, map, edit table, codetable, or CA ADS dialog to DC/UCF. You enableautomatic program definition by allocating nullprogram definition elements (PDEs) during systemgeneration. See also null PDE.

automatic rollback. A rollback performedautomatically by CA IDMS/DB when a transactionfails or an application requests recovery by means ofthe ROLLBACK command. CA IDMS/DB writes anABRT checkpoint for the transaction andautomatically rolls out the changes made to thedatabase by the transaction. The recovery occurswhile the system continues to process requests byother concurrently active transactions.

Automatic System Facility (ASF). An onlinefacility of CA IDMS/DB and CA ICMS used to createand manipulate non-SQL data tables. ASF is usedby end users and data processing professionals tocreate standalone applications, and by databaseadministrators to generate logical recordsautomatically.

automatically connected session. An SQLsession initiated by a statement other than aCONNECT statement. See SQL session.

autostatus facility. A runtime facility that checksfor errors generated by database, logical-record, orqueue and scratch record processing.

autotask. 1) At system startup or shutdown, a taskthat is initiated automatically by DC/UCF. 2) A taskthat is initiated automatically when a user signs on toa logical terminal.

back end. 1) Under UCF, the portion of the systemthat performs DC/UCF tasks. The back end receivescontrol and data from the CA IDMS UCF front end,which can be CA IDMS/DC or any of the othersupported TP monitors. The back end then invokesthe specified task and, when the task is finished,returns control and passes data back to the CAIDMS UCF front end. 2) The CA IDMS centralversion that receives and processes a remotedatabase request.

backlog. In the context of TCP/IP, a value thatlimits the maximum number of pending connections.

backout operation. The process of reversing theeffects of a transaction. During a backout operation,all database changes made during the life of thetransaction are rolled back, and one or more of thefollowing journal checkpoints are written: ABRT,DBAK. See also rollback.

backup. A database maintenance operation thatproduces a copy of the database, that can be usedto restore lost data.

BACKUP utility statement. The backup utility.BACKUP copies one or more areas or files in adatabase to a backup file, which can be used lateras input for a restore operation.

base table. A data table which is not derived fromother tables. See also data table, view.

basic mode. 1) In CA ADS, the mode of operationwhen the runtime system is executing an applicationnot created with the application compiler. Themovement between dialogs is determined solely bythe inter-dialog commands that have been coded inthe dialog premap and response process modules.2) In DML programming, the mode of operation inwhich data and device control characters aretransferred by the application program according tothe type of terminal in use. See also applicationmode.

Batch Command Facility (IDMSBCF). The CAIDMS tool you use to submit Command Facilitystatements as part of a batch job stream. See alsoCommand Facility.

batch control event. In CA ADS Batch, batchconditions, such as EOF and I/O error condition, thatcan occur at runtime during file input operations. Tocause special processing to occur based on one ofthese events, either associate a dialog responseprocess with the events or test for the event in dialogprocess statements.

batch Mapping Facility (RHDCMAP1). The batchcomponent of the Mapping Facility. Use thiscomponent to define, generate, modify, and deletemaps in a batch environment.

batch program. A program that executes in its ownregion or partition. A CA IDMS/DB batch application

Glossary 11

program can run either in local mode or under thecentral version. See also online program.

batch simulation. The simulation of the DC/UCF3270 input and output in batch mode. This capabilityallows you to simulate either single or multipleterminal DC/UCF configurations in a single batchsimulator job.

before image. See BFOR journal record.

below the line. Under systems that supportextended addressing, using storage addresses lowerthan 16 MB. DC/UCF program, reentrant, andstorage pools can reside either below or above theline. See also above the line.

BFOR journal record. The journal record thatcontains the image of a database record before ithas been updated.

BGIN checkpoint. The checkpoint that marks thestart of local work done by a transaction branch.This checkpoint is written to the journal file when thefirst update occurs or when a database transaction isinitiated if JOURNAL RETRIEVAL is specified atsystem generation.

BID. See transaction branch identifier.

bill-of-materials structure. A many-to-manyrelationship among record occurrences of the sametype. A bill-of-materials structure in the databaseenables explosion and implosion of the occurrencerelationships for that record. See also nestedstructure, self-referencing relationship.

BIND. 1) The database access function that initiatesa run unit. The BIND function establishesaddressability in variable storage to the IDMScommunications block, to the record types, andoptionally to procedure control information. 2) ADML command that establishes addressability invariable storage to the map request block (MRB) andto the record types used by the map.

block. 1) In a general database environment, aphysical unit of storage in a file. A block correspondsto a VSAM control interval or a BDAM record. 2) In aCA IDMS DDS environment, a physical unit of datathat can be transmitted from one DDS node toanother.

boolean selection criteria. See selection criteria.

branch identifier. See transaction branch identifier.

breakpoint. A temporary program interruption setby the online debugger. When a breakpoint isreached, control is passed from DC/UCF to theprogrammer.

border. Under CA IDMS Schema Mapper, thenumber of character spaces around the perimeter ofeach record block in the data structure diagram. Aminimum border of two character spaces is neededfor set connections and arrows; the maximum is 50character spaces. A two-character border puts atleast four character spaces between any two recordblocks.

buffer. A location in memory used at runtime tohold database or journal pages. Buffers compensatefor speed differences between the CPU and I/Odevices. You define database and journal buffers inthe DMCL module by using physical DDLstatements. See also database buffer, journal buffer,record buffer, buffer page, buffer pool.

buffer page. A buffer that is capable of holding asingle database or journal page.

buffer pool. A collection of buffer pages capable ofholding database or journal pages.

buffer utilization ratio. The ratio of pagesrequested to pages read by CA IDMS/DB. The ratiomeasures the effectiveness of buffer-pool size andthe database design.

BUILD utility statement. For an SQL-defineddatabase, the utility that builds indexes andreferential constraints linked through an index ontables that are being loaded with a phased orstepped load

builder code. In IDD, a single-character code thatis stored with an entity occurrence. This codeindicates the CA IDMS component that created orowns the entity-occurrence definition.

built-in function. In CA ADS and CA OLQ, aroutine that performs one of a variety of predefinedstring, arithmetic, date conversion, and trigonometricoperations. You can use built-in functions whencoding expressions in process code, selectioncriteria, and column computations.

12 CA IDMS Glossary

built-in table. For maps, an edit or code table thatis defined in and only available to a specific elementin the data dictionary. See also standalone table.

bulk external request unit. An external requestunit that does not use a 3270-type device for input;rather it uses bulk data transfer. See also externalrequest unit (ERU).

bulk fetch. In SQL programming, a FETCHstatement that retrieves multiple rows from a cursorinto a host variable array.

bulk insert. In SQL programming, an INSERTstatement that adds multiple rows in a host variablearray to a table in the database.

bulk processing. A CA IDMS/DB extension toANSI-standard SQL that allows the program toselect, fetch, or insert a group of rows using a hostvariable array.

bulk PTERM. In a DC/UCF system definition, aphysical terminal device type that designates bulkdata transfer. You define a bulk PTERM on theUCFLINE statement for each external applicationthat will concurrently request data services from theDC/UCF system.

bulk select. In SQL programming, a SELECTstatement that retrieves multiple rows from table(s) inthe database into a host variable array.

CA ADS. A general term that encompasses bothCA ADS and CA ADS Batch. CA ADS is aprogramming productivity tool (including afourth-generation language) for applications. CA ADSenables application developers to develop andexecute applications that can query and update a CAIDMS/DB database. CA ADS uses the sameconcepts and facilities as CA ADS Batch.

CA ADS Alive. A source-level testing anddebugging tool for CA ADS applications.

CA ADS application compiler (ADSA). A flexibledesign and prototyping tool. The CA-supplied taskcode for the online application compiler is ADSA.ADSA supplies definition screens that prompt thedeveloper for names of functions, responses,records, task codes, and security and menuspecifications. This information is stored in the datadictionary as a load module and is used at runtime todirect the flow of control in an executing application.

CA ADS Batch. A programming productivity tool(including a fourth-generation language) for batchapplications. CA ADS Batch enables applicationdevelopers to develop and execute batchapplications that can query and update a CAIDMS/DB database. CA ADS Batch uses the sameconcepts and facilities as CA ADS.

CA ADS dialog compiler (ADSC). In CA ADS, theonline development tool used to define dialogs. TheCA-supplied task code for the dialog compiler isADSC. ADSC definition screens prompt thedeveloper for dialog, map, subschema, andprocess-module specifications. ADSC stores thisinformation in the data dictionary and generates loadmodules that are used by the runtime system. Seealso ADSOBCOM, dialog.

CA ADS reports. See AREPORTs.

CA ADS Trace. The CA IDMS product that allowstracing during execution of a CA ADS dialog. CAADS Trace produces an online trace that can bereplayed as often as necessary. By using this traceutility, programmers and application developers canpinpoint the causes of dialog errors right at theirterminals.

CA Culprit. A batch retrieval product designed togenerate reports from CA IDMS/DB databases aswell as from other databases and conventional files.CA Culprit can also be used to create, load, modify,and delete data tables.

CA EDP Auditor. A tool for EDP auditors thatincludes a library of CA Culprit routines whichprovide algorithms and reports for confirmations,statistics sampling, statistics sample analysis, andsummary and graphical analysis.

CA Endevor/DB. CA Endevor/DB is a full-featuredmanagement facility that controls and monitorschange processing within the z/OS CA IDMS/DCenvironment. CA Endevor/DB provides automatedfacilities for performing change identification andmanagement, and promotion or migration of the datadictionary in the CA IDMS/DB environment. It alsoincludes security management, informationmanagement, and the CA Endevor SCM z/OSBridge.

CA ICMS (Information Center ManagementSystem). A corporate information server thatdistributes and manages information between the

Glossary 13

corporate mainframe, departmental minicomputers,and personal computers.

CA IDMS Extractor. An online tool used to specifyand generate test databases.

CA IDMS/DB. A high-performance DBMS for theIBM mainframe and compatible environments. CAIDMS/DB includes the DBMS itself and IDD, whichstores information about data and applications in adictionary.

CA IDMS/DB Analyzer. A utility product thatanalyzes the physical organization of a database andproduces reports that are useful for databaseplanning and tuning.

CA IDMS/DB Audit. A software tool that examinesthe physical integrity of a CA IDMS database,suggests corrective action, and fixes errors asdirected. For example, this tool detects fragmentedrecords and disconnected sets as well as othermaintenance problems.

CA IDMS/DB precompiler. See DML precompiler.

CA IDMS/DB Reorg. A software tool for physicallyreorganizing a CA IDMS database.

CA IDMS/DB trace facility. The CA IDMS/DBdebugging tool that you use to trace database callsin batch programs, utilities, compilers, and reports.

CA IDMS/DC. The CA IDMS teleprocessingmonitor. CA IDMS/DC controls the concurrentexecution of online applications and provides supportfacilities for the use of sophisticated terminals. CAIDMS/DC is fully integrated with CA IDMS/DB.

CA IDMS/DC Sort. An online sort utility for CICSand CA IDMS/DC environments that can sortinformation online regardless of the file structure ororiginal sequence.

CA IDMS DBOMP Transparency. A programinterface product that enables DBOMP databaseapplications to access a CA IDMS/DB database.Use of CA IDMS DBOMP Transparency requireslittle or no revision to these application programs.

CA IDMS DLI Transparency. A program interfaceproduct that enables DLI applications to access a CAIDMS/DB database. Use of CA IDMS DLITransparency requires little or no revision to theseapplication programs.

CA IDMS DDS. The CA IDMS software product thatcontrols communication between nodes in adistributed data processing network. Each node inthe network is a DC/UCF system.

CA IDMS Dictionary Loader. A CA IDMS softwareproduct used in conjunction with IDD. The CA IDMSDictionary Loader reads COBOL source programs toconvert file, record, and element descriptions into theDDDL source statements used to populate the datadictionary.

CA IDMS Dictionary Migrator. A software productthat automates the migration of entities from onedictionary to another.

CA IDMS DME. An online tool that simulates anISPF editor for editing IDD source modules.

CA IDMS DMLO. A utility product that executesDML commands interactively.

CA IDMS DQF. The CA IDMS product that givesyou quick and easy online access to the contents ofCA IDMS dictionaries. The menu structure of CAIDMS DQF allows you to find whatever informationyou need, without using complicated syntax.Cross-references are listed on the menus,eliminating a need for knowledge of dictionarystructure.

CA IDMS Enforcer. A utility product that isimplemented as a user exit to the DDDL compiler toenforce naming standards on all attempts to addentities to the dictionary.

CA IDMS interface module (IDMS). The modulethat initially receives all requests for CA IDMSservices from batch and DC/UCF applicationprograms. CICS application programs useIDMSCINT as an interface module.

CA IDMS Journal Analyzer. A data analysis facilitythat produces journal reports on database activity,journal displays, and audit reports.

CA IDMS Log Analyzer. A tool that producesreports on DC/UCF system and databaseperformance from information contained in the logfile. These reports reflect task-level activity.

CA IDMS Masterkey. A task initiation control facilityproduct for CA IDMS/DC. For example, you can use

14 CA IDMS Glossary

this product to assign task initiation streams to a PFkeys.

CA IDMS Online Log Display. The CA IDMSproduct that gives CA IDMS/DC and CA IDMS UCFusers online access to a full-screen display ofruntime events recorded in the CA IDMS log(DDLDCLOG).

CA IDMS Performance Monitor. A diagnosticproduct that provides comprehensive statistical,performance, and application data for DC/UCFsystems. See also application monitor, intervalmonitor, realtime monitor.

CA IDMS Presspack. The compression productthat optimizes database record or table compressionand decompression by using a data characteristictable (DCT) and Huffman compression techniques.See also IDMSCOMP, IDMSDCOM.

CA IDMS SASO (Standards AdministrationSystem Online). An online, full-screen editor thatenables access to and maintenance of documentsthat reside on the database.

CA IDMS Schema Mapper. A batch utility productthat produces database structure diagrams fromschema and subschema information stored in a CAIDMS/DB dictionary.

CA IDMS Server. The CA IDMS Server productprovides client/server connectivity to CA IDMSdatabases by implementing Microsoft's OpenDatabase Connectivity (ODBC) protocol and Sun'sJDBC protocol. ODBC access is provided forWindows client platforms. JDBC access is providedfor Windows client platforms and z/OS Unix SystemServices.

CA IDMS SQL. The CA IDMS product that allowsuse of the Structured Query Language (SQL) againsta CA IDMS/DB database either programmatically orthrough the CA IDMS Command Facility.

CA IDMS SQL Quick Bridge. A graphical userinterface (GUI) tool that runs under Windows andgenerates the source code for a table procedure.

CA IDMS SVC. The routine or module throughwhich programs running in other regions/partitionspass central version database requests to DC/UCF.DC/UCF returns confirmations or databaseinformation through the same SVC.

CA IDMS Task Analyzer. A CA IDMS/DC taskreport utility product that gathers program, dialog,task, and other statistics which it write to log andfrom which it generates reports.

CA IDMS TOTAL Transparency. A programinterface product that enables TOTAL databaseapplications to access a CA IDMS/DB database.Use of CA IDMS TOTAL Transparency requires littleor no revision to these application programs.

CA IDMS UCF. The software product that offersTP-monitor independence to users of CA IDMSonline products. This facility enables CAIDMS/DB-based applications to run withoutmodification under teleprocessing monitors otherthan CA IDMS/DC. Additionally, the distributedapplications feature of CA IDMS UCF provides thecapability of passing data between two systems.See also back end, front end.

CA IDMS VSAM Transparency. A programinterface product that enables applications that useVSAM file structures to access a CA IDMS/DBdatabase. Use of CA IDMS VSAM Transparencyrequires little or no revision to these applicationprograms.

CA IDMS Visual DBA. A tool that provides agraphical user interface-based facility for the CAIDMS database administrator. Creation andmaintenance of all CA IDMS object definitions arepossible from this single Windows-based tool. Thistool is a component of the CA IDMS/DB product.

CA OLQ. A product used by application developersand end users to view and report on the contents ofa CA IDMS/DB database through either anEnglish-like query language or SQL.

CAISAG. The CA Specify and Generate program isan installation utility used in the z/OS and MSP/EXenvironments to create site-specific installation jobcontrol for CA IDMS, CA IDMS Tools and CAEndevor/DB.

CALC key. A record element, or series ofconcatenated elements, designated as the symbolickey by which a record occurrence is stored in andretrieved from the database.

CALC location mode. A method of determining thetarget page for storage of a record in the database.The target page is calculated by means of a

Glossary 15

randomizing routine executed against the CALC keyin the record.

CALC overflow. See overflow.

CALC set. A system-owned internal set used byCA IDMS/DB to keep track of all records with alocation mode of CALC.

calculated storage. See CALC location mode.

call level interface. An API specified in terms offunction calls and parameter formats.

CALC utility. See IDMSCALC utility.

catalog. 1) The component of the dictionary thatcontains the SQL SYSTEM tables, physical databasedefinitions, and access module, database nametable, and DMCL load modules. The catalogcomponent consists of the DDLCAT, DDLCATX, andDDLCATLOD areas. See also user catalog. 2) Thedirectory of all information stored in CA ICMS and ofthe users who can access that information. Thecatalog is implemented in the data dictionary and isshared with CA IDMS/DB when both CA ICMS andCA IDMS/DB are installed.

catalog access passkey. In CA ICMS, a passkeythat allows access to catalog entities, permittingusers to access or manipulate the catalog structure.See also data access passkey.

catalog foundation. In CA ICMS, the corestructure of the catalog, generated at installation timeand when a new dictionary is created. Thefoundation establishes a fully functional catalog.

catalog reports. Eight standard reports thatdescribe the contents of the CA ICMS catalog. Seealso DREPORTs.

category. Under centralized security, resources thatyou group for efficiency in granting privileges. Forexample, you can categorize all load modules, tasks,and queues associated with a particular applicationand treat them as a single category for the purposeof assigning privileges.

CCDB. See Change Control Database (CCDB).

CCI. A CA Common Service communicationsfacility, the Common Communications Interface,CAICCI, that enables communications between CAsolutions. DC/UCF systems use CCI to enable

communications between DC/UCF systems locatedon different mainframes in a communicationsnetwork. CAICCI is also used by CA IDMS Server forcommunication to the mainframe from the PC.

CCI line. A communication line that uses CCI as acommunications access method. See communicationline.

CDMSLIB. The ddname (z/OS), filename (z/VSE),or linkname (BS2000/OSD) that identifies the CAIDMS/DB load (core-image) library in the DC/UCFsystem startup JCL.

centralized security administration. An approachto security that protects CA IDMS resources whetheror not an external security system is available,without using user exits to administer or enforcesecurity. If your site uses eTrust CA ACF2, eTrustCA Top Secret, or RACF, centralized securityinterfaces with these external security packages forthe protection of all securable CA IDMS resources.

central version. A CA IDMS system that enablesmultiple applications to access the databaseconcurrently. A central version controls access todata at the individual record (or row) level thusproviding integrity while maximizing concurrency. Italso provides automatic recovery in the event offailure.

central version mode. A mode in which thedatabase is accessed through the services of acentral version. This enables multiple applications toaccess and update the same database concurrently.All applications executing within a TP monitor(including DC/UCF) use central version services toaccess CA IDMS data. Batch applications canaccess data in central version or local mode. Seealso local mode.

central version runtime components. Thecomponents needed for a central version runtimeenvironment. These are a system dictionary,application dictionaries, user databases, journals,and the following runtime areas: DDLDCLOG,DDLDCRUN, DDLDCSCR, SYSMSG.DDLDCMSG,and DDLSEC.

chained set. A linked list structure where eachrecord contains a pointer for locating the next recordin logical sequence. Optionally, each record cancontain a pointer to the prior record in the chain anda pointer to the owner of the set.

16 CA IDMS Glossary

Change Control Database (CCDB). The ChangeControl Database is a facility of CA Endevor/DBused to maintain a complete log of changes made todata dictionary entities as well as information aboutusers, entities, projects, workflow status, migrationactivity and security. CA Endevor/DB supports anynumber of data dictionaries, and a single CCDB canbe viewed as a logical extension of a particulardictionary.

change only. The method of CA IDMS DictionaryMigrator execution which limits selection to changedentities only.

check constraint. A type of domain constraint thatrestricts the values of a table's column to a rangethat satisfies a search condition.

checkout. In ADSA, ADSC, and MAPC, theprocess that controls concurrent access to anapplication, dialog, or map by multiple users, so thattwo users do not modify the same entity at the sametime. See also explicit checkout, implicit checkout.

checkpoint. A record in the journal file thatdescribes the status of one or more databasetransactions or transaction branches.

check-user task. A subtask started by DC/UCF todetect abnormally terminated batch external requestunits running under the central version.

child. A logical database design term that refers toa referencing table in SQL database design and amember record in non-SQL database design. Seealso parent, member record, referencing table.

CKPT checkpoint. A journal checkpoint that marksthe simultaneous successful completion of multiplebranches of a local transaction. This record is usedto coordinate the commit of a local transactioninvolving multiple branches.

class. In IDD, an entity type used to documentcategories of attributes. See also attribute.

CLEANUP utility statement. The utility thatphysically erases logically deleted records from all orsome areas in a database segment.

CLIST. A system task that invokes a command listmodule. See also command list.

cloned system. A central version that uses anothersystem's definition. A cloned system does not exist

as a generated system definition in the dictionary. Itis created by CA IDMS when a CV is started thathas been identified as one that can be cloned, usinga CV number reserved for cloning.

close cursor. The act of closing a cursor; that is,making the cursor unavailable to the program until itis reopened. See also open cursor.

clustering. In CA IDMS/DB, the storage mode bywhich a record occurrence is stored as close aspossible to another record occurrence to which it islogically related. The purpose of clustering is tominimize I/O by grouping record occurrences that arelikely to be accessed together. Clustering can beaccomplished through: a relationship, an index, theCALC location mode.

cluster overflow. See overflow.

code table. A table used at runtime to translateinternal codes in a record-to-screen display formatand vice versa. Code tables are defined through theDDDL compiler.

column. A named collection of occurrences of asingle data element (field). See also attribute, row,table.

column header. A page with an easily-recognizedformat that you use as a reference to burst and alignpages for wallpapering the CA IDMS SchemaMapper data structure diagram. Column headersseparate each column of the diagram when it isprinted out on successive pages.

Command Facility. A CA IDMS tool that you useto submit several types of CA IDMS statements,such as physical DDL, SQL, and utility statements.See also Online Command Facility (OCF), BatchCommand Facility (IDMSBCF)

command list. A module that contains a series oftask statements. You can define command lists toautomate frequently used routines. You use IDD todefine a command list. You execute the commandlist by using the CLIST system task. See alsoCLIST.

COMMIT. 1) A navigational DML commit statementthat causes affected database sessions to remainactive after completion of the statement. 2) An SQLcommit statement that may or may not cause theissuing database session to terminate depending on

Glossary 17

the options specified and the manner in which theSQL session was started. See commit statement.

commit operation. The process of making theeffects of a transaction permanent. If the commitoperation is successful, all database changes madeduring the life of the transaction are madepermanent, and one or more of the followingcheckpoints are written: COMT, CKPT, or DCOM.

commit statement. A statement that initiates acommit operation. A successful commit operationresults in making database changes permanent. Thefollowing are examples of COMMIT statements:COMMIT TASK, COMMIT RELEASE, and FINISH.

common system area (CSA). The part of theDC/UCF nucleus that defines system-wide datavalues.

common work area (CWA). The shared systemstorage, acquired during DC/UCF system startup,that has a storage id of CWA. Any task running inthe DC/UCF system can access this storage. Thecommon work area is used to store system-widedata that must be available to all tasks.

communication line. A DC/UCF system entityrepresenting a communications method throughwhich a system communicates with external entitiessuch as other DC/UCF systems, terminals, or TCP/IPclient or server applications. Each line is associatedwith a single communication access method.

compiler-directive statements. Statements codedin a program to instruct a compiler to perform aservice (such as to copy a source module from thedata dictionary into the program). Compiler-directivestatements in a program are ignored at runtime whenthe program is actually executed.

compiler options. Specifications that control theoperation of a given compiler or precompiler.

complete access path. In CA ICMS, a path thatincludes the owner name of the entity to beaccessed, the names of all folders associated withthe entity, and the entity name.

compression. The process of removing repeatingcharacters in data. Compression reduces theamount of data stored in the database and improvesdata transport efficiency between machines. CAIDMS/DB optionally compresses data stored on thedatabase using the IDMSCOMP database procedure.

Greater compression can generally be achieved byusing the CA IDMS Presspack product. See alsodecompression.

COMT checkpoint. A journal checkpoint that marksthe successful completion of a transaction branch. ACOMT checkpoint is written to the journal file duringa commit operation. It is similar to an ENDJcheckpoint record except that it enables work doneafter the commit operation to be recorded on thejournal file using the same LID value. See ENDJ,LID.

concatenated key. A key composed of multipleelements (that are not necessarily contiguous).These elements are used together to form a singlekey.

condensed segment. The portion of a CAIDMS/DB disk journal file that contains only beforeimages for active recovery units. Condensedsegments are created by the ARCHIVE JOURNALutility statement.

conditional expression. See selection criteria.

CONNECT. 1) The Command Facility or SQLstatement that establishes a logical connection to thenamed dictionary. 2) The navigational databaseaccess function that establishes a record occurrenceas a member of a set occurrence. The object recordmust be defined as an optional automatic, optionalmanual, or mandatory manual member of the set.

connection. The linking of two CA IDMS DDSnodes so that data can be passed between thenodes.

constraint. A restriction placed on data valueswithin a database. See also check constraint,referential constraint, unique constraint.

control block. A logical collection of related dataitems used internally by CA IDMS products atruntime; the piece of storage defined by a DSECT.

control break. In CA Culprit and CA OLQ, anautomatic procedure that provides intermediatesummary information, such as subtotals, when thesort-key field changes.

control commands. In CA ADS, the CONTINUE,DISPLAY, EXECUTE NEXT FUNCTION,TRANSFER, INVOKE, RETURN, LINK, and LEAVEprocess commands that instruct the runtime system

18 CA IDMS Glossary

to pass control from one dialog to another or to auser program during the execution of an application.

control key. A program function (PF) key orprogram attention (PA) key defined to activate aresponse or process at runtime. [Enter] and [Clear]are also considered control keys. See also programattention (PA) key, program function (PF) key.

control length. That portion of a record up to andincluding the symbolic key (CALC, sort, or indexkey). When the symbolic key consists of two or moreconcatenated fields, the control length extendsthrough the end of the last concatenated field.

CONVERT PAGE. The Convert Page Utilitychanges the page range for an area or the maximumnumber of records that can be stored on a page ofan area.

coordinate position. In CA IDMS Schema Mapper,a combination of two numbers, which appears in theCross-Reference Report, that is used to find theexact location of a record block in a CA IDMSSchema Mapper Diagram. The numbers refer to theposition of the upper left corner of each record blockin the diagram. The position is numbered in units ofcharacter spaces, with the upper left corner of thediagram being the origin (0,0). The first number tellshow many character spaces the record block is fromthe left side of the diagram. The second numbertells how many character spaces the record block isfrom the top of the diagram.

coordinated commit. A commit operation involvingmultiple transactions or transaction branches(possibly distributed across multiple resourcemanagers) in which all changes are committed or allchanges are backed out.

coordinator. In a two-phase commit, thetransaction manager that initiates the commitoperation and is responsible for its overall outcome.A coordinator is sometimes referred to as an initiator.See also participant.

CORP. In CA ICMS, the name of the catalog.CORP also serves as the catalog entity thatrepresents the corporation as a whole. See alsocorporate catalog, private catalog.

corporate catalog. In CA ICMS, the portion of thecatalog that contains data controlled by thecorporation (as opposed to data controlled byindividual users). See also CORP, private catalog.

corporate property. All objects and folders in CAICMS owned by the corporation (that is, stored in thecorporate catalog).

CREPORTs. Reports that provide information onDC/UCF systems and their associated entities, asdefined in the data dictionary.

cross-reference processor. A component of theDictionary Loader that analyzes the output of theprogram processor to track all references to dataelements throughout a system of programs. Thecross-reference processor outputs cross-referenceinformation about the system of programs beinganalyzed.

Cross-Reference Report. A report that containsthe descriptions of sets, the name of each record,and location (coordinate position and page identifier)of each record block in the CA IDMS SchemaMapper data structure diagram. The report includesthe name and unique set number of each set andindex in the diagram. It also contains the names andlocations, in the diagram, of the owner and memberrecords of each set.

CSA. See common system area (CSA).

CTABGEN macro. A macro you use to assignactivity numbers to DCMT commands for thepurpose of securing DCMT commands.

currency. A technique that maintains the databasekeys of the most recently accessed records toindicate run-unit positioning in the database.

currency block. The control block that maintainscurrency information on all database records used byan application program. In CA ADS, a currencyblock is created for each application level thataccesses the database.

current of area. The most recently accessedrecord occurrence in a given database area. TheDBMS maintains current of area for each areaaccessed by the application program.

current of record. The most recently accessedrecord occurrence of a given record type. The DBMSmaintains current of record for each record typeaccessed by the application program.

current of run unit. The record occurrence mostrecently accessed by the application program. The

Glossary 19

DBMS maintains a current of run unit for eachtransaction.

current of set. The most recently accessed recordoccurrence in a given set. The DBMS maintainscurrent of set for each set accessed by theapplication program.

current schema. The SQL schema used in an SQLsession. You can explicitly specify a schema in theSET SESSION statement or use the default schemaestablished by the user profile, system profile, or aDCUF command.

cursor. An SQL-programming construct that is usedto process data in a result table. The cursor definesthe result table, and the program can retrieve eachrow of the result table one at a time with a FETCHstatement. See also global cursor, external cursor,shared cursor, updatable cursor.

cursor position. The cursor row whose values areavailable to the program.

CURSOR STABILITY isolation level. The isolationlevel of an SQL session that guarantees readintegrity. That is, all data accessed by the session isin a committed state and the most-recently accessedrow of an updatable cursor is protected from updateby other transactions while it remains current. Seealso TRANSIENT READ isolation level, isolationlevel.

CV. See central version.

CVNUMBER. A parameter of the DC/UCFsystem-generation SYSTEM statement.CVNUMBER allows you to specify a number thatidentifies the DC/UCF system to the CA IDMS SVC.

CWA. See common work area (CWA).

data. Facts and numbers that can be collected andprocessed. The processing of data yieldsinformation that is meaningful to an organization.

data access passkey. In CA ICMS, a passkey thatallows access to objects. See also catalog accesspasskey.

data area. See table data area.

database. A storage facility in which all data iscentralized and arranged independently ofapplications; a named collection of data tables.

database administrator (DBA). The individualand/or staff responsible for implementing andmaintaining the database.

database analysis utility. See IDMSDBAN utility.

database buffer. The storage space in memorythat holds database pages while CA IDMS/DBaccesses information on those pages. You define abuffer as part of the DMCL. Each buffer isassociated with one or more database files. Seealso buffer, journal buffer, record buffer.

database function. Services requested byapplication programs and performed by the DBMS toaccess and maintain the database.

database I/O. The input/output operationsperformed by the DBMS on the physical database.

database key (db-key). A unique identifierassigned by CA IDMS/DB to each record occurrencewhen it is stored in the database. The database keyconsists of the record's database page number andline index.

database-key format. The structure of thedatabase keys that identify the records in a givendatabase. A segment of a database can have onlyone database-key format. A database key is a 32-bitfield that contains two values: the record's pagenumber and its line index. The page number canoccupy 20 through 30 bits of the database key. Theline index can occupy 2 through 12 bits of thedatabase key. A synonym for database-key formatis radix.

database management system (DBMS). Thesoftware component that performs the physicaldatabase access, handling all database input/outputand space management functions.

database name. An entity that identifies thesegments to be accessed as part of the logicaldatabase. One or more database names comprise adatabase name table.

database name table. An entity associated with aDMCL that is used at runtime to map the logicaldatabase definition to one or more segments in theDMCL. The definition of a database name tableincludes one or more database names.

20 CA IDMS Glossary

database node. The node name of the DC/UCFsystem.

database page. See page.

database procedure. In CA IDMS/DB, aspecial-purpose subroutine designed to performpredefined programming functions, such as datacompression or data validation. The DBMS invokesa database procedure according to a record'sschema definition.

database record. A group of related data fieldsdefined in a non-SQL schema and stored in a CAIDMS/DB database. Database records function asthe building blocks of logical records.

database resource. Within centralized security, anentry associated with the definition or access to adatabase. See also global resource, systemresource.

database session. An association between anapplication and a CA IDMS database that can beused to retrieve and update data.

database status code. See status code.

database transaction. A database transaction is aunit of recovery representing work done by one ormore database sessions. All access to CA IDMSdata from within a database session is done underthe control of a database transaction. See alsodatabase session, local transaction, distributedtransaction, transaction branch.

data characteristic table (DCT). In CA IDMSPresspack, a table that contains either customized orgeneric information on data. The table is used tooptimize record and table compression anddecompression.

data communications administrator (DCA). Theindividual and/or staff responsible for implementingand maintaining the DC/UCF system.

Data Definition Language (DDL). The statementsthat define the logical and physical components of aCA IDMS/DB database definition (that is, the SQLschema or non-SQL schema, DMCL, subschema,and database name table). DDL is also used forData Description Language and the terms areinterchangeable. See Data Description Language(DDL).

Data Description Language (DDL). Thestatements that define the logical and physicalcomponents of CA IDMS/DB database definition (thatis, the SQL schema or or non-SQL schema, DMCL,subschema, and database name table). DDL is alsoused for Data Definition Language and the terms areinterchangeable. See Data Definition Language(DDL).

data dictionary. See dictionary.

data dictionary administrator (DDA). Theindividual and/or staff responsible for implementingand maintaining the data dictionary.

Data Dictionary Definition Language (DDDL).The IDD statements used to define the contents ofthe data dictionary.

data dictionary reports utility. See IDMSRPTSutility.

data dictionary schema. The schema(IDMSNTWK) that describes the data dictionarydatabase.

data field. In the Mapping Facility, a map field thatdisplays the value (if any) of a record elementassociated with the map field and, optionally, allowsthe terminal operator to input data.

data flow diagram (DFD). A diagram that showsthe flow of data to and from a particular function orset of functions. Data flow diagrams are used duringthe logical phase of database design.

data item. See attribute, element.

Data Manipulation Language (DML). Statementsby which application programs access andmanipulate the contents of a CA IDMS/DB database.DML statements can be coded in COBOL, PL/I, andAssembler application programs. See alsopath-DML commands, navigational DML, SQL DML.

data model. The theoretical basis of a databasesystem.

data security. The protection of data againstaccidental or intentional disclosure to unauthorizedpersons, unauthorized modifications, or destruction.

data services interface (DSI). An interfacebetween an application requesting CA IDMS servicesand the component providing the services. If

Glossary 21

necessary the DSI layer will use the datacommunications architecture for forwarding requeststo a separate address space or remote node.

data sharing. The CA IDMS feature that allowsmultiple CA IDMS central versions to share updateaccess to the same database areas. This featurerequires the IBM Parallel Sysplex environment.

Data Sharing Group. A named collection of CAIDMS systems in an IBM parallel sysplexenvironment. CA IDMS systems that participate in aData Sharing Group may share update access to adatabase, broadcast commands to all members ofthe group, share queues and enqueue commonresources, and monitor and report on all members ofthe Data Sharing Group.

data structure diagram. A graphic representationthat illustrates the components and relationshipswithin a database, including records, sets, and areas.See also record-type diagram.

data table. Presentation of data as a series of rowsand columns. A data table can be manipulated withthe three relational operations: select, project, andjoin. In CA IDMS/DB, a data table can be physicallystored in the database or it can be a view of othertables in the database. See also table, view.

data transfer services (DTS). A component of theCA IDMS database communications architecture thatcalls the name server to determine the location ofthe target resource and, if necessary, forwards therequest to the distributed node services (DNS)component for routing.

data type. A set of values that share processingcharacteristics. For example, the set of all integersis a data type.

DBA. See database administrator (DBA).

DBA group. In CA ICMS, a catalog-foundationgroup entity whose members share administrativeauthority over the catalog.

DBAK checkpoint. A journal checkpoint that marksthe abnormal completion of a distributed transaction.A DBAK checkpoint is written to the initiator's journalfile during the first phase of a two-phase commitoperation as soon as it determines that thetransaction's changes should be backed out. ADBAK checkpoint is written to a participant's journalfile when it is informed that its changes should be

backed out. See coordinator, participant, two-phasecommit.

DBCS. See double-byte character set (DBCS).

DBGROUP. A named collection of central versionsthat provide access to a common set of data. ADBGROUP is used in conjunction with dynamicdatabase routing to facilitate load balancing in aparallel sysplex environment. A central version is agroup member if the DBGROUP is defined in thesystem's database name table. See dynamicdatabase session routing.

db-key. See database key (db-key).

DBMS. See database management system(DBMS).

DBNAME. See database name.

DBNODE. See database node.

DBTBGEN macro. A macro used by onlinedebugger to assign activity numbers to onlinedebugger functions.

DCA. See data communications administrator(DCA).

DCE. See dispatch control element (DCE).

DCMT task. A system task that invokes a DCmaster terminal (DCMT) function. DCMT functionsare used to monitor and control various aspects ofthe DC/UCF system at runtime.

DCOM checkpoint. A journal checkpoint that marksthe successful completion of a distributedtransaction. A DCOM checkpoint is written to theinitiator's journal file at the start of the second phaseof a two-phase commit operation. A DCOMcheckpoint is written to a participant's journal filewhen it is informed that its changes should becommitted. See also coordinator, participant,two-phase commit.

DCPARM macro. A macro that describes theDC/UCF system to be started. It defines the versionnumber of the DC/UCF system, associates thesystem with the DMCL module, and provides othersetup information for the system.

DCPROFIL task. A system task that displayssystem information, such as installation options,

22 CA IDMS Glossary

system resource usage, the system exits used, theADSO and OLQ configurations, and the optionalAPARs currently applied.

DC system. A database/data communicationssystem that includes CA IDMS/DB and CA IDMS/DC.

DCSYSTEM. The name that, when combined with aversion number, uniquely identifies an occurrence ofa system added to the data dictionary through thesystem-generation compiler.

DCT. See data characteristic table (DCT).

DC/UCF nucleus. See nucleus.

DC/UCF system. A general term for a system thatis either a CA IDMS/DC system or a CA IDMS UCFsystem. A DC/UCF system provides both databaseand data communications services.

DC/UCF system reports. See CREPORTs.

DCUF task. A system task that invokes a DC/UCFuser function. User functions perform supportservices for the terminal user at runtime, such assending messages or altering profile information.

DDA. See data dictionary administrator (DDA).

DDDL. See Data Dictionary Definition Language(DDDL).

DDDL compiler. An IDD-supplied program thatstores DDDL descriptions in the data dictionary.

DDL. See Data Description Language (DDL).

DDLCAT dictionary area. A dictionary area thatcontains definitions of physical databases (segments,DMCLs, and database name tables); at sites with theSQL option, contains definitions of SQL entities(tables, constraints, indexes, and so on).

DDLCATLOD dictionary area. A dictionary areathat contains DMCL load modules, database nametable load modules, and access modules at siteswith the SQL option.

DDLCATX dictionary area. A dictionary area thatcontains indexes defined on entities stored in theDDLCAT area.

DDLDCLOD area. A dictionary area that containsload modules associated with entities contained inthe DDLDML area; for example map load modules,subschema load modules, and dialog load modules.See also load area.

DDLDCLOG area. The log runtime area. The logarea contains central version log records when thelog file for the central version is assigned to thedatabase. See also log, log file.

DDLDCMSG area. The message area of the datadictionary. The DDLDCMSG area contains messagetext identified by a message id. The area containsmessages loaded at installation as well as usermessages added through the DDDL compiler.

DDLDCRUN area. The queue runtime area. TheDDLDCRUN area contains the queue work recordsused by CA-supplied tools and online user programs.

DDLDCSCR area. The central version scratchruntime area. The DDLDCSCR area containsscratch work records used for temporary storage ofdata that can be accessed by CA-supplied tools andonline user programs.

DDLDML area. The area of the dictionary thatcontains definitions of DC/UCF systems, non-SQLschemas and subschemas, maps, dialogs, sourcemodules, records and elements, IDD users, andclasses and attributes.

DDLOCSCR area. The local mode scratch areathat contains runtime scratch records used byCA-supplied tools and user programs issuing SQLrequests in local mode.

DDLSEC area. The runtime area that contains userand group information.

DDS line. A communication line that allows oneDC/UCF system to communicate with another. Seealso communication line.

DDS network. Multiple DC/UCF systems connectedby CA IDMS SVCs or DDS lines.

DDS node. A DC/UCF system that participates in aCA IDMS DDS network. See also host node, targetnode, local node, node.

deadlock. An unresolvable contention for the use ofresources.

Glossary 23

deadlock prevention element (DPE). UnderDC/UCF, the control block used to detect deadlocksituations.

debugger. The online facility used to detect, trace,and resolve programming errors in programs thatoperate in a DC/UCF environment.

debug local block (DLB). The control block usedin a debugging session.

declaration module. In the CA ADS dialogcompiler, a module used under the SQL option todeclare cursors and to issue global WHENEVERstatements. The statements in a declaration moduleare not executed. They are compiler directives usedby the CA ADS dialog compiler at dialog compilation.

decompression. The process of expandingcompressed data. To decompress a databaserecord, you use CA IDMS Presspack or theIDMSDCOM database procedure. See alsocompression.

default. A preset value for a given option. A defaultvalue is used automatically unless an overridingvalue is explicitly specified.

default access module. The access moduleassociated with the application program issuing thefirst SQL statement executed within the SQLsession. See also access module.

default dictionary. The dictionary accessed by CAIDMS tools if you do not specify a dictionary by othermeans such as using a DCUF SET DICTNAMEcommand or CONNECT statement. To define adefault dictionary to the runtime environment, includea subschema mapping in the database name tableassociated with the runtime DMCL for the IDMSNWKsubschemas.

default ready mode. A default ready mode for anarea specified in a subschema definition. Thedefault mode determines the mode in which the areais to be readied for programs using that subschema.Therefore, the programs do not need to issue aREADY command for the area. However, if theprogram issues a READY command for one area, itmust issue a READY command for all areas to beaccessed.

definition area. See table definition area.

definition privilege. Under centralized security, aprivilege that allows a user to manipulate thedefinition of certain resources. See also accessprivilege, administration privilege.

DELETE statement. 1) An SQL database accessstatement that deletes one or more rows from atable. 2) A DDDL command that removes one ormore entity definitions from the dictionary.

derivation. The process of creating a view of datatables in the database. See also data table, view.

described statement. A dynamically-compiled SQLstatement for which the SQLDA contains information.

destination. An IDD entity type used to documentgroups of users or logical terminals as a singlelogical destination within a teleprocessing system.

detail area. The portion of a pageable map that islocated across the middle of the screen. The fieldsin the detail area define the detail occurrences forthat map.

detail occurrence. On a pageable map, eachoccurrence of the set of map fields defined in thedetail area. The runtime system determines howmany detail occurrences of this set of fields can fit inthe detail area of each page.

development center. An organizational structure,typically within an MIS department, geared towardthe development of high-speed, high-volumeproduction applications.

DFD. See data flow diagram (DFD).

DFGT checkpoint. A journal checkpoint that marksthe end of a distributed transaction. It is written to acoordinator's or participant's journal file at the end ofa two-phase commit operation, but only if some otherdistributed checkpoint (DCOM, DBAK, DIND, orDPND) had previously been written for thetransaction.

dialog. In CA ADS, an executable module thatperforms a unit of work in an application. A dialog isconstructed from other modules, such as subschemamap, and process module definitions. A dialogtypically handles all processing associated with agiven online transaction. This includes accessingand updating the database and handling mapout andmapin operations.

24 CA IDMS Glossary

dialog components. The premap process module,response process modules, map, and subschemathat make up a dialog. Components are associatedwith the dialog during an dialog compiler session.

dialog function. In CA ADS, an application functionassociated with a dialog. The dialog performs theprocessing work required by the function. Forexample, the dialog for an employee update functionretrieves and updates employee records in thedatabase.

Most functions in a typical CA ADS application aredialog functions. See also application function,dialog.

dialog response process. See response.

dialog work record. Dictionary records that aredirectly associated with a CA ADS or CA ADS Batchdialog. Dialog work records can be used as workingstorage during processing. See also map workrecord.

dictionary. The central repository used by CAIDMS products for data definitions, modules,documentation, and runtime information. Thedictionary itself is a CA IDMS/DB database. Seealso ASF dictionary, default dictionary, sessiondefault dictionary, system dictionary.

dictionary name. The name of the dictionary beingaccessed.

dictionary node. In your DC/UCF communicationsnetwork, the logical name of the DC/UCF systemthat controls the data dictionary being used.

DICTNAME. See dictionary name.

DICTNODE. See dictionary node.

DIND checkpoint.. A journal checkpoint written to aparticpant's journal file to note that it is prepared tocommit its portion of a distributed transaction. Theparticipant will wait for a directive from thecoordinator as to whether to complete the commitoperation or to back out changes. See alsocoordinator, participant, two-phase commit.

DIRECT location mode. In CA IDMS/DB, thelocation mode that permits the user to suggest theactual database page on which a record will beplaced.

directory load utility. See IDMSDIRL utility.

DISCONNECT. The database access function thatremoves a member record occurrence from a set butdoes not delete the record from the database.DISCONNECT can only be issued for a record thatis defined as an optional member of a particular set.

dispatch control element (DCE). The DC/UCFcontrol block that is used to manage the dispatchingof tasks.

displacement. In CA IDMS/DB, a storage methodin which records are clustered a specified distanceaway from their owner records. Displacement canbe used for both VIA set member records andbottom-level index (SR8) records.

Distributed Database System (DDS). See CAIDMS DDS.

distributed node services (DNS). A component ofthe CA IDMS communications architecture thatmanages communications for remote data access.

distributed transaction. A transaction in whichchanges are made to resources controlled bymultiple resource managers.

distributed transaction identifier (DTRID). A16-byte value that uniquely and globally identifies adistributed transaction. A DTRID is composed of an8-byte node name and an 8-byte hexadecimal value.

DLB. See debug local block (DLB).

DMCL module. The module that relates the logicalstructure of the database to the physical files onwhich it resides. The DMCL describes a CAIDMS/DB runtime environment. It includes segment,journal, and buffer definitions and identifies thedatabase name table that the DBMS uses at runtimeto map a schema definition of the database tospecific segments.

DMCL Syntax Generator. A program, IDMSDMCC,that generates release 12.0 physical databasedefinitions from validated release 10.2 DMCL andschema definitions.

DML. See Data Manipulation Language (DML).

DMLA. The DML precompiler for Assemblerprograms.

Glossary 25

DMLC. The DML precompiler for COBOL programs.

DMLP. The DML precompiler for PL/I programs.

DML precompiler. A compiler that converts DMLstatements in the source program to host languagestatements, producing a source file that serves asinput to the host language compiler. For example, aCOBOL program with embedded navigational or SQLDML statements is submitted first to the DMLCprecompiler and then to the ANSI COBOL compiler.

domain. In CA IDMS/DB, the possible values for aparticular column in a table; for example, the 502-character state codes). See also security domain.

domain constraint. A constraint that restrictscolumn values. A column's data type restricts valuesto the data type of the column. A check constraintrestricts column values to a range of values thatsatisfies a search condition.

domain integrity. In CA IDMS/DB, the dataintegrity rule that enables users to define a set ofvalid values for a particular column in a data table.

double-byte character set (DBCS). A 16-bit(double-byte) character set that allows representationof a large set of graphic characters on theappropriate hardware. With DBCS, it is possible tobuild applications for Japanese, Chinese, andKorean users.

download. The transfer of data from CA ICMS to apersonal computer or minicomputer.

DPE. See deadlock prevention element (DPE).

DPND checkpoint. A journal checkpoint that marksan interim result for a distributed transaction. ADPND checkpoint may be written for severalreasons, such as when a participant is forced toheuristically complete a transaction or when acoordinator is unable to communicate with one ormore of its participants. See also coordinator,participant, two-phase commit.

DREPORTs. Reports that provide information onentities stored in the DDLDML area of the dictionary.

DTRID. See distributed transaction identifier.

duplicate names. Identical names assigned to twoor more catalog entities.

duplicates options. In a non-SQL schema, theoptions that determine how record occurrences withduplicate key values are stored.

duration. In the SQL option, a value thatrepresents a time interval. These can be: labeleddurations, which represent a specific unit of time (forexample, 10 MINUTES represents 10 minutes); dateduration, which denotes an interval of years, months,and days; and time duration, which represents aninterval of hours, minutes, and seconds.

dynamic database session routing. A feature thatallows the dynamic selection of the node to which adatabase session is to be connected. The selectionis made by determining which CV in the DBGROUPhas the CPU cycles available to service the request.This feature requires the IBM Parallel Sysplexenvironment and must be used in conjunction withthe Data Sharing feature in order to dynamicallyroute update requests. See also DBGROUP.

dynamic program definition. The process ofdefining a program to DC/UCF at runtime through aDCMT VARY DYNAMIC PROGRAM command. Thedefinition exists only for the current execution of thesystem.

dynamic SQL. An SQL statement that is not knownto the program at precompile time and therefore iscompiled dynamically when the program executes.

dynamic system monitor. An online facility thatallows you to examine DC/UCF system activitybased on a time interval. The dynamic systemmonitor is invoked by the task code OPER.

dynamic task definition. The process of defining atask to the DC/UCF system at runtime by means ofthe DCMT VARY DYNAMIC TASK command. Thedefinition exists only for the current execution of thesystem.

ECB. See event control block (ECB).

edit table. A list of single values or ranges ofvalues that are valid for a data field. Edit tables aredefined through the DDDL compiler and are usedduring automatic editing of maps.

element. 1) The smallest meaningful unit of datawithin an organization. Elements are also known asfields or data items. 2) An IDD entity type used todefine group or elementary data elements. Elementscan participate in records built by the DDDL

26 CA IDMS Glossary

compiler, by the CA IDMS/DB schema compiler, or inmaps built by the DC/UCF mapping compiler. Theycan also exist independently in the data dictionary.3) The database records that participate in a logicalrecord. See also record element.

ELEMENT selector. In LRF, a SELECT clausedescriptor that associates a logical-record elementwith a particular path. At runtime, the path isselected when a program WHERE clause requestsany field in the named element.

emulated APPC. CA IDMS emulating software forthe PC and mainframe that allows CA ADS dialogsexecuting on a PC with a 3270 emulator card toemulate advanced-program-to-programcommunication (APPC) with the DC/UCF system.

encompassing session. A database session underwhich a subordinate session is initiated. See alsodatabase session, subordinate session, peersession, top-level session.

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

entity. 1) A particular category or type of item in thedata dictionary (such as a record, user, program,map, or dialog). 2) An item or idea from anapplication environment that is represented in thedatabase by a record type.

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

entity-relationship (E-R) diagram. A graphicaldescription of two or more entities in a database thatshare a relationship.

entity type. An IDD-defined category of informationin the data dictionary that provides a template forsimilar data. Examples of entity types arePROGRAMS, RECORDS, and USERS.

entity integrity. In CA IDMS/DB, the data integrityrule used to ensure that each row of a data table hasa unique primary key value that is not binary zerosor spaces.

entry point. 1) An IDD entity type that describesprogram entry points. 2) The entity that serves as a

gateway for CA IDMS Dictionary Migrator to theentities that are to be extracted from the sourcedictionary. You specify the entry point in theEXTRACT statement.

entry sequencing. In CA IDMS/DB, a method forstoring rows in sequential order in the database,based on an index.

E-R diagram. See entity-relationship (E-R) diagram.

ERASE. The navigational database access functionthat deletes a record occurrence from the databaseand, where appropriate, deletes records subordinateto it.

ERASE logical record. The LRF database accessfunction that deletes a logical-record occurrence fromthe database.

ERASE path group. A collection of paths(predefined in a logical-record subschema) designedto service application programs that request anERASE 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 thatcomplies with the IBM European standard: DATE asdd.mm.yyyy and TIME as hh.mm.ss.

EVALUATE command. In LRF, a command thatdetermines whether an expression is true or false.Based on the result, you can direct LRF to performspecific path logic.

event control block (ECB). A control block used tocontrol the sequencing of events within the DC/UCFsystem. At runtime, DC/UCF associates an internalECB with each resource in use by a task. The ECBis used when one task requests a resource in use byanother task. The requesting task must wait until theusing task posts the ECB to indicate that theresource has been freed. An external ECB is postedby the operating system.

exclusive lock mode. A logical lock mode placedon both areas and record occurrences to protecttransactions from accessing data that is beingupdated by the issuing transaction. An exclusivelock placed on an area implies an exclusive lock on

Glossary 27

all records in the area. See also share lock mode,null-lock mode.

EXIT. The debugger command that leaves thedebugger control blocks intact when returning controlto DC/UCF.

EXPAND PAGE utility statement. The utility thatincreases the page size of an area by transferring adatabase file to a new file with an expanded blocksize.

explain. The act of describing the strategy used toaccess data in an SQL table by issuing an EXPLAINSQL statement against an access module.

explicit checkout. In ADSA, ADSC, and MAPC, acheckout that allows the application developer tocontrol an entity across repeated definition andcompilation sessions. The checkout is not releaseduntil this action is explicitly taken by the developer.See also checkout, implicit checkout.

explicit record locks. Record locks set by anapplication program to preserve a lock that wouldotherwise be released following a change incurrency. See also record lock.

explicitly connected session. An SQL sessioninitiated by a CONNECT statement. See also SQLsession.

exploded structure. The expansion of abill-of-materials structure that traces all records undera given record.

export. An IDMSRADM utility function that movesdata from the database to a sequential file.

extended run unit. In CA ADS, a run unit that iskept open (in certain cases) when a dialog passescontrol to another dialog or to a user program. Seealso run unit.

external cursor. A global cursor declared in oneprogram that is shared by another program, whereboth programs are included in the same accessmodule. You define an external cursor using theDECLARE EXTERNAL CURSOR statement. Seealso cursor, global cursor, shared cursor, updatablecursor.

external picture. The format of data as displayedon the terminal screen or in printed output. Anexternal picture can be defined in a record element

through the DDDL compiler, or defined dynamicallythrough CA OLQ or MAPC. Among other places,external pictures are used during automatic editing ofmaps.

external request element (ERE). In a DC/UCFsystem, a control block used to handle processingrequests that initiate from outside the DC/UCFregion/partition. EREs are used by external requestunits, the CA IDMS UCF front-end program, andnodes that communicate with the system through aCA IDMS SVC.

external request unit (ERU). A request forDC/UCF system services that originates outside theDC/UCF address space and uses the SVC tocommunicate between the application and theDC/UCF system. External request units are initiatedfor: CA IDMS batch and CICS programs requestingdatabase services, programs requesting DC/UCFservices using CA IDMS UCF front end modules,and DC applications requesting services from adifferent address space within the same mainframe(DC-to-DC communication). See also bulk externalrequest unit.

external procedure. See external SQL procedure.

external SQL procedure. A procedure or a tableprocedure.

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

external security. In CA IDMS centralized security,an external security system, such as eTrust CAACF2 and eTrust CA Top Secret, to which you canroute a request for a security check. See alsointernal security.

external user session. A logical connectionbetween a DC/UCF system and an applicationexecuting outside that DC/UCF system. An externaluser session is initiated when the application initiatesthe first request for services within the DC/UCFsystem and is terminated when the last serviceinitiated by the application is terminated. An externaluser session can use the following communicationmethods: external request units, DDS, or LU 6.2.

external wait time. The amount of time theDC/UCF system waits for an external user session toissue a request before assuming that the applicationhas terminated.

28 CA IDMS Glossary

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

Extract Journal utility statement. The utility thatextracts the most recent AFTR image for each dbkeyrecorded on an archived journal file and writes it toan extract file. The extract file can later be used asinput to a ROLLFORWARD command for a "quick"recovery of a database area or file.

extract path. The route CA IDMS DictionaryMigrator follows through the dictionary's setconnections from the entity specified in theEXTRACT statement to all of its related components.

factotum task. A task started by the DC/UCFsystem to perform a system service for a user task.Examples are tasks that handle map pagingsessions and tasks that handle line I/O sessions.

FASTLOAD utility statement. In a non-SQLdefined database, the utility that loads data.

fastload. A service performed by the FASTLOADutility statement. FASTLOAD loads user records intothe database according to specifications of auser-written program.

FAST mode. An optional mode of execution inADSC, ADSA, MAPC, and user-written applicationsin which control is passed directly to the nextsequential screen when a transaction is successful.See also STEP mode.

fast mode threshold. The point at which the CAADS runtime system writes record buffer blocks(RBBs) and statistics control blocks to the scratch(DDLDCSCR) area across a pseudo-converse. Theruntime system invokes this feature only when thenumber of bytes used by these control blocksexceeds the specified threshold. See alsorelocatable storage, relocatable threshold.

FDB. See fixed dialog block (FDB).

FETCH statement. An SQL database accessstatement that retrieves values from the result tableassociated with a cursor and places them in hostvariables or a bulk buffer.

field. See attribute, element.

field level help. Help text associated with a datafield by means of the online or batch map compilers,and which is displayed when the help key defined forthe map is pressed either with the cursor positionedin a data field. See also help facility, map level help.

field mark. The default special character used on3270-type terminals to define the beginning of a mapfield.

file. 1) In CA IDMS/DB, a logical unit of databasestorage that has a one-to-one relationship with adirect-access storage device. The relationship isestablished with the ASSIGN TO clause of theschema DDL definition. 2) In IDD, an entity type thatrepresents card, tape, and other nondatabase files.

file organization. A method of ordering recordswithin a file. CA Culprit handles input fromphysical-sequential, indexed-sequential, card, andvirtual storage file types.

FIND. The navigational database access functionthat locates a record occurrence in the database.Once the record occurrence is found, the applicationprogram can initiate a GET function to copy thecontents of the record occurrence from the databaseto variable storage. See also GET.

FINISH. A navigational DML commit statement thatcauses affected database sessions to terminate. Seealso commit statement.

first functional call. The first database accessrequest passed by a database session to CAIDMS/DB at program execution time.

FIX ARCHIVE utility statement. The utility thatrewrites a tape journal file; for example, to make thetape journal file in use at the time of an abnormalsystem shutdown usable by the ROLLBACK utility.

fixed dialog block (FDB). In CA ADS, the dialogload module generated in the dialog compiler for useby the runtime system when a dialog is executed.

fixed-length compressed record. A record of fixedlength that is compressed through a specifiedcompression routine. Although the length of therecord is fixed from the point of view of userprograms, compression makes it internally variable.

FIX PAGE utility statement. The utility thatverifies, and optionally modifies, the contents of adatabase page.

Glossary 29

flow of control. In CA ADS, the way control ispassed from one application function or dialog toanother at runtime. Runtime flow of control isdetermined by user requests or runtime events,based on specifications made at definition time.

folder. In CA ICMS, a catalog entity used torepresent a collection of related information. Folderscan include objects and other folders.

footer. The final entry on each page of thedatabase. The footer is 16 bytes long and containsthe page number and other information about agiven page.

footer area. The portion of a pageable map that islocated across the bottom of the screen. Fields inthe footer area are displayed whenever the map isdisplayed.

foreign key. In logical database design, an attributeof an entity or relationship that is also used as theprimary key of another entity. A foreign key is usedto relate two data entities. For example, to relate theDEPARTMENT and EMPLOYEE entities, you mightdefine the DEPT ID attribute, which is the primarykey of the DEPARTMENT entity, as the foreign keyof the EMPLOYEE entity. See also primary key,secondary key.

forked set. See multiple-member set.

format. The textual content and textual organizationof record block, set, and index information in theCross-Reference Report or in the CA IDMS SchemaMapper data structure diagram. Also, the graphiccomponents of the diagram, such as the charactersused to draw record blocks, set connections, andarrows. You can control the format with the optionalOPTIONS, CHARDEF, DRECLINE, XRECLINE,DSETLINE, and XSETLINE statements; or CA IDMSSchema Mapper default format specifications candetermine all or part of the format.

formatting. The action of initializing database ordisk journal files into database pages or blocksaccording to information provided by the DMCL. Usethe FORMAT utility to format database and diskjournal files.

FORMAT utility statement. The utility thatprepares a database file, area, segment, or a diskjournal file for use by CA IDMS/DB.

fragment. The portion of a variable-length recordthat is stored on a separate page from the rootsegment.

fragment chain. In CA IDMS/DB, the fragments ofa variable-length record. Each fragment is stored ona separate page. Each fragment contains a pointerto the next fragment and a 4-byte variable-lengthindicator that contains the length of the data portionof the entire record.

fragment interval. The frequency with which theDC/UCF system writes dummy segment (DSEG)records to the journal file. If the system crashes,DC/UCF uses these dummy records to determine theappropriate place for warmstart processing.

free-form data. In CA ICMS, data (in an object)that is not formatted as a data table. Free-form datais produced through the use of personal computersand includes text, graphs, and procedures.

free-form object. In CA ICMS, an object thatcontains free-form data (as opposed to a data table).A free-form object is also known as an unstructuredobject.

front end. 1) Under CA IDMS UCF, the host TPmonitor. The CA IDMS UCF front end establishesthe connection to the CA IDMS UCF back end;passes data to the back end as necessary; andtransfers control to the back-end system. Whenback-end processing is finished, it returns controland any necessary data to the CA IDMS UCF frontend. 2) The environment from which a remotedatabase request is issued.

function. In the context of SQL, an SQL function.

function code. See major code.

generation. 1) The process that creates and storesa load module in the DDLDCLOD or DDLCATLODareas of the dictionary. Load modules can begenerated by the application compiler, the dialogcompiler, the OCF compiler (DMCL, database nametable, and access module load modules), the DDDLcompiler (edit and code tables), the mapping facility(the map load module), and the subschema compiler(the subschema load module). 2) In ASF, theprocess that automatically creates one subschemadefinition, syntax module, and load module persubschema. A subschema is automatically createdfor each table that is defined and generated. 3) Insystem generation, the process of validating the

30 CA IDMS Glossary

system definition and updating the definition to makethe system executable.

generic key. A partial symbolic key. A generic keyis typically used to identify a group of related recordoccurrences. For example, given a symbolic keybased on a customer name field, an appropriategeneric key might consist of only the first letter ofthis field; the generic key could be used to accessrecord occurrences for all customers whose namesbegin with a certain letter.

GET. The navigational database access functionthat retrieves a located record (that is, the recordthat is current of run unit) by copying its contentsfrom the database to variable storage. Beforeissuing GET, an application program typically issuesthe FIND function to locate the appropriate recordoccurrence in the database. See also FIND.

global cursor. A cursor that can be used by otherapplication programs sharing the access module thatcontains the cursor definition. You define a globalcursor by including the GLOBAL keyword in theDECLARE CURSOR statement. See also cursor,external cursor, shared cursor, updatable cursor.

global DMCL. A DMCL module that defines alldatabase areas accessed by all transactionsexecuting under the CA IDMS/DB central version.See also DMCL module.

global locking. The use of a lock structure in theCoupling Facility in the IBM parallel sysplexenvironment for recording and managing globallocks. CA IDMS/DB uses global locks to control DataSharing group inter-member access to sharedresources.

global record. In CA ADS, a record that isavailable to all functions of an ADSA-definedapplication. A global record remains in the recordbuffer for the duration of the application, unaffectedby dialog control commands. Global records for agiven application are named on the Global Recordsscreen in the application compiler. See alsoADSO-APPLICATION-GLOBAL-RECORD.

global resource. Within centralized security, anentity that is defined in the user catalog and that isshared by all systems in the CA IDMS securitydomain. Types of global resources are user, group,and user profile. See also user profile, systemresource, database resource.

global response. In the CA ADS applicationcompiler, an application response that isautomatically valid for all application functions whenthe application is being defined or modified.

The application developer can selectively disable aglobal response from specific functions at definitiontime. At runtime, the response is available from allfunctions except for those functions from which it isdeselected. The opposite of a global response is alocal response.

graphics literal. A double-byte character set stringinterpreted without shiftin and shiftout characters.

group. In CA ICMS and in centralized security, acollection of related users. Groups can include usersand other groups.

grouped view. A view that includes a GROUP BYor HAVING parameter in the query specification.

group element. In IDD, an element that containssubordinate elements. For example, the DATEelement is a group element that contains elementsMONTH, DAY, and YEAR.

header. The first entry on each page of thedatabase. The header is 16 to 28 bytes long andcontains the page number and other informationabout a given page.

header area. The portion of a pageable map that islocated across the top of the screen. Fields in theheader area are displayed whenever the map isdisplayed.

help facility. The facility of the DC/UCF onlineMapping Facility that allows field and map level helpto be associated with a map. For maps with thissystem-defined help, help text is displayed when thehelp key defined for the map is pressed, transparentto the application program or dialog displaying themap.

help load module. In the online mapping facility ofDC/UCF, a load module created by MAPC orRHDCMPUT that includes the text of help messagesto be displayed when the help key defined for themap is pressed by the user. See also help facility,field level help, map level help.

home page. The first page on which CA IDMS/DBstores an entire record or the root portion of avariable-length record.

Glossary 31

host node. In a DC/UCF communications network,the DC/UCF system acting as the front end. Seealso front end, server node, target node.

host variable. A program variable that isreferenced in an SQL statement. Host variables areused to receive data retrieved from the database andto supply data to be added to the database.

host variable array. An array of host variables foruse in bulk processing.

hot backup. The process of backing up thedatabase while the database area(s) are beingupdated.

host teleprocessing monitor. The teleprocessing(TP) monitor that serves as the CA IDMS UCF frontend. The CA IDMS UCF front-end programexecutes as an application under the host TPmonitor.

IDB. See Information Database (IDB).

IDB Communications. The component of CAICMS that links personal and departmentalcomputers to the IBM mainframe.

IDB Mail Facility. The component of CA ICMS thatcontrols the exchange of electronic mail amongpersonal computer users.

IDB Manager. The component of CA ICMS that isused to perform catalog administrative functions.

IDBSYSTEM. In CA ICMS, a user entity in thecatalog foundation. This entity represents the overallsystem as the owner of system folders and objects.

IDD. The CA IDMS software product used to controland report on information stored centrally in the datadictionary. IDD uses the DDDL compiler to populateand maintain the dictionary.

IDMS. See CA IDMS interface module.

IDMS access mode. In CA OLQ, an access modethat you use to access SQL defined tables. Seealso OLQ access mode.

IDMSBCF program. See Batch Command Facility(IDMSBCF).

IDMSBSVC module. In BS2000/OSD systems, themodule that performs CA IDMS SVC services. Seealso CA IDMS SVC.

IDMSCALC utility. The CALC utility. IDMSCALCreturns to a calling program a suggested pagenumber for storage of a CALC record.

IDMS communications block. A communicationsblock through which the DBMS communicates with aprogram issuing navigational DML requests. Thedata description of the IDMS communications blockis named SUBSCHEMA-CTRL.

IDMSCOMP. In CA IDMS/DB, an installed databaseprocedure that compresses records to decrease theamount of data stored in the database. IDMSCOMPreplaces repeating characters, such as blanks, withcodes. IDMSCOMP is invoked by the DBMSaccording to specifications in the CALL orPROCEDURE clauses of the schema AREA andRECORD statements. See also IDMSDCOM, CAIDMS Presspack.

IDMSDBAN utility. The database analysis utility.IDMSDBAN examines and reports on areas, pages,line indexes, records, and sets.

IDMSDBIO module. The module that performs allCA IDMS/DB database and journal input/output (I/O).

IDMSDBMS module. The module that controls allCA IDMS/DB database access. IDMSDBMS controlsaccess both to your databases and to the datadictionary.

IDMS-DC communications block. The controlblock through which DC/UCF communicates with aprogram that requests navigational database anddata communication services. The data description ofthe control block is named SUBSCHEMA-CTRL.

IDMSDCOM. In CA IDMS/DB, an installed databaseprocedure that restores a compressed record to itsuncompressed form for use by an applicationprogram. IDMSDCOM is invoked by the DBMSaccording to specifications in the CALL orPROCEDURE clauses of the schema RECORDstatement. See also IDMSCOMP, CA IDMSPresspack.

IDMSDIRL utility. The directory load utility.IDMSDIRL loads into the dictionary the componentsrequired to describe the dictionary itself as well as

32 CA IDMS Glossary

the components that describe the securityinformation stored in the dictionary.

IDMSIDDC syntax converter. A program thatreads a COBOL source program and/or one or moreCOBOL copy books and converts FILE SECTION 01and subsequent level statements to DDDL ADDRECORD statements.

IDMSIDDP syntax converter. A program that readsone or more PL/I copy books and converts the datastructures in the DECLARE statements to DDDLADD ELEMENT and ADD RECORD statements.

IDMSLBLS procedure. A procedure providedduring CA IDMS installation at a VSE/ESA site. Itcontains the file definitions for: dictionaries, sampledatabases, disk journal files, the SYSIDMSparameter file.

IDMSLOOK utility. The load module print utility.IDMSLOOK reports on the contents of selected loadmodules.

IDMS module. See CA IDMS interface module.

IDMSNTWK. The schema that describes thedictionary database. The IDMSNTWK schema isprovided at installation; unlike user schemas, it is notcompiled through the schema compiler, but is loadedby IDMSDIRL.

IDMSNWKA subschema. A dictionary subschema.IDMSNWKA is added to the data dictionary, alongwith the IDMSNTWK schema, by the IDMSDIRLutility.

IDMSOCKI. The CA IDMS socket programming calllevel interface module.

IDMSOPTI module. An optional module thatsupplies database-related information to the batchinterface. At runtime, the batch interface orTP-monitor interface module (for non-UCF programs)reads parameters from the IDMSOPTI module.These parameters determine whether the applicationcan use central version database services and, if itcan, the DC/UCF system the application can access.

IDMSPASS utility. In CA IDMS Presspack, theutility that collects statistics on the characteristics ofyour data and builds a custom data characteristictable for use in data compression anddecompression.

IDMSR-AREA. The ASF table definition area that isprovided with the installation of CA IDMS/DB or CAICMS. ASF uses this area to store definitions ofdata tables.

IDMSR-AREA2. The default name for the ASF datatable area provided with the installation of CAIDMS/DB or CA ICMS. ASF uses this area to storedata associated with ASF data tables.

IDMSRPTS utility. The data dictionary reportsutility. IDMSRPTS produces reports on the contentsof the data dictionary (such as schema-relatedinformation).

IDMSR schema. The schema that describes thedatabase areas used by ASF. The IDMSR schemais provided with the installation of CA IDMS/DB orCA ICMS. This schema is stored in the ASFdictionary.

IDMSRSTC utility. The schema compare utility.IDMSRSTC generates IDMSRSTT macro statementsthat describe the changes to be made whenrestructuring a database.

IDMSSCON utility program. A utility program thatconverts release 10.0 subschema load modules torelease 12.0 subschema load modules.

IDMS-STATUS routine. An error-checking routinecontained in the data dictionary and copied into theprogram by the DML compiler to abend the programif a nonzero value is present in the ERROR-STATUSfield.

IDMSUNPS utility. In CA IDMS Presspack, theutility that decompresses journal images of recordsthat were compressed with CA IDMS Presspack.

IJMP. An abbreviation for the CAIIJMP program.This program is used to generate the JCL needed toinstall CA IDMS system software products underz/OS, z/VSE.

implicit checkout. In ADSA, ADSC, and MAPC, acheckout that is implied by an application developerbeginning work on an entity, and which terminateswhen the entity is successfully compiled. See alsocheckout, explicit checkout.

imploded structure. The expansion of abill-of-materials structure that traces all recordsabove a given record.

Glossary 33

import. In CA ICMS, the function that moves objectdefinitions and data from a sequential file to thedatabase and data dictionary. The import function isimplemented through the IDMSRADM utility.

inactive interval. The amount of time the DC/UCFsystem permits an online task to wait for a resourcebefore abending the task.

incremental lock acquisition mode. A lockacquisition mode for SQL sessions that delaysplacing a lock on an area until the first statement thatrequires access to the area is executed by thesession within a transaction. See also preclaim lockacquisition mode.

index entry. In CA IDMS/DB integrated indexing,the portion of an SR8 system record that consists ofan index pointer for a record occurrence (for anunsorted set) or of an index pointer either for arecord occurrence or for another SR8 system record(for a sorted set). The index pointer is the db-key ofa member record occurrence.

index ID. A numeric identifier assigned to anSQL-defined index to uniquely identify it within anarea.

indexed relationship. An index structure thatpoints each occurrence of a parent entity to theassociated child entity occurrences.

indexed set. A database structure that can be usedto physically link related record occurrences togetheror to provide alternate access to a record. Anindexed set, a pointer array associated with eachowner occurrence contains the db-keys of all relatedmember record occurrences. See also user-ownedindexed set, system-owned indexed set.

indexing. A technique that uses a list of keys andpointers to determine the location of a record in thedatabase. Indexes allow for quick access byexact-key or generic-key search. In CA IDMS/DB,indexes can be defined as either system-ownedindexes or as indexed sets.

index key. A symbolic key defined for an indexedset in the database and used to sort the memberoccurrences of the set.

indicator variable. A host variable that is used tomanipulate null values.

information center. An organizational structuregeared toward the management and support ofend-user computing. An information center servesas a focal point for using, maintaining, anddistributing information throughout the corporation.

Information Database (IDB). The component ofCA ICMS that links computers to the IBM mainframeand creates the information center environment. TheInformation Database is composed of IDBCommunications, IDB Manager, and the IDB Mailfacility.

initialize utility. See FORMAT utility statement.

INSERT statement. An SQL database accessstatement that adds one or more rows to a table.

installation code. A code that you can use toestablish DC/UCF runtime security. You can assigninstallation codes to users within a profile. Then, youcan access these codes at runtime to determine auser's authority to access various softwarecomponents.

INSTALL STAMPS utility statement. In anSQL-defined database, the utility that storessynchronization stamps in an area of an SQL-defineddatabase that was reformatted by file.

integrity. The accuracy of data. See also recovery,referential integrity.

intent-exclusive lock. A logical lock placed on anarea that allows exclusive locks to be placed onrecords within the area. See also intent lock,intent-share lock, update-intent-exclusive lock.

intent lock. A logical lock mode placed on an areathat allows certain types of logical locks to be placedon records within the area. See also intent-sharelock, intent-exclusive lock, update-intent-exclusivelock.

intent-share lock. A logical lock placed on an areathat allows share locks to be placed on recordswithin the area. See also intent lock, intent-exclusivelock, update-intent-exclusive lock.

inter-CV-interest. A state in which an area is beingshared by at least one Data Sharing Group memberwith a status of UPDATE and more than one DataSharing Group member with a status of RETRIEVALor UPDATE.

34 CA IDMS Glossary

inter-dialog commands. In CA ADS, the controlcommands (TRANSFER, INVOKE, RETURN, andLINK) that instruct the runtime system to pass controlfrom one dialog to another, or to a user program,during the execution of an application.

interface program specification block (IPSB).The CA IDMS DLI Transparency component thatcontains user-supplied control information compiledby the IPSB compiler. The resulting module, loadedby the CA IDMS DLI Transparency interface,describes the correspondence between the CAIDMS/DB database structure and the simulated IMSdatabase structure seen by the application program.There can be one IPSB for each DL/I program, orseveral programs can use a single IPSB.

internal picture. The format of data as stored invariable storage or in the database. Internal picturesare defined for elements through the DDDL compiler.

internal response. In the CA ADS applicationcompiler, a response that does not invoke a function.An internal response is assumed to initiate aresponse process of a dialog.

internal security. In CA IDMS centralized security,a system that allows privileges to be granted only tothose users and groups that have been defined tothe user catalog. See also external security.

internal wait. The period of time that an externalrequest unit will wait for a database resource (suchas a locked area) or a system resource (such asstorage space) before abending.

internet address (IP address). A value thatidentifies a network interface, in most cases a singlehost.

internet protocol (IP). A protocol defining a packetdelivery service for higher level protocols, such asTCP and UDP.

interval monitor. The part of the CA IDMSPerformance Monitor that provides system-wide waitstatistics on each type of wait by interval. Theinterval monitor has both an online and a batchcomponent.

Interruptable Mode. The Animation Mode in whichyou specify animation stop (interrupt) points. Seealso Non-Interruptable Mode.

IP. See internet protocol (IP).

IP address. See internet address (IP address).

IPSB. See interface program specification block(IPSB).

IPSB generator. In CA IDMS DLI Transparency,the interface program specification block (IPSB)generator that produces all of the source statementsnecessary to define one IPSB. The IPSB that isgenerated is based on the contents of existing DL/Icontrol blocks.

IPv4. Internet protocol version 4.

IPv6. Internet protocol version 6.

ISO date/time format. A date/time format thatcomplies with the standard of the InternationalStandards Organization: DATE as yyyy-mm-dd andTIME as hh.mm.ss.

isolation level. An attribute of an SQL session thatdetermines read integrity. An isolation level ofCURSOR STABILITY guarantees read integrity. Anisolation level of TRANSIENT READ does not. Seealso CURSOR STABILITY isolation level,TRANSIENT READ isolation level.

iteration. See path iteration.

iterative command. A path-DML command thatLRF recognizes as a potential point at which to beginpath iteration.

Itree. A data structure that contains the internalinput representation of an SQL statement.

JIS date/time format. A date/time format thatcomplies with the standard of the Japanese IndustrialStandard Christian Era: DATE as yyyy-mm-dd andTIME as hh:mm:ss.

join. The generic relational operation that yields aresult table comprised of columns from two or moretables. Tables are joined based on columns that thetables have in common. See also outer join.

journal buffer. The storage space in memory thatholds the journal pages being written to a journal file.Each DMCL contains one and only one journalbuffer. See also buffer, database buffer, recordbuffer.

Glossary 35

journal file. A file on which database processing isautomatically recorded. The information recordedincludes checkpoints and before and after images ofdatabase records updated during processing. Journalfiles allow recovery of the database in the event of aprogram or system failure. See also archive journalfile.

journal fix utility. See FIX ARCHIVE utilitystatement, PRINT JOURNAL utility statement.

journaling. In CA IDMS/DB, the process of writingjournal buffer information to the journal file.

journal record entry. An entry written to a journalfile by CA IDMS/DB to document changes to arecord in the database.

journal reporter. A reporting facility that enablesusers to analyze the contents of the CA IDMS/DBarchive journal file. The journal reporter isimplemented through CA Culprit. See alsoJREPORTs.

JREPORTs. Reports that provide information on thecontents of an archive journal file. See also journalreporter.

junction record. In CA IDMS/DB, a member recordrepresenting the relationship between records thatown it. Junction records permit many-to-manyrelationships between record types.

KEEP. The navigational database access functionthat locks a record occurrence against access orupdate by another transaction.

kept storage. Storage that remains allocated byDC/UCF after a task ends. DC/UCF associates keptstorage with the logical terminal from which it wasrequested. See also shared storage, user storage.

key. See CALC key, concatenated key, databasekey (db-key), foreign key, generic key, primary key,symbolic key.

keys table. For each CA IDMS online tool, a table(defined at system generation) that describes theterminal control keys and the functions they perform.

keyword. A word used in the command syntax of aCA IDMS product. Keywords are recognized by thesystem and must be typed exactly as shown incommand syntax, which uses uppercase to display

required characters and lowercase to display optionalcharacters.

layout. The arrangement of record blocks, sets,and indexes in a CA IDMS Schema Mapper datastructure diagram.

LID. A 4-byte value that locally identifies the workdone by a transaction branch. A single LID value iscarried in BFOR, AFTR, COMT, ENDJ, and ABRTjournal records to distinguish the work done by onebranch from that of another. Multiple LID values canoccur in the CKPT, DCOM, and DBAK records.

line. 1) A communication line. 2) An IDD entitytype used to document a method of communication.

line drivers. The software components thatcommunicate with the access methods in use tomove data between main storage and teleprocessingI/O devices.

line index. The item that identifies the location of arecord occurrence on a database page. A databasepage contains one line index for every recordoccurrence on that page.

line mode. In DC/UCF programs, line-by-linetransfer of data to and from a program.

link. In CA IDMS/DB and CA IDMS/DCprogramming, the process of loading a program ordialog and passing control to it.

linkage options. In CA IDMS/DB, options thatallow the user to specify the types of pointers (next,prior, and/or owner) to be used in relating memberand owner occurrences of a set.

linked constraint. A referential constraint in whichCA IDMS/DB maintains a physical linkage betweenthe rows in the referenced and referencing tables.See also unlinked constraint.

linked relationship. A relationship in which relatedentity occurrences are linked to one another throughembedded pointers. Types of linked relationshipsare: chained or indexed. See also unlinkedrelationship.

literal field. In the Mapping Facility, a map field thatdisplays a predefined literal string to be displayed.

LKG. See lock grant control block (LKG)

36 CA IDMS Glossary

LKS. See lock session block (LKS).

LKW. See lock wait block (LKW).

load area. The DDLDCLOD or DDLCATLOD areasof the data dictionary in which load modules arestored. See also DDLDCLOD area, DDLCATLODarea, load module.

load list. A path used by the DC/UCF system whensearching for programs to load. A load list caninclude both load libraries and data dictionaries. Youdefine load lists during DC/UCF system generation.

load module. 1) A program unit in executable codethat can be loaded into main storage for execution.CA IDMS products use load modules stored in theload areas (DDLDCLOD or DDLCATLOD) of thedictionary or in a load library. 2) An IDD entity typeused to define a load module. See also load area.

LOAD utility statement. For an SQL-defineddatabase, the utility that loads data.

local mode. A CA IDMS/DB mode of operation inwhich a batch program uses a dedicated copy of theDBMS to access the database. In local mode, onlyone application program can update the database atany given time. See also central version.

local node. In a DC/UCF communications network,the DC/UCF system that controls the terminal youare using. In batch mode, the local node is theDC/UCF system with which your program firstestablishes communication. This term is a synonymfor host node.

local response. In CA ADS, the type of responsethat is valid only when specifically associated with afunction. The concept of a local response appliesspecifically at application definition time. Theopposite of a local response is a global response.

local task. In a DC/UCF communications network,a DC/UCF task that is requested and executed at thehost node. The resulting database I/O can beperformed by either the host node or target node.

local transaction. A transaction in which changesare made to resources controlled by a singleresource manager.

location mode. The manner in which a recordoccurrence is physically located in an area of the

database. The three available location modes areCALC, DIRECT, and VIA.

lock acquisition mode. For SQL sessions, themode that determines when area locks are acquired.Preclaim mode places locks on all areas that specifyPRECLAIM when the first statement that requiresaccess to the database is executed. Incrementalmode delays placing a lock on an area until the firststatement that requires access to the area isexecuted. See also preclaim lock acquisition mode,incremental lock acquisition mode.

LOCK AREA utility statement. The utility thatplaces a physical area lock on an area or all areas ina database segment.

lock grant control block (LKG). The control blockthat identifies each resource in use by a task. AllLKGs for the same resource are chained together sothat all tasks sharing the resource can be identified.

locking. In CA IDMS/DB, a facility that maintainsthe integrity of the database by restricting access bya transaction to records or areas that are currently inuse by another transaction.

lock mode. A mode associated with each logicallock that determines whether the lock conflicts withother locks already held on the resource and withlocks subsequently requested by other transactions.See also share lock mode, exclusive lock mode,null-lock mode, intent lock.

LOCKMON command. A system-defined taskwhich you can use to display and react to locksbeing held for an area or by a terminal. You can alsouse Lock Monitor to free locks so that you canchange states for an area.

lock session block (LKS). The control block thatassociates locks managed by the lock manager withthe user session requesting those locks. The LKSfor a task that is waiting on a lock managed by thelock manager is chained to the LKW created torepresent the wait.

lock wait block (LKW). The control block thatindicates a task is waiting for a database resource.All LKWs for the same resource are chained togetherso that all tasks waiting on the resource can beidentified.

log. The runtime repository for DC/UCF systemmessages, snap dumps, trace information, and

Glossary 37

statistics. The log can be assigned either to theDDLDCLOG area or to a sequential disk or tape file.See also DDLDCLOG area, log file.

log area. See DDLDCLOG area.

log file. A sequential disk or tape file defined foruse as the DC/UCF system log. DC/UCF writes thesystem log to a sequential file or to the DDLDCLOGarea, depending on the system-generationspecification. CA OLQ Batch and CA ADS Batchusers can specify their own sequential log files foruse at execution time. See also log.

logical area lock. A lock used by the centralversion to control concurrent access to areas bydatabase transactions running under the centralversion. Logical area locks are derived from themode in which an area is readied. See also physicalarea lock.

logical database design. See logical model.

logically deleted record. A record flagged fordeletion but not yet physically deleted from thedatabase. CA IDMS/DB physically deletes therecord only after it has been disconnected from allsets of which it is a member.

logically deleted user/group. In centralizedsecurity, a user or group flagged for deletion but notyet physically deleted from the user catalog. Thesecurity facility physically deletes the user or groupwhen you execute the SDEL task in each system ofthe security domain and against each dictionary inthe system that contains the security definitions.

logical model. A logical mapping of data and datarelationships, together with integrity rules, thatrepresents the inherent structure of the data relativeto a given set of business functions. Typically, thelogical model is documented with the aid of data flowdiagrams representing the known set of all corporatefunctions. The logical model is not applicationdependent; it represents all data entities and theirrelationships.

logical network. A combination of databases andapplication programs that handle an organization'sinformation and processing requirements. See alsophysical network.

logical operators. The operators AND, OR, andNOT. These operators can be used in selection

criteria to help specify the rows to be accessed froma data table.

logical record. One or more database recordspresented to the application program as a singlerecord. Logical records provide access to multipledatabase records by a single request. The use oflogical records is supported through the LogicalRecord Facility.

logical-record element. A database record thatforms part of a logical record.

Logical Record Facility (LRF). The softwarecomponent that simplifies application programmingby allowing the database administrator to predefinelogical records and the processing sequencesnecessary to access them.

logical-record occurrence. The data returned inresponse to a logical-record request. Alogical-record occurrence is composed of oneoccurrence of each database record that makes upthe logical record.

logical-record request. A database accessfunction issued by an application program to requestLRF services. The four logical-record functions areOBTAIN, MODIFY, STORE, and ERASE.

logical-record request control (LRC) block. Thecontrol block through which LRF communicates withthe program requesting logical-record services.

logical terminal. 1) DC/UCF's view of the eventsassociated with a particular physical terminal. Thelogical terminal is used by DC/UCF to communicatewith the physical terminal. At runtime, the terminaloperator's signon information (for example,password, security codes), the executing task, andresources are associated with the logical terminal. Alogical terminal is defined by the LTERM statementat system generation. 2) An IDD entity type used todocument the logical terminals in an onlineenvironment.

logical terminal element (LTE). The control blockused by DC/UCF to manage and maintain theresources associated with a particular logicalterminal.

log service driver. The DC/UCF task that writesrecords to the CA IDMS/DC log area. Log servicedrivers also open the log area, initialize the CA

38 CA IDMS Glossary

IDMS/DC log work area, and acquire log buffers atsystem startup.

longterm lock. A shared or exclusive record lockthat is maintained across transactions. See alsolocking, notify lock, record lock.

LOOK command. LOOK is a system-defined taskthat allows you to look at the contents of selectedload modules. See also IDMSLOOK.

LRC block. See logical-record request control(LRC) block.

LRF. See Logical Record Facility (LRF).

LTE. See logical terminal element (LTE).

LTERM. See logical terminal.

mail facility. See IDB Mail Facility.

mainline dialog. In CA ADS, a dialog that isdesignated as an entry point to an application thread.A dialog is specified as mainline through the dialogcompiler.

MAINTAIN INDEX utility statement. For anon-SQL defined database, the utility that builds,rebuilds, or deletes one or more indexes.

major code. The first part of the two-part valuereturned to the ERROR-STATUS field of the IDMSand IDMS-DC communications blocks uponcompletion of a non-SQL DML function. The majorcode, a two-byte value, identifies the DML functionperformed:

■ The value 00 applies to all DML functions.

■ Values in the range 01 through 20 identifydatabase functions, both online and batch.

■ Values in the range 30 through 51 identifyDC/UCF functions.

See also minor code.

MANDATORY membership. A membership optionthat determines how member record occurrences aredisconnected from the set. When a record hasmandatory membership in a set, occurrences of thatrecord are disconnected from the set with theERASE function.

MANUAL membership. A membership option thatdetermines how member record occurrences are

connected to the set. When a record has manualmembership in a set, occurrences of that record areconnected to the set with the CONNECT function.

map. 1) A formatted layout of a terminal screen. Amap names the literal and variable fields on thescreen, identifies the location of each field on thescreen, names the record element associated witheach variable field, assigns display characteristics(attributes), and defines editing criteria. Maps arecreated through the DC/UCF mapping facility. 2) AnIDD entity type that documents the maps (or tables)used by teleprocessing monitors.

MAPB. The task code for the online map compilerfor creating batch file maps that are used byADS/Batch. See also RHDCMAP1, RHDCMPUT.

MAPC. The task code for the online map compilerfor creating online maps. See also RHDCMAP1RHDCMPUT.

mapin. The mapping operation in which valuesentered by the terminal operator into variable mapfields are moved into program variable storage. InCA ADS, each mapin operation begins a new task.

map level help. Help text associated with a map bymeans of the online or batch map compilers, andwhich is displayed when the help key defined for themap is pressed either with the cursor positioned in adata field for which no field-specific help is defined oroutside of any data field. See also help facility, fieldlevel help.

map load module. The load module generated bythe DC/UCF Mapping Facility. Programs and dialogsexecute map load modules to display and receivedata.

mapout. The mapping operation in which a map isdisplayed at the terminal. Literal fields are moved totheir assigned positions, and the contents of theassociated data areas in variable storage are movedto the map's data fields.

mapping. The method used by CA IDMS onlinefacilities to transfer a complete screen of databetween application programs and a terminal.

mapping compilers. Batch and online mappingtools:

■ The batch compiler (RHDCMAP1) and batchutility (RHDCMPUT) allow you to define,

Glossary 39

generate, decompile, report on, and delete mapsin batch mode.

■ The online mapping compiler (also known asMAPC) allows you to define, generate, anddelete maps in online mode.

Mapping Facility. A tool that you use to define thelayout of maps.

mapping mode. In CA IDMS/DC terminalmanagement functions, the mode in which an entirescreen of data is transferred, field by field. Mappingmode can be used with 3270-type terminals and alsowith glass TTYs that have associated deviceindependence tables.

map request block (MRB). The control block usedto perform mapping operations.

map work record. A record associated directly witha map. The record is automatically available to adialog or program that uses the map. Map workrecords can be schema records or records builtusing IDD. See also dialog work record.

master terminal function. See DCMT task.

MDT. See modified data tag.

member record. A database record type defined assubordinate to an owner record type in aone-to-many relationship. For example, in arelationship defined between a DEPT owner and anEMPLOYEE member, each department can containseveral employees.

membership. In CA ICMS, the relationshipbetween an entity and the folder or group in whichthat entity is included. (Both objects and folders canbe members of folders; both users and groups canbe members of groups.)

membership options. In a non-SQL schema, thespecifications that indicate how a member recordoccurrence is connected to or disconnected from aset occurrence. For a given record in a set, theschema can specify one of the following membershipoptions: MANDATORY AUTOMATIC, MANDATORYMANUAL, OPTIONAL AUTOMATIC, or OPTIONALMANUAL.

menu. See menu map.

menu/dialog function. In CA ADS, an applicationfunction defined as a menu function and alsoassociated with a dialog. Like a menu function, themenu/dialog function uses system-supplied menuprocessing facilities. However, the menu/dialogfunction can also perform any processing defined inthe associated dialog. See also application function,menu function, menu map.

menu function. In CA ADS, an application functionthat displays a system-defined menu map andperforms standard system-supplied menu processingactivities at runtime. See also application function.

menu map. A map containing a list of validresponses the user can select. In CA ADS, menumaps are automatically built for an applicationdefined by using the application compiler. A menumap must be defined to coordinate withsystem-supplied menu processing facilities. CA ADSprovides three system-defined menu maps for use inCA ADS applications. Users can also define theirown menu maps. See also map, menu function.

menu mode. The menu-driven version of the onlinedebugger, CA OLQ, and IDD.

menu stack. In CA ADS, the sequence of menusand menu/dialogs that the user has executed butthrough which the user has not yet returned. TheCA ADS runtime system uses the menu stack tomanage the flow of control through menus atruntime.

Merge Archive utility statement. The utility that isused to merge the archived journal files of DataSharing group members that are sharing updateaccess to data. It can also be used to merge archiveand local mode journal files to simplify a subsequentrecovery operation.

message. An IDD entity type that documentsinformational messages to be used in DC/UCFapplications.

message area. See DDLDCMSG area.

message field. In the Mapping Facility, a map fieldthat displays messages generated by an applicationprogram or by the automatic error-handling facility.

migration. 1) The process of moving componentsfrom one system to another. 2) The process ofmoving an application from a test system to aproduction system. 3) The conversion of a software

40 CA IDMS Glossary

system from one type of hardware to another or fromone type of software architecture to another. 4) Theprocess of upgrading an installed product to a newrelease of that product. 5) The process of movingsource and/or load modules from one data dictionaryto another.

minimum fragment. The smallest portion of avariable-length record to be stored on a page otherthan the record's home page. The minimumfragment specification, provided in the non-SQLdefined schema, is used when a record's home pageis too full to store the complete record.

minimum path. In CA ICMS, the shortest path thatuniquely identifies an entity in the catalog.

minimum root. The smallest portion of avariable-length record to be stored on the record'shome page. The minimum root specification,provided in the schema, is used when a record'shome page is too full to store the complete record.

minor code. The second part of the two-part valuereturned to the ERROR-STATUS field of the IDMSand IDMS-DC communications blocks uponcompletion of a non-SQL DML function. The minorcode, a two-byte value, describes the status of thefunction identified by the major code. See alsomajor code.

mixed page group feature. In CA IDMS/DB, thefeature that allows a database session to accessdata in different page groups. Specifying MIXEDPAGE GROUP BINDS ALLOWED when defining aDBNAME activates this feature for all sessionsconnecting or binding to the DBNAME.

model dialog. In ASF, the default dialog used togenerate dialogs for data tables. The model dialogis stored as a source module in the DDLDML area ofthe ASF dictionary.

model map. In ASF, the default map used togenerate screen displays for data tables. The modelmap is stored in the DDLDML area of the ASFdictionary.

model subschema. In ASF, the default subschemaused to generate subschemas for data tables. Themodel subschema is stored as a source module inthe DDLDML area of the ASF dictionary.

modified data tag. For a variable field on a map,the internal tag that keeps track of whether or not the

value in that field has been changed by the terminaloperator.

MODIFY. The navigational database accessfunction that replaces the contents of adatabase-record occurrence with the values in itscorresponding variable storage.

MODIFY logical record. The LRF database accessfunction that replaces the contents of a logical-recordoccurrence with the values in its correspondingvariable storage.

MODIFY path group. A collection of paths(predefined in a logical-record subschema) designedto service application programs that request aMODIFY logical-record function.

module. An IDD entity type used to define sourcecode for processes, qfiles, edit tables, code tables,reports, and transactions.

MPMODE. See multiprocessing mode.

MRB. See map request block (MRB).

multihomed system. A system on which multiplenetwork interfaces (instances of TCP/IP) are active.

multilevel hierarchy. A relationship formed when amember of a set is the owner of another set.

multiple-member relationship. A singlerelationship maintained for more than one child entitytype.

multiple-member set. A set in which two or morerecord types participate as members.

multiple membership. The relationship formedwhen a given record type is owned by more thanone record type and, thus, is a member in more thanone set type.

multiple selectors. In LRF, two or moreELEMENT, FIELDNAME, FIELDNAME-EQ, orKEYWORD selectors specified in a single SELECTclause. Only a program request whose WHEREclause references all of the named selectors can bematched to this path.

multiple-set ownership. A relationship formedwhen one record type owns more than one set.

Glossary 41

multiple sets. The relationship formed when onerecord type is related to a second record type inmore than one way.

multiprocessing mode. The code lock thatDC/UCF uses to enforce execution serialization in amultitasking environment. Multiprocessing modesdivide code into families. Certain families ensureserial execution of all code that has been assignedto that family while other families allow concurrentcode execution. By serializing only that code whichrequires it, DC/UCF is able to increase throughput byexploiting multiple CPUs.

multiprogramming. Under DC/UCF, the ability toexecute several different tasks concurrently.Multiprogramming enables a system to runlarge-volume online and batch programssimultaneously.

multitasking. In the DC/UCF environment, theability to run multiple operating-system subtasks atthe same time. DC/UCF supports multitasking in auniprocessing and multiprocessing environment.

multithreading. Under DC/UCF, the ability of twoor more different tasks to execute a reentrantprogram concurrently. Multithreading conservesstorage and reduces CPU overhead.

name server. A component of the CA IDMSdatabase communications architecture that identifiesthe location of resources within the network.

native VSAM support. The ability to use CAIDMS/DB to access data from a file defined to VSAMand containing VSAM records. The VSAM files mustbe defined to CA IDMS/DB by including specificstatements in the schema and DMCL DDL. Oncedefined to CA IDMS/DB, the VSAM files appear tothe DBMS as CA IDMS/DB files and can beaccessed by CA IDMS/DB applications.

natural collating sequence. A collating sequencein which negative numeric values are sorted lowerthan positive values. See also standard collatingsequence.

navigation. The process of searching the setsstored in a database and of following the memberrecord pointers (next, prior, or owner) to locatespecific record occurrences.

navigational database access. A database accessmethod that requires knowledge of the physical

structure of the database. Navigational databaseaccess allows programmers precise control of thedatabase. See also SQL database access.

navigational DML. 1) A data manipulationlanguage that obtains and updates the database onerecord at a time, using currency and error checkingto ensure correct results. 2) Non-SQL DMLdatabase and DC/UCF commands.

nested structure. Any data processing structure inwhich one component exists as a sublevel of anothercomponent. See also bill-of-materials structure.

next linkage. In CA IDMS/DB, the type of setlinkage in which the owner and members of a setoccurrence are linked by next pointers. Next pointerscause the owner to point to the first member, the firstmember to point to the second member, and so on;the last member points to the owner.

node. A system defined to a DC/UCFcommunications network.

node name. The logical name of a DC/UCFsystem.

Non-Interruptable Mode. The Animation Mode inwhich you do not specify animation stop (interrupt)points. CA ADS Alive steps through dialoganimation one line of code at a time, pausing for aspecified length of time. The Non-InterruptableMode causes all CA ADS Alive Animation RuntimeSession commands to be inoperative. See alsoInterruptable Mode.

nonoperative status. In CA ADS, the status of adialog when control has passed from that dialog toanother dialog with the TRANSFER or RETURNcommand (that is, when the dialog is no longer partof the application thread).

non-sharable transaction. A transaction initiatedby a database session for which transaction sharingis not enabled. A non-sharable transaction cannot beshared by sessions that are peers of the initiatingsession but can be shared by sessions that aresubordinate to the initiating session. See alsosharable transaction, peer session, subordinatesession.

non-SQL defined schema. A schema defined withnon-SQL DDL statements.

42 CA IDMS Glossary

nonterminal task. A task that is not initiated from aterminal. For example, a task that DC/UCF initiatesautomatically at startup or shutdown.

non-terminating task data transfer. A means ofdata transfer between program storage and aterminal that allows a front-end application (forexample, a CICS user task) to wait for informationfrom a CA IDMS UCF back end without terminating.See also terminating task data transfer.

NOREADY. In CA ADS, an option of the READYAREA compiler directive that indicates that a dialogwill not use the area and that the CA ADS runtimesystem should not ready it when a databasetransaction begins.

normalization. The analysis of data structuresbased on a set of rules. The rules eliminateredundancy and ensure unique identifiers. Underthis approach, data can be normalized to varyingdegrees (first normal form, second normal form, thirdnormal form). Third normal form is typically used todesign stable data structures. Normalization is partof the database design process.

notify lock. A special form of the longterm lockestablished by using the LONGTERM NOTIFY optionof the KEEP DML command. Notify locks monitordatabase activity for the record that is current ofrecord type, set, or area. See also locking, longtermlock, record lock.

nucleus. The group of modules that performDC/UCF system functions, such as program loadingand storage management. Nucleus modules arestored in the appropriate program and reentrantpools.

nucleus map. A table listing the name and addressof each module in the DC/UCF nucleus.

null-lock mode. A special type of logical lock whichis placed on a record to signify a notify lock and onan area to signify transient retrieval access.Null-locks provide no protection against concurrentaccess. See also share lock mode, exclusive lockmode.

null PDE. A generic program definition element thatis set aside during system startup for later use. Youallocate null PDEs to a system when you wantDC/UCF to define programs automatically. NullPDEs are defined during system generation. Seealso automatic program definition.

null SELECT clause. In LRF, a SELECT clausewithout any path descriptors. This clause identifies apath that LRF can match with any logical-recordrequest.

null value. A construct that denotes the absence ofa value and is not the same as spaces or numericzeros, which are actual values. In an SQL-defineddatabase, a column, regardless of data type, cancontain a null value unless the column definitionspecifically disallows them.

object. The logical unit in which CA ICMSmaintains information. An object can be formattedas a data table (the equivalent of a CA IDMS/DBdata table) or can be stored in a free-form format (tohold such information as text, spreadsheets, andgraphs).

object dictionary. In CA IDMS Dictionary Migrator,a dictionary that acts as the destination for entitiesthat are moved during the migration process. Yourobject dictionary is populated by entities that arecopied from your source dictionary(s). Only oneobject dictionary can be used during each migration.See also source dictionary.

object record. 1) A record occurrence that is thetarget of a database access request. 2) At systemgeneration, the dictionary record representing anentity that participates in a DC/UCF system. Objectrecords associate source records with DC/UCFsystems. Only object records are used when aDC/UCF system executes. See also source record.

OBTAIN. The navigational database accessfunction that combines the FIND and GET operationsto retrieve a record occurrence.

OBTAIN logical record. The LRF database accessfunction that retrieves a logical-record occurrence.

OBTAIN path group. A collection of paths(predefined in a logical-record subschema) designedto service application programs that request aMODIFY logical-record function.

occurrence, logical-record. See logical-recordoccurrence.

occurrence, override. A specification in theSecurity Resource Type Table (SRTT) for anoccurrence of a resource that overrides the SRTTspecification for the resource type.

Glossary 43

occurrence, record. See record occurrence.

OCF. See Online Command Facility (OCF)

OCFX task. An online task that executesOCF-language modules; that is, modules containingCommand Facility statements.

offline area status. The status for an area definedto the runtime DMCL in which database transactionsexecuting under the central version can neitherretrieve nor update data in the area.

offload. The process of moving the contents of adisk file to tape.

OLM. The online mapping facility of DC/UCF. Notethat this term no longer refers to the online mapcompiler (MAPC and MAPB).

OLP. The system task that invokes the onlinePLOG. See also online PLOG.

OLQ access mode. In CA OLQ, an access modethat you use to access non-SQL defined (that is,ASF) tables and records. See also IDMS accessmode.

ON clause commands, path-DML. In LRF,commands that specify path branching, pathiteration, or return control to the program in responseto a specific error-status value returned by theDBMS.

ON clause, program request. A clause that can becoded in an application program, following alogical-record request, to test for a specific pathstatus returned by LRF.

one-of-a-kind record. See OOAK record.

Online Command Facility (OCF). The CA IDMStool you use to submit Command Facility statementsinteractively and see the resulting output on a displayscreen. See also Command Facility.

online debugger. A facility to detect, trace, andeliminate errors in programs running under thecontrol of a DC/UCF system.

online mapping (MAPC and MAPB). The onlineversion of the facility for defining and generatingmaps for online use (MAPC) or batch (MAPB).

online PLOG. The online version of the PRINTLOG utility that displays the current contents of theDDLDCLOG area of the data dictionary. See alsoPRINT LOG utility statement

online program. A program that executes in aDC/UCF system. See also batch program,TP-monitor program.

online task. A task defined to the DC/UCF systemeither during system generation by means of theTASK statement, or at runtime by means of theDCMT VARY DYNAMIC TASK command.

online terminal block (OTB). In CA ADS, thecontrol block used by the runtime system.Associated with a logical terminal, this block existsacross tasks, anchoring all other control blocks. TheOTB contains the name of the current dialog and theaddresses of the current variable dialog block (VDB)and the fixed dialog block (FDB).

online terminal block extension (OTBX). In CAADS, an extension of the online terminal block (OTB)that is created when the runtime system executes anapplication generated by the application compiler.The OTBX contains pointers to the task applicationtable (TAT) and to the record buffer block (RBB) andapplication definition block (ADB) for the currentlyexecuting application.

online work area (OWA). In CA ADS, the workarea that exists for the life of a task. The OWAcontains fields for communication betweenADSORUN2 and ADSOCDRV, the subschemacontrol block, a pointer to the current map requestblock (MRB), and an internal stack.

OOAK record. A one-of-a-kind record type in thedatabase. An OOAK record is created when onlyone occurrence will exist for a record type.

open cursor. The act of opening a cursor; that is,making the cursor available to the program to fetchcursor rows. See also close cursor.

OPER. The system task code that invokes theDC/UCF dynamic system monitor. See also dynamicsystem monitor.

operating mode. See protocol.

operative status. In CA ADS, the status of a dialogthat is still an active part of an application thread.See also application thread.

44 CA IDMS Glossary

optimizer. A component of the SQL option thatvalidates table and column references against thedictionary and selects the most efficient databaseaccess strategy for an SQL statement.

OPTI module. See IDMSOPTI module.

OPTIONAL membership. The membership optionthat determines how member record occurrences aredisconnected from the set. When a record hasoptional membership in a set, occurrences of thatrecord can be disconnected from the set withoutbeing erased.

OPTF. See RHDCOPTF

order option. In a non-SQL schema, thespecification that indicates the logical order in whichmember record occurrences are connected within aset occurrence. The following order options areavailable: FIRST, LAST, NEXT, PRIOR, andSORTED.

orphan count. A count maintained by CA IDMS/DBwhen adding members to an unsorted indexed set.The orphan count indicates the number of indexentries that have been relocated when an SR8record is split to accommodate new members.

OTB. See online terminal block (OTB).

OTBX. See online terminal block extension (OTBX).

outer join. A SELECT statement operation thatjoins complete tables; that is, it includes the rowsthat have no match in another table. The result ofan outer join is a result table with all the rows fromone of tables in the join operation. See also join.

overflow. In CA IDMS/DB, a condition occurringwhen records must contend for storage space in thedatabase. The two types of overflow are CALCoverflow and clustered (or VIA) overflow. A CALCoverflow condition occurs when the randomized pagefor a CALC record is too full to accommodate therecord; the record is stored on the next page. Aclustered (VIA) overflow condition occurs if the pagesize for the database area is too small to hold alloccurrences of a clustered relationship.

overflow run unit. A system run unit that isinitiated by DC/UCF when all predefined system rununits are in use. DC/UCF terminates overflow rununits when they are no longer needed.

OWA. See online work area (OWA).

owner linkage. The type of set linkage in which theowner and members of a set are linked by ownerpointers. Owner pointers cause each member topoint to the owner.

owner record. The record type to which all otherrecords in a set are subordinate.

ownership. 1) An attribute of an SQL schema. Theuser who issues the CREATE SCHEMA statementsowns the schema and implicitly holds all access anddefinitions privileges on the tables, views, andaccess modules associated with the schema.Ownership can be transferred from one user toanother. 2) In CA ICMS, the relationship between auser (or the catalog) and an entity owned by thatuser. A user can own objects and folders; thecatalog can own objects, folders, users, and groups.

packet-data-movement buffer. The CSA (z/OS),the SVA (z/VSE version 2.1 or later), or the area in astorage pool that DC/UCF uses to communicate withexternal request units.

page. A logical division of the database thatcorresponds to a physical block in a file. An area ismade up of a range of contiguous pages. All pageswithin an area have the same size, but page sizecan vary from one area to another.

pageable map. In CA ADS, a map that can containunlimited occurrences of a set of map fields. Apageable map can contain more detail occurrencesthan can fit on the terminal screen at one time; theterminal operator can move from page to page toview all the detail occurrences.

page field. In the Mapping Facility, a pageable-mapfield that displays the current page number andpermits the operator to select another page fordisplay.

page group. An attribute of a segment thatuniquely identifies a collection of page ranges. In amultiple-database environment, a segment can beassociated with only one page group, while a pagegroup can be associated with more than onesegment; that is, page groups allow a page range tooccur more than once.

page identifier. A unique two-character (alphabetic)identifier that specifies the position of a (paper) pagein a CA IDMS Schema Mapper data structure

Glossary 45

diagram. The first character identifies the page'scolumn (which runs down the length of the diagram),and the second character identifies the page's row(which runs across the width of the diagram).

page lock. A logical lock used by CA IDMS/DB toprotect the contents of a database page while itresides in a Data Sharing group member's bufferpool.

page number. A unique, system-assigned numberfor a database page.

page range. 1) The range of pages, from beginningto end, in a database area. 2) A subgroup of pagesin a database area.

page reserve. The specified number of bytes perpage designated specifically for expansion ofvariable-length records. Page reserves minimizefragmentation of variable-length records duringupdate functions. The designation of a page reservedoes not affect the physical structure of thedatabase.

PA key. See program attention (PA) key.

panel. An IDD entity type that associatesdocumentational entries and users with maps used inthe 3270-type terminal environment. In IDD, theterms panel and screen are synonymous.

parent. A logical database design term that refersto a referenced table in SQL database design and anowner record in non-SQL database design. See alsochild, owner record, referenced table.

participant. In a two-phase commit, a resource ortransaction manager other than the coordinator. Aparticipant is sometimes referred to as an agent. Seealso coordinator.

passkey. In CA ICMS, a catalog entity thatrepresents permission for users to accessinformation or to perform administrative tasks. Seealso catalog access passkey, data access passkey.

path. 1) In CA IDMS/DB, a route through theapplication database that is used to access andupdate data. 2) In LRF, the subschema componentthat contains path-DML commands. Thesecommands perform the data manipulation necessaryto fill a program's logical-record request.

PATH. In CA Culprit, the parameter that indicatesthe access path through the database.

path-DML commands. In LRF, the DMLstatements in a logical-record path (defined in asubschema) that perform the database navigationand functions necessary to fulfill a program's requestfor a logical record. See also Data ManipulationLanguage (DML).

path group. In LRF, a collection of paths (definedin a subschema) designed to fulfill program requestsfor specific logical records and specific databaseaccess functions. Up to four path groups can bedefined for each logical record (that is, OBTAIN,ERASE, STORE, and MODIFY).

path iteration. In LRF, the reexecution of all or partof a logical-record path to access all occurrencesthat meet the selection criteria specified in a programrequest or in a path WHERE clause. Path iterationis implemented through FIND/OBTAIN EACHpath-DML commands.

path selectors. The descriptors in a subschemaSELECT clause that LRF compares with thecontents of a program request's WHERE clause.

path status. A literal provided by either LRF or theDBA to indicate the outcome of a logical-recordprogram request.

peer session. A database session in the samesession hierarchy as another session and neither ofwhich is a subordinate session of the other. See alsodatabase session, subordinate session,encompassing session, top-level session.

permission. In CA ICMS, authority given to a userthrough passkeys. Users can be given permission tomanipulate information in CA ICMS as well as tomanipulate catalog entities.

PF key. See program function (PF) key.

physical area lock. A lock set and examined byCA IDMS/DB whenever an area is opened in anupdate mode. Physical area locks preventconcurrent updates by multiple local databasetransactions, multiple central versions, or both.Physical area locks also prevent update access to anarea that requires rollback of database transactions.See also logical area lock.

46 CA IDMS Glossary

physical database. A collection of data that residesin operating system files; CA IDMS/DB usesinformation provided at runtime to determine how tomap the logical representation of the database toone of perhaps many physical implementations ofthe database. See also segment.

physical database definition. The part of thedatabase definition that describes the physicalstructure of the database, including segments, theDMCL, and a database name table.

physical database design. The process of tailoringthe logical model to specific application performancerequirements, the best use of computer resources,and efficient data access.

physical DDL. The database definition languagesubmitted to the Command Facility that defines aphysical database. Physical DDL statements defineDMCLs, database name tables, segments, and thecomponents associated with these entities.

physical network. A combination of interconnectedequipment (hardware) and programs(telecommunications access methods) used totransmit data between physical locations. See alsological network.

physical terminal. 1) A physical device, such as aCRT (3270-type), TTY, or printer, that exists within ateleprocessing system. In the DC/UCF environment,a physical terminal is associated with a logicalterminal; physical terminals are defined with thePTERM statement at system generation. 2) An IDDentity type that documents the physical CRT, TTY,and printer devices in a teleprocessing system.

PLOG. See online PLOG.

pointer. A database key stored in the prefix of arecord occurrence that indicates the physical locationin the database of another related record occurrence.When a set is defined between related databaserecord types, CA IDMS/DB stores pointers torepresent their relationship.

populate. To load a database with actual datavalues. A database can be populated only after ithas been defined.

port. 1) In the context of TCP/IP, a 16-bit numberthat is used to distinguish different applicationprograms that use the same network interface. 2) In

CA IDMS DDS, an access point through which thenode passes request and response packets toanother node.

positioned delete. Using SQL DML, deleting therow where the cursor is positioned in the result tableassociated with an updatable cursor. A positioneddelete requires the WHERE CURRENT OF clause inthe DELETE statement. See also searched delete.

positioned update. Using SQL DML, modifyingone or more column values in a row where thecursor is positioned in the result table associatedwith an updatable cursor. A positioned updaterequires the WHERE CURRENT OF clause in theUPDATE statement. See also searched update.

Post-Abort Browse Facility. In the event of ananimation/execution abort, CA ADS Alive displaysthe Post-Abort Browse Session screen showing theprocess containing the error. The line of sourcewhich caused the abort is preceded by theassociated error message.

POSTMASTER. In CA ICMS, a group entity whosemembers share authority over the mail facility.

POST OFFICE. In CA ICMS, a user entity thatcontrols the distribution of letters through the mailfacility.

preclaim lock acquisition mode. A lockacquisition mode for SQL sessions that places lockson all areas that specify PRECLAIM when the firststatement that requires access to the database isexecuted by the session within a transaction. Seealso incremental lock acquisition mode.

predefined run unit. A system run unit initiated atDC/UCF system startup and maintained for theduration of system execution. See also system rununit.

predicate. An operand of a search condition. Itexpresses or implies a comparison operation. Forexample, the BETWEEN predicate searches for allvalues within a range of values.

prefetch. A CA IDMS/DB feature for z/OS thatprovides the capability for CA IDMS/DB to do fulltrack reads. I/O requests are bundled so that there isonly one scheduling action for multiple physical I/O's.

prefix. See pointer, record prefix.

Glossary 47

premap process. An optional component of a CAADS dialog. A premap process is executed beforethe dialog's map is displayed, unless ENTRY POINTIS MAP is specified. The premap process performsany special processing required by the map. A givendialog can have only one premap process.

A premap process is defined as a standaloneprocess module in the data dictionary. You make aprocess module the premap process for a dialog byusing the dialog compiler. See also process module,response process.

prepared statement. An SQL statement that hasbeen dynamically compiled at runtime.

primary key. 1) The element or elements in arecord that uniquely identify each occurrence of thatrecord type. 2) The column or columns in a tablethat define a unique constraint and which are notnull. The primary key uniquely identifies each rowand prevents duplicate rows from being stored. Seealso foreign key, secondary key.

primary protect key. One of two storage protectkeys, provided by the operating system, thatDC/UCF uses to implement storage protection.When the system nucleus has control of the DC/UCFregion/partition, all storage pages in theregion/partition are set to the primary protect key.This allows the system nucleus to modify any pagein the region/partition. See also alternate protectkey.

primary storage pool. Storage pools 0 and 255 ina DC/UCF system. The primary (system) storagepool contains system storage and, optionally, userstorage. Storage pool 0 must be defined in order forthe DC/UCF system to start up. Storage pool 255 isthe primary (system) pool located in 31-bit addressspace.

PRINT INDEX utility statement. The utility thatreports on the structure of system-owned indexesand indexed sets.

PRINT JOURNAL utility statement. The utility thatreports on transaction checkpoints in an archivejournal file.

PRINT LOG utility statement. The utility that printsall or selected portions of the DC/UCF system log oran archive log file created by the ARCHIVE LOGutility statement.

PRINT PAGE utility statement. The utility thatprints the contents of one or more database pages indisplay (character) and/or hexadecimal format.

PRINT SPACE utility statement. The utility thatreports on space utilization in one or more areas orsegments.

prior linkage. The type of set linkage in which theowner and members of a set occurrence are linkedby prior pointers. Prior pointers cause the owner topoint to the last member, the last member to point tothe next-to-the-last member, and so on; the firstmember points to the owner.

privacy lock. See access restriction.

private catalog. In CA ICMS, a portion of thecatalog that contains data controlled by an individualuser (as opposed to data controlled by thecorporation). See also CORP, corporate catalog.

private property. All objects and folders in CAICMS that are owned by a particular user (that is,stored in a private catalog).

privilege. Under CA IDMS internal security, theright to access a particular resource and perform aparticular operation on that resource. Types ofprivileges are: definition privileges, access privileges,or administration privileges.

procedure. In the context of SQL, an SQLprocedure.

process. An IDD entity type used to define sourcecode for CA ADS process modules.

process command. In CA ADS, a commandprovided for use in coding process modules fordialogs. Process commands are English-likestatements that are fully integrated with DC/UCF andCA IDMS/DB facilities. See also process module.

process module. In CA ADS, a module of processcommands defined for use in dialogs. A processmodule performs one or more processing options forthe dialog. For example, a process module mightobtain and update employee records in thedatabase.

You define a process module in the data dictionaryby using the DDDL compiler. You add a processmodule to a dialog by using the dialog compiler.When used by a dialog, a process module is either a

48 CA IDMS Glossary

premap process or a response process. See alsopremap process, response process.

product code. The unique system-supplied namethat identifies a DC/UCF development tool or onlinecompiler to the transfer control facility (TCF). Forexample, IDD is the product code for online IDD;SSC is the product code for the online subschemacompiler.

profile. A set of attributes and options associatedwith users in a CA IDMS environment. Profiles usedto set initial values for environmental variables in theuser session are processed at signon time. See alsouser profile, system profile.

program. 1) An IDD entity type used to documentuser application programs. 2) Under DC/UCF, anexecutable entity that is stored and executed as aprogram; (for example, a subschema, map, dialog,edit/code table, or DML program).

program attention (PA) key. A predefined controlkey that serves as an alternative to typing a certaininstruction. When a PA key (PA1, PA2, or PA3) ispressed, no data is transmitted from the screen tothe record buffer. See also control key, programfunction (PF) key.

program definition element (PDE). The DC/UCFcontrol block that specifies general programcharacteristics. The number of PDEs used in aDC/UCF system is controlled by system-generationspecifications.

program directory list. An internal table ofprograms defined to the DC/UCF system. Theprogram directory list is built either at system startupor as programs are loaded during system execution.

program function. In CA ADS, an applicationfunction associated with a site-written program. Thissite-written COBOL, PL/I, or Assembler programperforms the processing activities required by thefunction. For example, the program might performspecialized data cross-validation routines. See alsoapplication function.

program function (PF) key. A predefined controlkey that serves as an alternative to typing a certaininstruction. When a PF key (PF1 through PF24) ispressed, data is transmitted from the screen to therecord buffer. See also control key, programattention (PA) key.

program pool. The storage space in memory intowhich resident and nonresident programs are loadedfor execution. Typically program pools hold CA ADSapplications, dialogs, subschemas, maps, databaseprocedures, edit/code tables, access modules,relational command modules, and user programs.Program pool specifications are part of a system'sdefinition.

program processor. A component of the DictionaryLoader that analyzes a single COBOL program andoutputs information about how the program usesdata.

program registration. The CA IDMS/DB securityfeature that enables you to associate programs withsubschemas. Using program registration, you cancontrol compilation of DML programs that use aparticular subschema.

project. The generic relational operation throughwhich only specific columns of a data table areaccessed.

prompt mode. The line-oriented method ofcommunicating with the debugger.

propagation. In CA ICMS, an ambiguousassociation that can occur when duplicate names areused.

protected retrieval ready mode. A retrieval readymode in which other transactions executingconcurrently under the central version can ready thearea only in shared retrieval or protected retrievalmodes.

protected update ready mode. An update readymode in which other transactions executingconcurrently under the central version can ready thearea in shared retrieval mode only.

protocol. 1) In CA IDMS/DB, a set of sourcestatements that the DML compilers use as a modelto convert DML statements into calls for DBMSservices. A protocol is stored as a module in thedata dictionary. 2) The formats and sequencing ofcommunications between entities during theperformance of an operation. For example, IP is acommunications protocol that defines a packetdelivery service.

prototype. In CA ADS, an early version of anapplication used to test and demonstrate thefunctions, responses, and maps of the application.

Glossary 49

The production application can be developed directlyfrom the prototype.

proxy lock. A global lock used to represent a lockon each record within a given database page. Proxylocks are acquired only in a Data Sharingenvironment.

pseudo column. An automatically created columnthat does not physically exist on the database.

pseudoconversational programming. An onlineprogramming technique that frees resources beingused by a task while the system waits for completionof data entry by the operator. For example, theruntime system of CA ADS is pseudo-conversational.

pseudo-converse. The interval between mapoutand mapin, during which the system resources for atask are freed.

PTERM. See physical terminal.

public access. In IDD, the ability of unregisteredusers to access data dictionary entity occurrences.

PUNCH. When using CA IDMS compilers in batchmode, the function that directs information to the filedefined for punched output.

PUNCH utility statement. The utility that retrievesthe DMCL or database name table load module fromthe dictionary, and writes them, in object moduleform, into the file defined for punched output.

qfile. 1) A module, stored in the data dictionary,that contains a sequence of CA OLQ commands.When a qfile is executed, all of the commandscontained in it are performed. Qfiles can be createdautomatically through CA OLQ or manually throughIDD. 2) An IDD entity type used to define sourcecode for CA OLQ qfiles.

QREPORTs. Reports that provide information onSQL-related entities stored in the DDLCAT,DDLCATX, and DDLCATLOD dictionary areas.

quasi-reentrant program. A COBOL program thatdoes not modify its own code, other than workingstorage.

queue. 1) A work area containing queue recordsshared by tasks on all DC/UCF terminals and bybatch programs. Queue records allow a task orapplication to pass data to another task or

application, or to transfer data from one terminal toanother. The records in a queue are preservedacross system shutdowns for a user-specifiednumber of days. 2) An IDD entity type thatdocuments the manner in which a teleprocessingsystem groups similar requests. See also queuerecord.

queue area. See DDLDCRUN area.

queue record. A record stored in the DDLDCRUNarea. Queue records, once stored, are available toany task in a system. Queue records are maintaineduntil explicitly deleted or until a retention periodelapses.

quiesce point. A quiesce point is a point in time atwhich no transactions are accessing a database areain update mode.

radix. See database-key format.

RBB. See record buffer block (RBB).

RCE. See resource control element (RCE).

RCM module. A module that contains the SQLstatements embedded in an application program.You create an RCM by precompiling the programthat contains the embedded SQL statements. Seealso access module

READY. The database access function that tells CAIDMS/DB which areas of the database theapplication program will access and in which readymode.

ready mode. See area ready mode, default readymode.

realtime monitor. The component of the CA IDMSPerformance Monitor that captures and displaysinformation describing the use of specific systemresources at the time of the request.

record. 1) An IDD entity type used to documentrecords, reports, and transactions. Typically, recordsare collections of related elements. Reports arehard-copy records. Transactions are collections offunctions or processes. 2) A synonym for recordtype and for record occurrence. 3) The internalimplementation of the rows of an SQL table.

record block. A representation of a CA IDMSrecord in a CA IDMS Schema Mapper data structure

50 CA IDMS Glossary

diagram. Record block descriptions can also belisted in the Cross-Reference Report. A record blockcontains various record fields.

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

record buffer block (RBB). In CA ADS, thestorage block dynamically allocated by the runtimesystem for subschema, database, work, and maprecords used by a dialog. An application can haveone primary RBB and as many secondary RBBs asneeded. The size of the RBB is specified by thePRIMARY POOL and SECONDARY POOLparameters of the ADSO system generationstatement.

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

record ID. A number that uniquely identifies eachrecord type in the database. Record IDs areassigned explicitly by the DBA or automatically bythe schema compiler.

record lock. Under the central version, a lockplaced on a record occurrence to prevent access toand/or update of that record occurrence. Recordlocks are used to protect the integrity of databaserecords (for example, preventing concurrent updatingof an occurrence by two or more transactions).Record locks are never maintained for transactionsoperating in local mode since concurrent update isprevented by physical area locks. See also locking.

record occurrence. A collection of related dataelement values accessible as a unit through CAIDMS/DB. A record occurrence corresponds to arow in a data table.

record prefix. The part of a record occurrence thatdescribes the set relationships for the record. Theprefix contains pointers to the next, prior (ifapplicable), and owner (if applicable) records in allsets in which the record participates.

record type. In CA IDMS/DB, a defined category ofinformation in the database, representing a group ofsimilar record occurrences. (For example, the DEPT

record type provides a template for data about alldepartments within the organization.)

record-type diagram. A graphic representationused to define the characteristics of a record type inthe database. A record-type diagram contains suchinformation as record name, id number, and length.Record-type diagrams are used within a datastructure diagram to define the entire database. Seealso data structure diagram.

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

recovery unit. The part of a transaction that fallsbetween two checkpoints.

reentrant pool. The storage space in memory intowhich reentrant programs and tables are loaded forexecution. Reentrant pool specifications are part ofa system's definition.

reentrant program. A program that dynamicallyacquires all variable storage and does not modify itsown code.

referenced table. The table in a referentialconstraint that contains the primary key. To assurereferential integrity between two tables, a row in thereferenced table cannot be deleted or have itsprimary key altered if the primary key value exists asa foreign key in the referencing table.

referencing table. The table in a referentialconstraint that contains the foreign key. To assurereferential integrity between two tables, a row can beinserted in the referencing table only if the value ofits foreign key exists as a value in the primary key ofthe referenced table.

referential constraint. A constraint that defines arelationship between two tables. A referentialconstraint identifies a foreign key in the referencingtable whose value must exist as a value in theprimary key of the referenced table.

referential integrity. In CA IDMS/DB, the dataintegrity rule that guarantees consistency betweentables that share a common column value. Forinstance, referential integrity would ensure thatcustomer order information is not added to thedatabase unless the customer has already beenadded. See also integrity, recovery.

Glossary 51

reflexive join. A generic relational operation thatyields a result table comprised of columns fromdifferent rows of the same table. Reflexive joins areused to implement bill-of-materials structures.

registered user. A user who is permitted to accessand/or update an entity occurrence in the datadictionary.

relational DBMS. A database management systembased on the relational model. See also relationalmodel.

relational key. In IDD, a user-defined keyword thatrelates entities of the same type. User-defined nestsare implemented through relational keys.

relational model. A data model in which data isrepresented in data tables consisting of rows andcolumns. Data tables can be manipulated with thethree relational operations: select, project, and join.See also relational DBMS.

relational table. See data table.

RELOAD utility statement. Reloads the databaseusing input created by the UNLOAD utility statement.

relocatable storage. Storage within the DC/UCFregion/partition that is eligible to be written to scratchacross a pseudo-converse. In CA ADS, storageused 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 thestorage pool but increases I/O to the scratch area.See also fast mode threshold, relocatable threshold.

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

relocated record. In CA IDMS/DB, a record that ismoved from its home page to another page by theRESTRUCTURE SEGMENT utility statement, themigration utility (RHDCMIG1 and RHDCMIG2), or asa result of processing an SQL DDL statement. Arelocated record is considered an SR3 system record

and the line index created for the record on the newpage contains a record id of 3. When CA IDMS/DBaccesses the record, it can return the record to itshome page if there is space available. See alsoSRn system record.

remote task. In a DC/UCF communicationsnetwork, a task that uses CA IDMS UCF to executeat a target node rather than at the host node. Thehost node performs terminal I/O operations. Thetarget node executes the program and eitherperforms database I/O or routes the request throughCA IDMS DDS to yet another node. In this case,both the CA IDMS UCF front end and the CA IDMSUCF back end are DC/UCF systems.

requestor lock table (RLT). In CA IDMS/DB, thelock table created for each transaction with longtermlocks.

required field. A field for which the terminaloperator must supply input data.

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

resident program. A program that is loaded atDC/UCF system startup and remains in the systemregion/partition for as long as the system is running.Resident programs are loaded into the appropriateprogram or reentrant pool. You designate residentprograms by using the system-generationPROGRAM statement.

resource. 1) A component or service used by theDC/UCF system at runtime. Resources include CPUtime, program pools, storage pools, tasks, queues,buffers, journals, RLEs, RCEs, DPEs, EREs,database-key locks, the log, the loader, and systemservice calls. 2) Within the security facility, entities inyour environment to which you control access. 3) Anobject to which requests are routed. See alsodatabase resource, global resource, resource nametable, system resource.

resource control element (RCE). The controlblock created when a task acquires a resource. TheRCE contains pointers to the task identifier and tothe resource being used.

resource link element (RLE). The control blockthat links all resources being used by a task.

52 CA IDMS Glossary

resource manager. A software component thatcontrols access to and the state of one or morerecoverable resources such as a database. A centralversion is an example of a resource manager.

resource manager interface (RMI). A softwarecomponent that facilitates communication between atransaction manager and a resource manager. TheRMI forwards requests from the transaction managerto its corresponding resource manager and returnsthe results of the operation.

resource name table. A table created by CA IDMSfrom the RESOURCE TABLE system generationstatement. The resource name table identifies thenodes on which resources in your DC/UCFcommunications network are located. DC/UCF usesthe resource name table at runtime to identify thelocation of resources required to satisfy databaserequests.

resource, securable. A CA IDMS/DB entity towhich you control access. For example, securableresources are users and system profiles.

resource timeout interval. The amount of time theDC/UCF system permits a terminal to be inactivebefore it invokes a resource timeout program.Terminal activity occurs when the user presses acontrol key (such as ENTER or PF1) that passesdata to the system. See also resource timeoutprogram.

resource timeout program. The program invokedby the DC/UCF system when the resource timeoutinterval expires. See also resource timeout interval.

resource type. Within the security facility, entitiesin your environment to which you control access.See also global resource, system resource, databaseresource.

response. See application response, globalresponse, internal response, local response, validresponse.

response field. The special 1- to 32-character mapfield in which terminal operators can enter aresponse field value (for a response process orapplication response) to select the next processing tobe performed. The $RESPONSE map field or theAGR-MAP-RESPONSE field of theADSO-APPLICATION-GLOBAL-RECORD can beused as the response field.

response field value. In a dialog, the field valueassociated with a specific response process in thedialog. At runtime, the user can enter the responsefield value in the map's response field to execute thatresponse process.

response process. An optional component of a CAADS dialog. A response process is executed afterthe end user presses a control key (such as PF1 orENTER) in response to the dialog's map. A givendialog can have any number of response processes.

A response process is defined as a standaloneprocess module in the data dictionary. You make aprocess module a response process for a dialog byusing the dialog compiler.

RESTORE utility statement. The utility thatrestores one or more areas in a database by copyingback the contents of a file created by the BACKUPutility statement.

restructure. The process of reorganizing thestructure (records, sets, areas) of an existingnon-SQL defined database. Restructuring is usuallyperformed to improve database efficiency or to meetchanging data management requirements. See alsoRESTRUCTURE CONNECT utility statement.

RESTRUCTURE CONNECT utility statement. Theutility that connects new prior and owner pointers inexisting sets.

restructure schema compare utility. SeeIDMSRSTC utility.

RESTRUCTURE SEGMENT utility statement. Theutility that modifies record occurrences to match newschema specifications.

RESYNCHRONIZE STAMPS utility statement. Inan SQL-defined database, the utility that comparesand updates synchronization stamps. Thecomparison is made between the stamps that residein an area of an SQL-defined database and theircounterparts that reside in the catalog. The utilitycan update either set of stamps.

retrieval path. The logical-record path (defined in asubschema) that carries out the OBTAINlogical-record function requested by an applicationprogram. See also OBTAIN path group.

retrieval area status. The status of an area definedto the runtime DMCL in which database transactions

Glossary 53

executing under the central version can retrieve butnot update data in the area; a local mode transactionor another central version can update the area.

retrieval ready mode. An area ready mode inwhich the readying transaction can retrieve, but notupdate, data in the area.

RHDCMAP1. A batch component of the MappingFacility. See also RHDCMPUT.

RHDCMIG1 and RHDCMIG2 utility programs.Utility programs that convert the DDLDML area ofrelease 10.0 dictionaries to the DDLDML area of arelease 12.0 dictionary.

RHDCMPUT. A batch component of the MappingFacility. See also RHDCMAP1.

RHDCOPTF. A module loaded at CA IDMS startupthat identifies the optional functionality activated forthe system. This load module is created byassembling and linking the source version of theRHDCOPTF module. The specific optionalfunctionality to be activated is set by using the#DEFOPT macro.

RHDCSMIG utility program. A utility program thatconverts user, task, and program security definitionsfrom a release 10.2 dictionary to preliminary release12.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 adatabase record occurs more than once in a singlelogical-record definition. Roles are typically used toprocess bill-of-materials structures.

rollback. The part of a backout process thatrestores the database to an earlier state. Therollback process restores the database by usingbefore images from a journal file. See also backout,rollback statement, ROLLBACK utility statement,recovery.

ROLLBACK. See also rollback statement.

rollback statement. A statement that initiates abackout operation. A backout operation results indatabase changes being backed out. The following

are examples of BACKOUT statements: ROLLBACKTASK, ROLLBACK.

ROLLBACK utility statement. The utility thatrestores all or part of a database to a previous stateby applying before images from the journal file.

rollforward. The process of restoring the databaseby using after images from a journal file (in contrastto rollback, which uses before images). Therollforward process is performed with theROLLFORWARD utility.

ROLLFORWARD utility statement. The utility thatrestores a database to a later state by applying afterimages from the journal file.

root. The portion of a variable-length record placedon the home page.

root page. See home page.

root segment. See fragment.

routine. In the context of SQL, an SQL routine.

row. A horizontal row of data in a table.

ROWID. A pseudo column associated with everybase table and view. The ROWID value for a row ofa base table uniquely identifies that row, althoughthe value can be assigned to another table row if theoriginal row is deleted. The ROWID column for aview is the ROWID column of the first base table inthe decomposition of the view.

row-level security. The ability to control access totable rows depending on the data they contain. InASF, row-level security acts in conjunction withpasskey security, which controls access to entiretables. See also passkey.

RRS. IBM's Resource Recovery Services.

RRS context. The application context in which aunit of recovery can exist.

RRS context services. The operating systemcomponent that manages RRS contexts.

RRS context token. A value that uniquely identifiesan RRS context.

RRS UR. A UR managed by RRS.

54 CA IDMS Glossary

RRS UR state. An attribute of an RRS UR thatidentifies a stage of the two-phase commit process.

RRS URID. A value that uniquely identifies an RRSUR.

Rtree. A data structure that contains the internalruntime representation of an SQL statement. Thisrepresentation directs the SQL runtime engine(module IDMSHLDB) in executing the statement.

RTSV checkpoint. A checkpoint writtenautomatically to the journal file each time CAIDMS/DB encounters an error while executing anSQL or physical DDL statement that updated thedatabase. During recovery, CA IDMS/DB rolls backto the journal record designated by the RTSVcheckpoint record.

RUAL. An abbreviation for the DC/UCF nucleusmodule RHDCRUAL. RUAL allocates anddeallocates system run units for executing tasks.

runaway interval. The amount of time the DC/UCFsystem permits a task to execute without returningcontrol to the system. A task returns control to thesystem for each system service call and eachdatabase operation.

runtime phase. The portion of the debuggingprocess that takes place during the execution of aprogram.

runtime system. A teleprocessing system thatdefines the operating environment for CA IDMS/DB.The runtime system provides both central versionservices and teleprocessing services.

run unit. A database session through which a CAIDMS database can be accessed using navigationalDML requests. See also extended run unit, systemrun unit, predefined run unit, database transaction,database session, SQL session.

scalar function. In SQL programming, a functionthat returns a single value. This value is derivedfrom the expression or expressions in the argumentsof the function invocation. For example, the scalarfunction DATE obtains the date from a specifiedvalue expression.

schema. The part of the database definition thatdescribes the logical structure of the database,including the names and descriptions of all tables,

elements, records, sets, and areas. One schemaexists per database.

schema compiler. A CA IDMS/DB-suppliedprogram that converts source non-SQL schema DDLstatements into description of a database and storesthis description in the data dictionary.

schema Data Description Language. The DDLthat defines a non-SQL schema.

schema DDL. See schema Data DescriptionLanguage.

schema-owned record. A database record definedthrough the schema compiler or copied into theschema.

scratch area. See DDLDCSCR area, DDLOCSCRarea.

scratch record. A record stored in the DDLDCSCRor DDLOCSCR area. Scratch records, once stored,are available to any task running on the same logicalterminal. Scratch records are maintained untilsystem termination.

screen. See panel.

SDEL task. In CA IDMS centralized security, aDC/UCF system task that deletes all privilegesassociated with logically-deleted authorizationidentifiers.

search condition. A boolean expression that yieldsa truth value. The operands of a search conditionare predicates, and the operators are the logicaloperators AND, OR, and NOT.

searched delete. Using SQL DML, removing rowsin a table by deleting each row in the table thatmeets the search criteria specified in the WHEREclause of the DELETE statement. See alsopositioned delete.

searched update. Using SQL DML, modifying datain a table for any row that meets the search criteriaspecified in the WHERE clause of the UPDATEstatement.

secondary key. An attribute in a data entity that isused by certain business functions to accessoccurrences of that entity. For example, anEMP-NAME might be the secondary key and

Glossary 55

EMP-ID might be the primary key for the entityEMPLOYEE. See also primary key, foreign key.

secondary storage pool. A DC/UCF storage poolother than pool 0 or 255. Secondary storage poolsare numbered from 1 through 254. DC/UCF usessecondary storage pools for user-type storage (ratherthan system storage). Secondary storage pools areoptional.

security domain. Under centralized security, theset of DC/UCF systems and local mode jobs thatshare a set of user definitions.

segment. A grouping of areas and files that containthe data in the database. A segment represents aphysical database usually defined by a singleschema. For CA IDMS/DB to access a segment atruntime, it must be included in the definition of aDMCL.

select. The generic relational operation throughwhich only specific rows of a data table areaccessed.

SELECT clause. In LRF, the section in aPATH-GROUP clause that delimits a path and,optionally, contains path selectors.

SELECT statement. An SQL database accessstatement that retrieves values from one or moretables and views and returns the values in the formof a result table.

selection criteria. An expression that specifieswhich rows of a data table are to be selected forprocessing. Selection criteria can include botharithmetic and logical operations.

selectors, path. See path selectors.

self-referencing relationship. A relationshipbetween different occurrences of the same entity. Abill-of-materials is an example of a self-referencingrelationship. See also bill-of-materials structure.

server node. In a DC/UCF communicationsnetwork, the DC/UCF system that actually servicesthe database request initiated by the host node. Seealso host node, target node.

service driver. A continuously active task thatprovides system services. See log service driver.

session default dictionary. The dictionary that willbe accessed within a user session if none other isexplicitly identified. The session default dictionarycan be established through profile attributes, DCUFstatements, SYSIDMS parameters, or the systemdefault dictionary.

set. 1) A synonym for set type. 2) A group ofrecord blocks that represent a CA IDMS set and areconnected to one another with set connection lines inthe CA IDMS Schema Mapper data structurediagram. Each set is numbered in the diagram with aunique set number. Sets are also listed, with theirdescriptions, in the Cross-Reference Report.

set connection. A physical line or series of lines,each with an arrow at the end that points toward amember of a set in the CA IDMS Schema Mapperdata structure diagram. Set connections connect anowner of a set and its members.

set junction character. Under the CA IDMSSchema Mapper, an uppercase letter O used at ajunction where a multi-member set connection linesplits into more than one line.

set membership options. See membershipoptions.

set number. A unique number assigned by CAIDMS Schema Mapper to identify each set and indexin a schema or subschema. Set numbers appear inthe CA IDMS Schema Mapper data structurediagram as part of set connection lines and indexlines. For multi-member sets, the set numberappears in the diagram next to the owner and eachmember. Set numbers are cross-referenced in theCross-Reference Report.

set occurrence. An owner record occurrence andall of its member record occurrences.

SET OPTIONS. The statement or function thatdefines default processing options for the currentsession of the command facility or a CA IDMScompiler.

set order options. See order option.

set type. A structure representing a relationshipbetween two or more record types, where one recordtype is the owner and the others are members.

56 CA IDMS Glossary

setup phase. The preliminary part of the debuggingprocess when, typically, programs are identified tothe debugger.

sharable transaction. A transaction initiated by adatabase session for which transaction sharing isenabled. A sharable transaction can be shared byother sessions that are peers of the initiating sessionand by sessions that are subordinate to the initiatingsession. See also non-sharable transaction, peersession, subordinate session.

shared cache. The Shared Cache feature allowsmultiple CA IDMS central versions to share databasebuffers for one or more files through the use of theIBM Parallel Sysplex Coupling Facility.

shared cursor. A cursor that is declared andopened in one program and accessed in anotherprogram, where both programs are included in thesame access module. See also cursor, updatablecursor, global cursor, external cursor.

shared retrieval ready mode. A retrieval readymode in which other transactions executingconcurrently under the central version can ready thearea in shared update, shared retrieval, protectedretrieval, or protected update modes.

shared storage. Storage in a DC/UCF storage poolthat, once allocated, is available to all tasks in theDC/UCF system. See also kept storage, userstorage.

shared update ready mode. An update area readymode in which other transactions executingconcurrently under the central version can ready thearea in shared update or shared retrieval readymodes.

share lock mode. A logical lock mode placed onareas and records that guarantees that no updatesare made to data while a transaction is accessing it.A share lock placed on an area implies a share lockon each record within the area. See also exclusivelock mode, null-lock mode.

shiftin character. A hardware-dependent characterthat indicates the beginning of a double-bytecharacter set string. A shiftin character can occupyfrom 1 to 3 bytes.

shiftout character. A hardware-dependentcharacter that indicates the end of a double-byte

character set string. A shiftout character can occupyfrom 1 to 3 bytes.

shutdown. The process of stopping DC/UCFsystem execution.

signoff function. In CA ADS, a system functionused in conjunction with signon security. Whenselected at runtime, the SIGNOFF function signs theuser off the application, then redisplays the screenfrom which the function was selected.

signon function. In CA ADS, a system functionthat validates a user's id and password when theuser invokes an application.

signon processing. Under centralized security,processing that identifies and validates the userrequesting CA IDMS services. It also processesuser-related information such as the list of groups towhich a user belongs and profile information.

signon profile. 1) A command list (CLIST) moduleassociated with a particular user (through a systemor user profile attribute) and executed automaticallywhen that user signs on to DC/UCF. 2) In CA OLQ,a series of CA OLQ commands saved as a qfile thatis executed automatically when a user signs on toCA OLQ. A signon profile can be associated with aparticular user to tailor the user's CA OLQ session.

SKIP Mode. An Animation Mode that you specifyduring an Animation Runtime Session inInterruptable Mode. CA ADS Alive responds bychanging the Animation Mode to STEP Mode and aspecified number of statements are bypassed beforedialog animation is stopped again. See also STEPMode.

SME. See space management entry (SME).

SMI. See space management interval (SMI).

SMP. See space management page (SMP).

socket. The end point of an IP communication.

sockets. An API used by two application programsto communicate with each other. It is most commonlyused in conjunction with TCP/IP.

socket descriptor. A value that uniquely identifiesa socket. The socket API runtime assigns the socketdescriptor.

Glossary 57

sorted set. In CA IDMS/DB, a set in which themember record occurrences can be retrieved inorder by database key, symbolic key, or generic key.

source dictionary. In CA IDMS Dictionary Migrator,the dictionary which acts as a reservoir for entitiesthat are available for migration into another (object)dictionary. Your source dictionary is not changedduring the migration process. Multiple sourcedictionaries can be used during each migration. Youcan also use your object dictionary as a sourcedictionary. See also object dictionary.

source record. At DC/UCF system generation, thedata dictionary record that represents anindependent entity. See also object record.

space available count. The number of bytes offree space on a database page.

space management entry (SME). In CA IDMS/DB,a 2-byte item on the space management page of anarea in the database. There is a one-to-onecorrespondence between the number of spacemanagement entries and the number of pages in thearea. The SMEs indicate the amount of availablestorage on the page.

space management interval (SMI). The number ofpages controlled by one space management page(SMP).

space management page (SMP). A page in anarea reserved by CA IDMS/DB to keep track ofavailable space on each page in that area. A spacemanagement page contains space managemententries.

spanned record. 1) A database record whoseoccurrences span VSAM control intervals. 2) Ajournal record that spans journal blocks.

spawning. The process by which the DBMScreates a new index level to accommodate newmembers added to a sorted indexed set.

special register. A system-supplied variabledefined by CA IDMS/DB for use in an SQL session.You use special registers in place of literals primarilyin SQL DML statements. For example, the specialregister, CURRENT DATE, can be used in WHEREclause selection criteria.

splitting. The process of creating a new systemindex record (SR8) on the same level as the originalsystem index record.

SQLCODE. A field in the SQLCA structure thatcontains a return code indicating the completionstatus of an SQL statement.

SQL Communication Area (SQLCA). A datastructure to which the DBMS returns informationabout the execution of an SQL statement.

SQL database access. A database access methodthat uses SQL DML to access data and that doesnot require knowledge of the physical structure of thedatabase. See also navigational database access.

SQL DDL. A data definition language that definesSQL entities such as tables and views.

SQL Descriptor Area (SQLDA). A data structure towhich the DBMS returns information about aprepared SQL statement. The SQLDA valuesdescribe the result of the prepared statement.

SQL DML. A data manipulation language thatobtains and updates the database by selecting,updating, inserting, and deleting rows in data tables.

SQL schema. A named collection of tables, views,and access modules. You create an SQL schemawith the CREATE SCHEMA statement.

SQL function. A builtin aggregate or scalar functionor a scalar function created by a CREATEFUNCTION statement.

SQL procedure. The entity created by a CREATEPROCEDURE statement. See also SQL routine,external SQL routine, table procedure.

SQL Quick Bridge. See CA IDMS SQL QuickBridge.

SQL routine. An SQL procedure, a tableprocedure, or an SQL function.

SQL session. A database session through which aCA IDMS database can be accessed using SQLDML requests. See also database session, run unit.

SQL statement cache. An area in memory used tostore the output from the compilation of a dynamicSQL statement in order to reduce overhead byeliminating redundant compilations.

58 CA IDMS Glossary

SQL trace facility. A facility activated by theSQLTRACE SYSIDMS parameter that you can useto trace the execution of SQL statements in a batchprogram.

SREPORTs. Statistics reports that summarize datacontained in the archived system log file.

SR. In CA IDMS/DB, one of seven system recordtypes used for space management:

■ SR1 Owner of the system-owned CALC set.An SR1 record occurs once for each page in anarea as bytes 5 through 16 in the page header.

■ SR2 A record that replaces records relocatedby the RESTRUCTURE SEGMENT utilitystatement, the migration utility (RHDCMIG1 andRHDCMIG2), and SQL processing following theaddition of a column to a table.

■ SR3 A record that identifies a relocated record.

■ SR4 A record that identifies fragments ofvariable-length records.

■ SR6 A dummy record that appears in thesubschema tables as a place holder for excludedowner or member record definitions in setrelationships.

■ SR7 Owner record in an index. An SR7 recordis stored CALC under the name of the indexedset and occurs once for each indexed set in thedatabase that does not have a user-definedowner record.

■ SR8 A record that contains index entries thatpoint to lower level SR8 records or to an indexedset's member record occurrences.

stack. The area at the end of a task controlelement (TCE) that is used by DC/UCF during taskexecution as a temporary work area and as a placeto save registers.

standalone CA ICMS. A CA ICMS environment inwhich CA IDMS/DB is not also installed.

standalone record. A database record that is notrelated to any other record through a set.

standalone table. For maps, an edit or code tabledefined independently in the data dictionary (byusing the TABLE statement). A standalone table canbe used by any record element that is associatedwith a map. See also built-in table.

standard collating sequence. A collatingsequence based on the EBCDIC value of the data.See also natural collating sequence.

starting point. Under CA IDMS Dictionary Migrator,this entity and all of its related entities are copiedinto the object dictionary. You determine what thestarting point is by specifying the entry point andwhatever option you choose to include in the LEVELparameter.

startup routine. The module that is executed tobegin the DC/UCF startup process. The startupprocess begins the execution of a DC/UCF system.

statistics reports. See SREPORTs.

status code. A 4-digit code returned by the systemto an application program to describe the completionstatus of a navigational DML command. The first twodigits represent a major code; the last two digitsrepresent a minor code.

status definition record. SeeADSO-STAT-DEF-REC.

STEP mode. A mode of application execution inwhich the current screen is redisplayed withmessages describing the results of the transactionbefore control is passed to the next sequentialscreen. STEP mode is the default in ADSA, ADSC,MAPC, and user-written applications. See alsoFAST mode.

STEP Mode. An Animation Mode that you specifyduring an Animation Runtime Session inInterruptable Mode. CA ADS Alive stops at everyline of code for the current process. See also SKIPMode.

storage cushion. Space reserved in a DC/UCFstorage pool for use by tasks that are alreadyexecuting.

storage mode. The characteristic of databaserecords that indicates whether the length of a storedrecord is fixed (F), variable (V), fixed compressed(FC), or variable compressed (VC). See alsolocation mode.

storage pool. The storage space in memory that isallocated for work areas and control blocks requiredby DC/UCF system and by programs executingunder the DC/UCF system. Typically storage poolshold: program variable storage, COBOL working

Glossary 59

storage, variable portions of CA ADS dialogs,subschema tables, and access modules, currencyblocks, database lock tables, buffer pools, user tracebuffers, and secondary allocations of null PDEs.Storage pool specifications are part of a system'sdefinition. See also primary storage pool.

storage protection. A measure that protects pagesin the system region/partition from being overwritten.

STORE. The navigational database access functionthat adds a record occurrence to the database.

STORE logical record. The LRF database accessfunction that adds a logical-record occurrence to thedatabase.

STORE path group. A collection of paths(predefined in a logical-record subschema) designedto service application programs that request aSTORE logical-record function.

stream. An ordered sequence of bytes.

subarea. A subdivision of an area's page range.

subordinate session. A database session initiatedwhile processing a request for another session. Mostcommonly, a subordinate session is initiated by anSQL routine invoked while processing an SQLrequest. However, a subordinate session can alsobe initiated by a database procedure invoked whileprocessing a navigational DML request. See alsodatabase session, encompassing session, peersession, top-level session, SQL routine.

subschema. A program view of a non-SQL defineddatabase used at runtime, consisting of all or asubset of the data elements, record types, set types,and areas defined in the schema. Logical-recordcomponents are also defined in the subschema.

subschema compiler. A CA IDMS/DB-suppliedprogram that converts source subschema DDL intosubschema descriptions. The subschema compilerstores source descriptions in the data dictionary andstores load modules in the DDLDCLOD area.

SUBSCHEMA-CTRL. Names the IDMScommunications block through which an applicationprogram and the DBMS communicate.

subschema Data Description Language. TheDDL that defines a subschema.

subschema DDL. See subschema DataDescription Language.

SUBSCHEMA-LR-CTRL. Names the logical-recordrequest control (LRC) block through which anapplication program and LRF communicate.

subschema usage mode. The type of databaseaccess permitted to programs that use a particularsubschema: logical records only, database recordsonly, or mixed (both logical records and databaserecords).

subsystem. An IDD entity type used to documentautomated or manual data processing systems. Seealso system.

suspense file. In CA ADS Batch, a file defined tostore input records found to contain edit errors atruntime.

SVC. See CA IDMS SVC.

sweep the database. See area sweep.

symbolic key. One or more user-defined recordelements used to store or retrieve data, asdetermined by application requirements. The keycan be a primary key, foreign key, or some othermeaningful element in the record. Under CAIDMS/DB, keys are used to store data through theCALC location mode and/or to sort data in indexedand chained sets. Database keys (db-keys) are notsymbolic keys.

symbolic parameter. A parameter that connects ageneric logical definition of a subarea, displacement,or index to a specific definition in the physicaldatabase definition. With symbolic parameters,multiple physical databases can use the sameschema definition.

symbol table. A dialog generation option used tospecify whether or not a symbol table is created for adialog. The symbol table facilitates the use ofelement names and process line numbers by theonline debugger.

synchronization stamp. An internally-generatedtimestamp used to ensure that the definition of atable matches the data being accessed.

synonym. An alternative name that is defined foran entity in the data dictionary. Synonyms aredefined in DDDL statements or in the schema.

60 CA IDMS Glossary

syntax converter. In IDD, the facility that capturesCOBOL or PL/I record and element definitions andadds them to the data dictionary.

syntax files. Under CA IDMS Dictionary Migrator, acollection of files that contain source statementsused as input to the CA IDMS utilities and compilers.The syntax files permit completion of the movementof entities and entity components from one or moresource dictionaries to the object dictionary.

SYSCA schema (SQL). At sites with the SQLoption, the schema that contains the CA-suppliedviews of the SYSTEM tables and records in theIDMSNWK schema. These views restrict access totable definition information based on a user'sSELECT authority. See also SYSTEM schema(SQL).

SYSCTL file. A file used by a batch or CICSapplication to direct its CA IDMS requests to a targetsystem and/or database. The SYSCTL file containsvalues that define the DC/UCF system, CA IDMSSVC, node, and database the program will use.

sysgen. An abbreviation for system generation.See also system generation.

SYSIDMS parameter file. A parameter file addedto the JCL stream of batch jobs running in localmode or under the central version. It specifies:physical requirements of the environment, such asthe DMCL and database to use at runtime; runtimedirectives that assist in application execution;operating system-dependent file information.

system. 1) A DC/UCF system or central version.2) An IDD entity type used to document automatedor manual data processing systems. See alsosubsystem.

system dictionary. The dictionary that includes allinformation required to establish, maintain, andcontrol the processing environment. It contains theDC/UCF system definition and physical databasedefinitions. Each runtime environment must have asystem dictionary named SYSTEM which containsthe following areas: DDLDML, DDLDCLOD,DDLDCMSG, DDLCAT, DDLCATX, andDDLCATLOD.

system function. 1) In CA ADS, a predefinedfunction available to ADSA-generated applications.The system functions are POP, POPTOP, TOP,

RETURN, HELP, QUIT, ESCAPE, SIGNON,SIGNOFF, FORWARD, and BACKWARD. A systemfunction is incorporated into an application when thatfunction has been associated with a valid response.2) A DC/UCF system task (such as SIGNON, DCMT,and DCUF).

system generation. The process of using thesystem-generation compiler to populate the datadictionary with the definition of a DC/UCF system.

system-generation compiler. A CAIDMS/DB-supplied program that accepts sourcestatements defining a DC/UCF system and storesthe definition in the data dictionary.

system index. A standalone index structureproviding alternate access to entity occurrences.The root (or top index entity) is an SR7 entityoccurrence. The is an internal record type with alocation mode of CALC.

system log. See log.

system mode. The execution mode in which aprogram can access all storage pages in theDC/UCF region/partition.

system-owned indexed set. An indexed set inwhich the owner record is a system-defined SR7record. The location mode of an SR7 record isCALC on the set name for non-SQL defined indexesor on an internally-generated name for SQL-definedindexes. There is at most one occurrence of an SR7record for each system-owned index. See alsouser-owned indexed set.

system photo. The information at the beginning ofa system or task snap that shows all currentlyexecuting tasks and the resources allocated to eachtask.

system profile. A profile that includes attributesthat apply to users of a specific DC/UCF system.For example, a system profile might identify thename of a dictionary a user can access. See alsouser profile.

system record. In CA IDMS/DB, one of the ninesystem record types (for example, SR1 and K0).System records are used internally by CA IDMS/DBto perform space management functions.

system reports. See CREPORTs.

Glossary 61

system resource. Within centralized security, anentity shared system-wide by CA IDMS processingunder the central version. See also global resource,database resource.

system run unit. A run unit initiated by theDC/UCF system as part of providing a standardservice such as writing a message. You canpredefine system run units. See also predefined rununit.

SYSTEM schema (SQL). At sites with the SQLoption, the schema associated with the tables thatcomprise the catalog component of the dictionary.See also SYSCA schema (SQL).

system storage pool. See primary storage pool.

system task. A CA IDMS supplied task thatperforms one of a variety of DC/UCF system supportservices at runtime. System tasks include theDCMT, DCUF, SIGNON, and SIGNOFF tasks.

system trace. The DC/UCF debugging aid thatrecords the system service modules used inprocessing a DC/UCF request in a trace table.When a program issues a SNAP request, DC/UCFwrites the trace table to the log.

system 90. The executable demonstration systemgenerated at installation time. This system providesthe batch simulator system used to rundemonstration jobs. Later in the installationprocedure, system 90 can optionally be generated asan online system with one terminal (the console) andany number of specified users.

system 99. A DC/UCF system that is generated atinstallation time. System 99 provides a samplesystem configuration. This base system can be usedto generate other DC/UCF systems.

table. 1) An IDD entity type used to define edit andcode tables. Edit and code tables are used duringautomatic editing to validate and encode/decodedata values in map data fields. 2) A CA IDMS/DBdata table. See also data table. 3) Any collection ofdata in tabular form.

table data area. In ASF, the area in which tabledata is stored, as opposed to the table definitionarea in which table definitions are stored. Tabledefinitions and data should not be stored in the samearea. See also area, IDMSR-AREA2.

table definition area. In ASF, the area of a CAIDMS/DB database used to store definitions of datatables, as opposed to the table data area in whichtable data is stored. Table definitions and datashould not be stored in the same area. See alsoIDMSR-AREA.

table definition record. In ASF, a record, stored inthe table definition area of the database, thatcontains the definition of a data table. The definitionrecord is stored separately from the actual data forthat data table.

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

table procedure. The entity created by a CREATETABLE PROCEDURE statement.

tabular data. See data table.

tailored diagram. A data structure diagram as itappears after you have used at least one optionalCA IDMS Schema Mapper parameter statement tomodify the layout or format of the diagram that isgenerated by default (use of the PROCESSstatement only).

target node. In a DC/UCF communicationsnetwork, the DC/UCF system that is identified toservice a database request by the host node. Seealso host node, server node.

target page. The database page that the DBMSuses when trying to store or access a particularrecord.

task. 1) The basic unit of work under DC/UCF thatconsists 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 todocument teleprocessing system tasks.

task application table (TAT). In CA ADS, the tablethat contains a list of all task codes and theapplications they activate. The TAT is updated in thedata dictionary by the application compiler and isused at runtime. The TAT can be built and migratedby using the ADSOTATU utility. See alsoADSOBTAT, ADSOTATU.

task code. The unique name that identifies a taskto DC/UCF. The user types the task code inresponse to the DC/UCF system prompt. Task

62 CA IDMS Glossary

codes are defined at system generation or by usinga DCMT VARY DYNAMIC TASK command.

task control element (TCE). The control block thatties together all of the resources of a task, indicatesthe status of the task, and provides a stack ofsystem working storage and user registers.

task definition element (TDE). The DC/UCFcontrol block that specifies general taskcharacteristics. Task definition elements areassigned either at system generation or by using theDCMT 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/IPimplementation.

temporary table. A table created by an SQLsession that exists only for the duration of thetransaction in which it is created. The table can bepopulated and that table data can be manipulatedwithin the transaction.

terminal I/O. The input/output operations betweenmain storage and a user terminal. Terminal I/O iscontrolled by a teleprocessing monitor.

terminating task data transfer. A means of datatransfer from program storage to a terminal or deviceusing CA IDMS UCF to pass the data and controlserially between a CA IDMS UCF front end and backend. The front end initiates a task on the back endsystem and waits until the task is complete to returnthe requested information. See also non-terminatingtask data transfer.

test mode. The mode of DC/UCF that you use toexecute test versions of programs. You specify testmodes by using the DCUF TEST command. For CAADS Batch applications, you specify test modes byincluding the test control parameters in the jobstream.

With test mode in effect, DC/UCF first searches forprograms whose version number matches thatspecified by the DCUF TEST command. You canspecify version numbers for dictionary load modules.Additionally, z/OS users can specify test loadlibraries in the startup JCL by using Vnnnn DDstatements, where nnnn corresponds to the testversion number.

third normal form. See normalization.

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

ticker interval. The frequency with which theDC/UCF system checks for time-related events (suchas runaway tasks).

TIME checkpoint record. The checkpoint thatmarks the initialization of the journal buffer. Thedate and time values for this checkpoint are suppliedwhen the journal buffer is written to the journal file.

top-level session. A database session that has noencompassing session. See also database session,encompassing session, subordinate session, peersession.

TP-monitor program. A program that executesunder a teleprocessing (TP) monitor other than CAIDMS/DC. TP-monitor programs use central versionoperations to access CA IDMS/DB databases.

trace. Under CA IDMS Dictionary Migrator, toidentify an entity, its related entities, its relatedcomponents, and all of the connections among theseentities and components.

trace facility. Any debugging tool used to record asequence of runtime commands, programs, ormodules. CA IDMS provides the following tracefacilities: batch trace facility, database trace facility,system trace facility, user trace facility, and CA ADSbatch trace facility.

transaction. 1) A database transaction. 2) Theseries of tasks that perform one logical activity. Forexample, a transaction typically includes all tasksthat display, retrieve, and process data on a singlemap. Note, this type of transaction is different than adatabase transaction, which CA IDMS/DB uses to

Glossary 63

manage resources and control recovery. See alsodatabase transaction. 3) An IDD entity type used todocument collections of functions or processes.

transaction branch. A portion of a transaction thatis a separately identifiable unit of work within whichdeadlocks cannot happen. Each database sessionthat does not share its transaction with anothersession causes a new transaction branch to becreated. A hierarchy of transaction branches can becreated. The target of a commit or backout operationis always a single transaction branch, but theoperation includes all subordinate branches of thetarget.

transaction branch identifier (BID). A 16-bytevalue that uniquely and globally identifies atransaction branch. It is composed of the 8-bytenode name of the local central version and an 8-bytehexadecimal value. Once assigned to a transactionbranch, the BID never changes even if the branchparticipates in serially-executed transactions.

transaction manager. A software component thatdirects commit and backout processing. In adistributed transaction, multiple transaction managerscan be involved in a single commit or backoutoperation. If so, their actions are coordinated toachieve a consistent result. Every central versioncontains a transaction manager as a component.

transaction sharing. A facility that allows two ormore database sessions to share a singletransaction in order to eliminate inter-sessiondeadlocks.

transaction lock. A lock set and examined by CAIDMS/DB in order to control access to individualrecords and areas. See locking.

transaction state. The state in which an SQLsession can access data. READ ONLY means thesession can read, but not update, data. READWRITE means the session can read and updatedata.

transaction statistics. Statistics collected byDC/UCF for a transaction.

transfer control facility (TCF). The CA IDMSsoftware tool that enables the terminal user totransfer from one CA IDMS online tool to anotherwithout having to return first to DC/UCF.

Transfer File. An output file that reflects the layoutand format of a CA IDMS Schema Mapper datastructure diagram. The Transfer file containsparameter statements. You can use it as atime-saving device, as input, when recreating ormodifying a CA IDMS Schema Mapper data structurediagram.

TRANSIENT READ isolation level. An isolationlevel in which CA IDMS/DB places no locks on rowsaccessed by the session and prevents thetransaction from performing updates. This isolationlevel provides no protection from the effects ofconcurrent database transactions; that is, it allows asession to read uncommitted data and allows othertransactions to update the data. See also CURSORSTABILITY isolation level, isolation level.

transient retrieval area status. The status of anarea in which database transactions executing underthe central version retrieve data using no recordlocks. A local mode application or another centralversion can concurrently update the area.

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

transmission control protocol (TCP). A reliable,connection-oriented IP protocol.

two-phase commit. 1) A protocol that is used toachieve a coordinated commit for a distributedtransaction. 2) A commit operation that uses atwo-phase commit protocol.

transparency. In IDBCOMM, a process of datatransmission that prevents data from being mistakenfor control characters and from being convertedimproperly during transmission.

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

When transparency is requested and the type notspecified, the default is 6-bit format. Data is groupedinto 6-bit chunks during the conversion process.

TUNE INDEX. The Tune Index Utility walks a sortedindex in order to cause the adoption of orphanedindexed records. An orphaned indexed record is a

64 CA IDMS Glossary

record whose index pointer does not point back tothe index record (SR8) which contains the record'sindex entry.

UCF system. A database/data communicationssystem that includes CA IDMS/DB and CA IDMSUCF. A CA IDMS UCF system does not include CAIDMS/DC.

UDAS. The CA IDMS UCF Distributed ApplicationSupport Feature. With this feature, an applicationmay be distributed between the front-end system andthe back-end system in an environment that consistsof one of two CA IDMS/DC systems or a CAIDMS/DC back end and a front end on a systemusing one of the TP-monitors supported by CAIDMS/DC.

UDP. See user datagram protocol.

unit of recovery (UR). A set of changes that iscommitted or backed out as a single unit.

unique constraint. A constraint that requires eachrow of a table be unique with respect to the value ofa column or combination of columns. A uniqueconstraint is defined when an index or CALC key isdefined with the UNIQUE parameter. See alsoreferential constraint.

unique key. In logical database design, an attributeor combination of attributes whose value(s) uniquelyidentifies an occurrence of an entity or relationship.

unlinked constraint. A referential constraint forwhich CA IDMS/DB does not maintain a physicallinkage between the rows in the referenced andreferencing tables. Instead, the referencing tablemust have a CALC key or index key defined on theforeign key and the order of the columns in theprimary key must match the order of columns of theforeign key.

unlinked index. A system-owned index in whichthere are no index pointers in the member records.

unlinked relationship. A relationship in which noembedded pointers are used to link related entityoccurrences. See also linked relationship.

unload/reload. The process of unloading andreloading a database or portion of a database. Theunload/reload process is performed with the CAIDMS/DB utility statement UNLOAD and RELOAD,

and is sometimes required when restructuring adatabase.

UNLOAD utility statement. The utility that unloadsrecords from one or more areas of the database inpreparation for reloading.

UNLOCK utility statement. The utility that removesthe external lock on an area.

unsorted set. A set in which the member recordsare not maintained in sequence by a symbolic keyvalue.

unstructured object. See free-form object.

updatable cursor. A cursor that allows the programto update or delete the row on which the cursor ispositioned. See also cursor, global cursor, sharedcursor, external cursor.

updatable view. A view derived from a single tableor view through which you can update, insert, anddelete rows.

update area status. The status of an area in whicha database session executing under the centralversion can retrieve and update data within the area;local mode applications and other central versionscan retrieve from, but not update, the area.

update-intent-exclusive lock. A logical lock placedon an area that allows exclusive locks to be placedon records within the area by the issuing transaction,but not by other transactions. See also intent lock,intent-share lock, intent-exclusive lock.

update path. The logical-record path (defined in asubschema) that carries out the ERASE, MODIFY, orSTORE logical-record function requested by anapplication program.

update ready mode. An area ready mode in whichthe readying transaction can both update andretrieve data within the area.

UPDATE statement. An SQL database accessstatement that modifies the values in one or morerows of a table.

UPDATE STATISTICS utility statement. For anSQL-defined database, the utility that updatesstatistical information maintained in the dictionary forone or more tables.

Glossary 65

upload. The transfer of data from a personalcomputer or minicomputer to CA ICMS.

UR. See unit of recovery.

USA date/time format. A date/time format thatcomplies with the IBM USA standard: DATE asmm/dd/yyyy and TIME as hh:mm AM and hh:mmPM.

user. Under centralized security, an entity createdwith the CREATE USER statement that defines auser in the user catalog.

user catalog. Under centralized security, therepository that contains the definition of allauthorization IDs within the CA IDMS securitydomain, definitions of user profiles, and privilegesheld by users and groups on global resources. Seealso global resource.

user datagram protocol (UDP). An unreliable,connectionless IP protocol.

user-defined edit module. In the DC/UCF mappingfacility, an Assembler program that can be coded tosupplement or replace automatic editing and errorhandling on mapin and/or mapout. See alsoautomatic editing, error handling.

user-defined entity. An IDD entity type used todocument information that does not conform to anyof the standard entity types.

user-defined nest. A relationship betweenoccurrences of a single entity type expressed interms that are meaningful to IDD users.

user exit. A predefined entry point in a DC/UCFsystem. User exits let you receive control at specifictimes during system execution. You can use theseexits to implement various types of site-specificprocessing, including statistics collection and securitychecks.

user function. See DCUF command.

user mode. The execution mode in which aprogram can access only storage pages that it owns.

user-owned indexed set. An indexed set in whichthe owner of the set is a user-defined record. Seealso system-owned indexed set.

user profile. A profile that includes attributes for auser session on any DC/UCF system in the securitydomain. For example, system-independentinformation such as the user's employee number.See also system profile.

user program function. See program function.

user response. In CA ADS, the combination of acontrol key and response field value (if any) that aruntime user enters on mapin. In an application, theuser response must be a valid application response.

user storage. Storage in a DC/UCF storage poolthat, once allocated, is available for use by therequesting task. See also kept storage, sharedstorage.

user trace facility. The DC/UCF debugging toolthat saves information related to programs executingfrom a logical terminal. The user trace facility iscontrolled by the DCUF SET USERTRACEcommand. The facility captures the program name,request type, and system registers for each programexecuted from a logical terminal.

user-written edit module. See user-defined editmodule.

validate. In system generation, the process used toverify and cross-reference relationships among allcomponents of the system definition.

VALIDATE utility statement. The utility that checksreferential constraints for a referencing table, makingsure that referenced rows exist and contain theappropriate column values.

valid response. In CA ADS, a global or localresponse that is defined as valid for a particularapplication function. More than one response can bevalid for a single function.

value. In logical database design, a singleoccurrence of an attribute.

variable dialog block (VDB). In CA ADS, anonreentrant table used by the runtime system toobtain user-specified information about a particulardialog. The VDB is dynamically created for eachdialog when the dialog is initiated. It resides in thestorage pool and contains header information, themap request block (MRB) for the dialog (if any), anda variable record element (VRE) for each recordused in the dialog.

66 CA IDMS Glossary

variable field. In the Mapping Facility, any mapfield whose value can be changed during mapexecution. The following types of fields are variable:data fields, message fields, page fields, andresponse fields.

variable-length record. In CA IDMS/DB, a recordwhose length depends on a variable field (that is, arecord defined with an OCCURS DEPENDING ONclause).

variable record element (VRE). In CA ADS, acontrol block that contains variable runtimeinformation on a record used in a dialog. One VREis established for each record in a dialog. Internally,CA IDMS/DB also treats fixed-length compressedrecords as variable-length records.

VDB. See variable dialog block (VDB).

VECT. The DC/UCF symbol used to designate thedebugger's vector table.

VIA location mode. The location mode thatclusters member records in the same physicallocation for efficient database access. Optionally,VIA can cluster member records with their owners.

VIA overflow. See overflow.

view. 1) A table that is not physically stored in thedatabase but instead derives data from one or moreother tables each time the view is requested. 2) Asubset of a record definition that, through thesubschema, restricts the elements of the record thata given program can access. A subschema view fora record is defined through the DDDL or subschemacompiler. See also table, base table, updatableview.

Visual DBA. See CA IDMS Visual DBA.

VM/ESA option. In CA IDMS/DB installations, anoption that allows a DC/UCF system to run in aVM/ESA virtual machine. The VM/ESA option alsomakes communication possible from one virtualmachine to another in a VM/ESA environment.

Vnnnn. The generic term for the ddname orlinkname of a test load library. Nnnn indicates theDC/UCF test version under which load modules fromthis library are used. For example, if a user specifiesDCUF TEST 6, DC/UCF searches V0006 beforesearching the current loadlist. Test load libraries are

available under z/OS, z/VM and VM/ESA, andBS2000/OSD.

VRE. See variable record element (VRE).

walking a set. A retrieval process in which aprogram using navigational DML or the DBMS, inresponse to an SQL request, can access all of themembers of a set starting with the owner recordoccurrence and accessing each member occurrencein the set until the program reaches the owner recordagain.

wallpapering. The process of bursting andassembling a CA IDMS Schema Mapper datastructure diagram and (probably) hanging it on a wallfor viewing.

warmstart. A method of automatic databaserecovery that occurs when CA IDMS/DB recognizesa system failure when it restarts the system. It usesthe journal files to rollback all transactions that wereactive when the system failed. To do this, itidentifies the disk journal file active at the time offailure, locates the last journal record written beforethe system failed, and rolls back and writes ABRTcheckpoints for all incomplete transactions.

WCC. See write control character (WCC).

weak entity. An entity in the database that isidentified only by its relationship with another entity.Typically a weak entity has a primary key thatcontains only one foreign key.

weight factor. A number assigned by the user to aDDS port and used by DC/UCF to select the pathbetween two CA IDMS DDS nodes when more thanone path is available.

WHERE clause, path-DML. In LRF, the clause in apath-DML command that specifies selection criteriato identify the desired database-record occurrences.

WHERE clause, program request. In LRF, theclause in a logical-record program request thatspecifies selection criteria to identify the desiredlogical-record occurrences.

WHERE clause, SQL. In SQL, the clause in anSQL DML statement (for example, SELECT andUPDATE) that specifies selection criteria to identifythe desired table rows.

Glossary 67

wildcard. A single character that represents one ormore characters in a string. An entity name with awildcard character identifies all the entities whosenames match the pattern established by thewildcarded name.

window. In CA IDMS Performance Monitor, theportion of a screen that contains data for a specificstatistic or help topic. CA IDMS PerformanceMonitor windows allow you to control rows andcolumns of data that exceed the width and depth ofthe terminal screen.

work record. See dialog work record, map workrecord.

write control character (WCC). In a map, theinternal character that holds various mapoutspecifications for the display of that map.

XA interface. A specification for the interactionbetween a transaction manager and a resourcemanager that enables a two-phase commit operationto be performed.

XA XID. An identifier assigned to a transaction by atransaction manager using the XA interface.

XCTL. Part of the version of the Assembler DMLtransfer statement that requests DC/UCF to passcontrol to a program, but not to return control to theprogram issuing the transfer statement.

3270 simulation facility. The DC/UCF tool that youuse to simulate 3270-type terminal operations atnon-3270-type terminals or in batch mode. See alsobatch simulation.

68 CA IDMS Glossary