Adabas Glossary - Software AG Documentation

More documents

Recommendations

Info

Glossary file In Adabas, a file is a group of related records that have the same format (with some exceptions; see Adabas Design in the Concepts and Facilities). The disk storage space allocated to a single Adabas database is segmented into logical Adabas files. A certain part of the overall space within the database is allocated to each logical file. When this space is filled with records from that file, Adabas automatically allocates more space to the file from the common free space pool. This dynamic space allocation, together with the dynamic recovery of released space, allows Adabas databases to run without intervention for long periods of time. A physical Adabas 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. An expanded file is 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 multiclient file is an Adabas file with records accessible through an owner ID. Only records identified by the same individual or group owner ID can be accessed or updated by the related user. This allows the file to be maintained as a single Adabas file, but to be used as multiple logical files (each record group belonging to an owner ID is a logical file). Super owner IDs allow access to all records in the file. file control blocks (FCBs) The control block Adabas assigns to each file in a database. There is one FCB per file. The FCB identifies the file's physical location and associated RABNs. The FCBs are part of the Associator. format ID The format ID is an ID that is assigned a decoded format buffer. The format buffer is stored once for each user and can then be referenced by its format ID and reused. Individual format IDs are stored once for each user and used only by that user. The format buffers are identified by a combination of unique format ID and terminal ID. 8 Contrast this with global format IDs which store a decoded format buffer once globally and share it with many users running on the same Adabas nucleus. Glossary
G general control blocks (GCBs) The format ID is specified in Adabas control block fields (ACBADD5 or ACBXADD5). For more information about format IDs, read Command, Format, and Global Format IDs, in the Adabas Command Reference Guide. The two control blocks Adabas assigns to each database. The GCBs identify the database and where it resides. The GCBs are part of the Associator. generation Information is stored on the Recovery log (RLOG) by generation, the logical unit used for recovery. A generation includes all activity between consecutive operations of: ■ ADASAV SAVE/RESTORE (database), ■ RESTORE GCB, or ■ SAVE DELTA/RESTORE DELTA (database). For more information, read Generation: The Unit of Recovery in Adabas Utilities Manual. global format ID A global format ID is an ID that is assigned a decoded format buffer. The format buffer is stored once globally and can then be referenced by its format ID and reused. Global format IDs are stored once globally and can be used by any user running on the same Adabas nucleus. The format buffers are identified by a unique format ID. Contrast this with format IDs which store a decoded format buffer once for each user and are used only by that user. The global format ID is specified in Adabas control block fields (ACBADD5 or ACBXADD5). For more information about format IDs, read Command, Format, and Global Format IDs, in the Adabas Command Reference Guide. global parameters Some ADARUN parameters are global parameters; that is, they must have the same values for all nuclei in a cluster. In addition, some of the global parameters are set at session initialization and cannot be changed. global transaction A global transaction is a unit of work that involves changes to resources under the control of more than one database operating in one or more operating system images. Glossary Glossary 9
Page 1 and 2: Adabas Glossary Version 8.2.2 Octob
Page 3: Table of Contents Glossary ........
Page 6 and 7: Glossary Adabas direct access metho
Page 8 and 9: Glossary base file When dealing wit
Page 10 and 11: Glossary user training, controlling
Page 14 and 15: Glossary I ID An abbreviation of ta
Page 16 and 17: Glossary logical transaction The sm
Page 18 and 19: Glossary P ■ change Adabas operat
Page 20 and 21: Glossary Software AG publications a
Page 22 and 23: Glossary Contrast this trigger type
Page 24 and 25: Glossary like the NI it manages, co
Page 27 and 28: Index (see database administrator (

Adabas Glossary - Software AG Documentation

Create successful ePaper yourself

Delete template?

Save as template?