Glossary entries exist beginning with the following letters:
The Adabas load modules comprising the Delta Save Facility.
A load module of Delta Save Facility that is loaded to the Adabas nucleus and contains the program logic for recording changed RABNs in the DLOG area.
A load module of Delta Save Facility that is loaded for ADARES executions and contains the program logic for building the DSIM data set.
A load module of Delta Save Facility that is loaded for ADASAV executions and contains the program logic for the input parts of SAVE DELTA, MERGE, and RESTORE DELTA processing.
The teleprocessing-monitor-dependent interface module that connects the application/user to Adabas. The actual module name depends on the TP monitor being used; for example, the module name for linking to a batch or TSO program is ADALNK, and for CICS, the module name is ADALNC. The term "Adalink" refers to the module appropriate for the given environment. The terms "Adalink(s) and "ADALNKS" are synonyms.
Adabas stores each database record in a Data Storage block, identified by a relative Adabas block number (RABN). Each record's RABN is kept in a table called the address converter. The address converters, one for each database file, are stored in the Associator. Address converter entries are in ISN order (that is, the first entry tells the RABN location of data for ISN 1, the 15th entry holds the RABN location of data for ISN 15, and so on).
The storage area assigned to a program task/work unit. In MVS, an address space is a region; in VSE, a partition; and in BS2000, a task. In this documentation, the term "region" is used as a synonym for "partition" and "task".
A consolidation of the continual sequence of individual delta save tapes produced since creation of the last full save tape. The full save tape and the consolidated delta save tape together represent the database status following the most recent save operation.
Controls and manages the database resources. Tasks include defining database distribution, assigning a structure and resources, creating and maintaining programming and operation standards, ensuring high performance, resolving user problems, defining and teaching user training, controlling database access and security, and planning for growth and the integration of new database resource applications and system upgrades. Also known as the database analyst.
The ADASAV utility operation that saves only those blocks of the Adabas database that have been added or altered since the last full or delta save operation; also, the resulting save data set.
The optional Adabas feature that provides the ability to perform save operations that save only changed blocks of the database. Using the Delta Save Facility, you can make interim delta save tapes and then combine them into a final normal full database save tape.
ADADSF functional units that are called at certain times during operation to implement delta save functionality.
A DSID identifies each save data set produced by the Delta Save Facility.
The process of recording changed RABN lists to the delta save logging (DLOG) area.
The DLOG area is space allocated in the Adabas Associator to record the RABNs of changed Adabas blocks written to the database.
A DLOG area "detail entry" describes a changed block or range of blocks in the DLOG area.
A DLOG area "detail block" is a type of block that contains detail entries.
The current status of the Delta Save Facility. The possible status conditions are
|not installed||DLOG area has not been defined, although the nucleus may be running with DSF=YES|
|disabled||DLOG area has been defined but no delta save logging occurs, and no delta save operations are possible|
|enabled||DLOG area is defined and delta save logging is being performed; delta save operations are possible.|
An interim direct access data set holding the images of all database blocks changed during an online save operation. These blocks are held for subsequent consolidation with the associated online save data set. The DSIM data set is a companion to the related online save output tape.
A table of DSIM data set contents which, after consolidation, is used to retrieve the database blocks stored in the data set in ascending RABN sequence.
A logical file comprising physical files in one or more locations. The physical files have the same field definition table (FDT), but non-overlapping ISN ranges. The data content of at least one field (the field value criterion) determines the physical file in which a data record is located.
A table that defines each file's record structure and content. There is one FDT for each database file. FDTs, stored in the Associator's fixed area, have three parts: the first is a list of the file's fields in physical record order, the second part is a "quick index" to the records in the first part, and the third part defines the files sub/superfields and sub-/super-/hyper- and phonetic descriptors.
An ADASAV utility save operation that saves the complete current database; also, the resulting save data set.
Every Adabas record is assigned an internal sequence number (ISN) to identify the record. Each record keeps its original ISN, regardless of where it is located.
Records in a physical database file have four-byte ISNs ranging from MINISN to MAXISN. In replicated files, a record has the same ISN in all file copies. In partitioned files, the ISN ranges are non-overlapping for each physical file.
The result of combining multiple consecutive delta save tapes into a single consolidated delta save tape.
A save tape constructed by the Delta Save merging function, containing the complete database.
A physical file contains database records. Each physical file is identified by a file number. The number of physical files (and physical file numbers) per physical database is limited to 5000 or one less than the ASSOR1 block size, whichever is lower.
The portion of the calling program's parameter area, called the user buffer, that contains the data transferred during Adabas read, search, and update operations. When reading data field definitions, Adabas also returns the field definition information in the record buffer.
The creation of an interim DSIM data set from sequential protection log (PLOG) data sets. This mode is used when normal DSIM data set creation fails.
Adabas divides Data, Associator, and Work disk space into device-dependent logical blocks. The blocks in each of the three areas are numbered consecutively in ascending sequence beginning with RABN 1. The data blocks themselves as well as their addresses are referred to throughout Software AG publications as "RABNs". In other words, the sentence, "Adabas assigns RABNs 1-10 to the Associator" means ten Adabas storage blocks numbered 1-10 are assigned-not just the block numbers, whereas "Adabas assigns 50 RABNs to the Associator" means 50 blocks of storage with unspecified RABN numbers is assigned.
A processor of Adabas calls and issuer of replies. An Adabas nucleus is an example of a service (see also target).
A receiver of Adabas calls. A target maintains a command queue, and communicates with routers using ADAMPM. A target is also classified as a service. The Adabas nucleus is a target.
A batch or online application program that generates Adabas calls and uses an Adalink for communication.