HP OpenVMS Systems Documentation
|Example 8-7 Sample Run of PERSONNEL-UPDATE Before Promotion|
EMPLOYEE LISTING MANAGER OF GROUP A IS: HOWELL GROUP B2 SUPERVISOR IS: MOORE GROUP B2 EMPLOYEES EMPLOYEE NUMBER EMPLOYEE NAME 05500 BAKER 02000 DEANE 07400 FIFER 05000 KLEIN 01400 RILEY GROUP B1 SUPERVISOR IS: NOYCE GROUP B1 EMPLOYEES EMPLOYEE NUMBER EMPLOYEE NAME 04000 BURLEW 07000 NEILS 01000 RAVAN
|Example 8-8 Sample Run of PERSONNEL-UPDATE After Promotion|
EMPLOYEE LISTING MANAGER OF GROUP A IS: HOWELL GROUP B3 SUPERVISOR IS: KLEIN GROUP B3 EMPLOYEES EMPLOYEE NUMBER EMPLOYEE NAME 07000 NEILS 01400 RILEY GROUP B2 SUPERVISOR IS: MOORE GROUP B2 EMPLOYEES EMPLOYEE NUMBER EMPLOYEE NAME 05500 BAKER 02000 DEANE 07400 FIFER GROUP B1 SUPERVISOR IS: NOYCE GROUP B1 EMPLOYEES EMPLOYEE NUMBER EMPLOYEE NAME 04000 BURLEW 01000 RAVAN
The italicized words in this list are relevant to (both) database programs and other programs.
access mode: In a database environment, that part of
the COBOL data manipulation language READY statement's usage mode that
describes what capabilities your run unit will have with regard to
records in the realm you have readied. The access mode can be RETRIEVAL
(read only) or UPDATE (read and write). See also usage mode
and allow mode.
allow mode: That part of the DML READY statement's
usage mode that describes what you will allow other run units to do
while your run unit works with storage areas in the realms you have
readied. The allow mode can be CONCURRENT, PROTECTED, EXCLUSIVE, or
BATCH. See also usage mode and access mode.
at end condition: A condition caused during FETCH or
FIND statement execution for a database, when no next logical record
AUTOMATIC member: A database record that automatically
becomes a member of a given set when the record is stored in the
database. AUTOMATIC set membership is declared in the schema.
available mode: The state of a database record that
allows its use by the Database Control System (DBCS) in executing an
operation requested by a given run unit. A record is available if it is
stored in a database area accessible to the DBCS, and the intended use
does not conflict with the processing requirements of concurrent run
Bachman diagram: A graphic representation of the set
relationships between owner and member record types used to analyze and
document a database design.
BATCH RETRIEVAL usage mode: The state of a realm which
allows concurrent run units to update the realm while the current run
unit accesses a copy of the realm which was made at the point when the
READY was executed.
BATCH UPDATE usage mode: The state of a realm in which
the current run unit may access or update any data in the realm while
allowing concurrent run units to retrieve from the realm but preventing
them from updating the realm. Effectively similar to PROTECTED UPDATE.
CDD/Repository: See Oracle CDD/Repository.
CODASYL: An acronym for the COnference on DAta SYstems
Languages, the committee that produced the document titled CODASYL
COBOL Journal of Development. This document serves as the basis
for the standardization of the Oracle CODASYL DBMS data manipulation language
CONCURRENT usage mode: The state of a realm in which
it may be accessed by concurrent run units.
concurrency: The simultaneous use of a database or a
sequential, relative, or indexed file by more than one user.
currency indicators: Pointers maintained by the
Database Control System (DBCS) that serve as place markers in the
database for your run unit.
data definition languages (DDL): The languages used to
describe schemas, subschemas, and storage schemas. See also schema
DDL, storage schema DDL, and subschema DDL.
data manipulation language (DML): The Oracle CODASYL DBMS
language interface that permits programs to interact with Oracle CODASYL DBMS
data-name: A user-defined word that names a data item
described in a data description entry. In general formats, data-name
represents a word that must not be reference-modified, subscripted,
indexed, or qualified unless specifically allowed by rules of the
database: A collection of related records on a mass
storage device. All of the records and sets are controlled by a
database administrator (DBA): The person or group of
people responsible for planning, designing, implementing, and
maintaining a database.
database aggregate: A subschema group item or table
defining one or more database items. A database aggregate can contain
one or more database aggregates.
Database Control System (DBCS): The component of
Oracle CODASYL DBMS that, together with the OpenVMS operating systems,
provides run-time control of database processing.
database exception condition: The state that exists
for a run unit when the DBCS detects a situation for that run unit that
requires special handling.
database item: An elementary data item defined in a
subschema. It corresponds uniquely to a data item in the subschema's
database key (dbkey): A numeric value that uniquely
identifies a record in the database. The Database Control System
assigns the value when a record is stored in the database. Although
your run unit cannot directly access database keys, they are used by
the Database Control System whenever you store, retrieve, or manipulate
a record. Dbkey values are notated in the form x:y:z, where
x is the area, y is the page, and z is the
database key condition: A condition for which a truth
value can be determined, that: (1) two specified database key values
identify the same database record, (2) a database key value is null,
(3) or a key value is identical to any database key value in a keeplist.
database key identifier: A phrase in a COBOL source
program that refers to a database key value within a currency indicator
or a keeplist.
database management system (Oracle CODASYL DBMS): A system
for creating, maintaining, and accessing a collection of interrelated
database records that may be processed by one or more applications
without regard to physical storage. Oracle CODASYL DBMS establishes logical
relationships among records. Data is described independently of
application programs, providing ease in application development, data
security, and data visibility. Oracle CODASYL DBMS is available under a
database object: A set type, record type, realm,
record key, or data item defined in the schema.
database page: The unit of data transfer between
Oracle CODASYL DBMS and the OpenVMS operating systems. Each database page
consists of one or more blocks of 512 bytes each.
Database Query utility (DBQ): An online interactive
utility that allows the user to access a Oracle CODASYL DBMS database
directly and that shows the results of each execution of a DML
statement. This utility provides low-level query facilities for data
DB-CONDITION: A database special register whose value
indicates either a successful condition or an exception condition.
DB-CURRENT-RECORD-ID: A database special register
containing the subschema user ID number (UID) of the record type of the
current record of the run unit. It contains zero if there is no current
record of the run unit.