Glossary entries exist beginning with the following letters:
A single physical database is one set of Associator and Data Storage data sets identified by a single database ID number (DBID).
Using Adabas Parallel Services, a single physical database is accessed simultaneously by up to 31 Adabas nuclei running under a single operating system image.
Extended Common Service Area (ECSA) is a virtual storage area above the 16MB line that can be accessed from all address spaces in the operating system image.
Adabas Parallel Services uses global areas in shared data spaces to ensure that current data is available to all nuclei.
The global areas (data spaces) are accessible by all nuclei in an Adabas Parallel Services cluster and are used to synchronize their processing and to share data.
Each Adabas Parallel Services cluster uses a global cache area to hold ASSO/DATA blocks that have been updated during the session. The cache area provides the cluster nuclei with up-to-date block images to ensure data integrity.
The size of the global cache area is determined by the ADARUN CLUCACHESIZE parameter setting of the first cluster nucleus to start.
Each Adabas Parallel Services cluster uses a global lock area to manage the setting, status, and release of various locks imposed during multiple update nucleus processing. The global lock manager synchronizes the nuclei, users, and transaction processing to ensure data integrity.
The size of the global lock area is determined by the ADARUN CLULOCKSIZE parameter setting of the first cluster nucleus to start.
The ADACOM task is the first component of an Adabas Parallel Services cluster to be started and the last component to be stopped. ADACOM sets up the Adabas Parallel Services environment on an operating system image. Parameters of the ADACOM control program define the characteristics of any number of Adabas Parallel Services clusters.
ADACOM must be active on the image before any Adabas Parallel Services nucleus can be started.
ADACOM creates and owns the global areas. After initialization, it is responsible for holding the global areas and performing operator commands.
Each Adabas Parallel Services nucleus has its own local buffer pool, the size of which is determined by the ADARUN parameter LBP.
An ADARUN parameter that identifies a particular Adabas nucleus as a cluster nucleus.
Adabas Parallel Services allows a maximum of 31 nuclei in one cluster. All nuclei in the cluster work on the same database. There is no predefined limit on the number of Adabas Parallel Services clusters that can be used.
The parallel participant table (PPT) is an area of 32 blocks in the database's Associator. It is used to track the Work, PLOG, and CLOG data sets/files used by the nuclei running in a cluster (as well as by a noncluster nucleus).
Each cluster nucleus reserves one PPT block for itself and records in this block the names of the Work, PLOG, and CLOG data sets/files that it uses, together with pertinent status indicators.
Individual cluster nuclei use the PPT information to access the Work data sets/files of the peer nuclei when performing recovery after a nucleus failure.
The ADARES utility uses the PPT information to access the PLOG or CLOG data sets/files of the cluster nuclei when performing the automated PLOG or CLOG merge, respectively.
Furthermore, cluster and noncluster nuclei use the PPT information to warn about changes in the Work or PLOG JCL, if the previously used Work or PLOG data sets/files still contain data.
As a component of the Adabas SVC/Router, SVCCLU routes commands to the cluster nuclei. It uses the nucleus and user tables in common storage, which are updated based on nucleus or ADACOM information, to decide to which nucleus to assign a new user and route the user's commands.
There is no predefined limit on the number of Adabas clusters, each servicing a separate database, that can run under a single SVC/Router.
A product version is identified by the first two digits of the versioning number. Software AG distinguishes between major and minor versions according to the amount of functionality or technology added to the product. All other digits indicate correction levels.
In the product documentation, the notation vrs, vr, or simply v is often used as a placeholder for the current product version, for example, in data set or module names.
| Placeholder | Meaning | Definition |
|---|---|---|
| v | version | Major Version
The first digit of the product version number indicates major architecture and functionality implementation or enhancement that adds value to the product. |
| r | release | Minor Version
The second digit of the version number indicates functionality addition or enhancement that adds value to the product. |
| s | system maintenance level | Correction Level
Correction levels contain error corrections only, without new functionality, including documentation of all modifications and repairs. In case it is necessary to include functional changes into a correction level, an exception handling process ensures that corresponding quality assurance activities are triggered. These functional changes are documented. The main target is to avoid impacts when you install such a correction level. The third number of an Adabas Parallel Services version denotes the system maintenance level. On certain platforms supported by Adabas, additional levels may exist, such as update package, patch level, service pack and hot fix. |
