The following terms and abbreviations are used in the Entire Net-Work documentation with a meaning particular to Entire Net-Work. Terms not defined here are either general Software AG Adabas or Entire Net-Work terms or other data processing terms or abbreviations defined in the appropriate documentation.
An authority in a network that issues and manages keys for message encryption.
Each target maintains a queue of commands (or messages) into which the router places user requests. The target calls ADAMPM to build and maintain the queue.
Generic name for the Entire Net-Work task. It describes any process using intermachine communication allowing transparent access to remote targets.
A message created by an Entire Net-Work component and sent to another Entire Net-Work component, and typically performing a function within Entire Net-Work. Such messages normally are not seen outside Entire Net-Work.
A commonly addressable table containing information about all currently active targets on the node.
A variable value applied via an algorithm to a block of unencrypted text to produce an encrypted result. Keys are also used to decrypt encrypted text.
The access method-dependent part of Entire Net-Work. During initialization, each node dynamically loads one line driver for each access method that the node uses.
A communications connection between two adjacent Entire Net-Work nodes. The link performs the low-level protocols for the connected line drivers.
A sequence of characters, normally comprising control information and a body, that is transferred between two network entities. In Entire Net-Work, messages are classified as either control or payload (user request) messages and are sent from node to node.
A link that is coded with parameter values that serve as default values for many partners, eliminating the need to code one LINK statement for each partner. As each partner connects, new control blocks are allocated and initialized from the model link.
A real or virtual processor running a multitask operating system. Each node has a router and possibly one communicator.
The sequence of links and nodes between the originating and target node of a message. Multiple paths between originating and target nodes may exist, in which case, Entire Net-Work selects the shortest path to transmit a message.
An encrypted and secret key used in combination with a public key to encrypt and decrypt messages and digital signatures.
A value provided by some designated authority as an encryption key. Used in combination with a private key, the public and private keys can be used to encrypt and decrypt messages and digital signatures.
Any node through that a message passes on its way from the originating node to the target node.
Data returned in answer to a request from a user. Depending on the application protocol, a request may not result in a reply; however, the current Entire Net-Work protocol always provides a reply to a request, and allows requestors not identified as targets (that is, not independently addressable in the network) to receive data in the form of replies.
An amount of data presented to the router for transmission to a target. If necessary, transmission is performed through a communicator. In the current Entire Net-Work protocol, requests always result in replies. An Adabas command is an example of a request.
Each communicator maintains a queue into which the router places user requests to be transmitted to targets on other nodes. The communicator calls ADAMPM to build and maintain the queue. A communicator's request queue is equivalent to a database target's command queue.
The main routine responsible for interregion communication. The router is called by ADALNK and by targets via ADAMPM. One router handles all interregion requests on a single node, maintaining the ID Table of all active targets on that node. It closely interacts with the Entire Net-Work communicator to permit intermachine communication as a logical extension of interregion communication.
A target. Targets typically perform service functions for the callers, and are therefore also referred to as "services" or "service systems".
A message sequence between two tasks, typically a user and a target. The concept of a session is confined to the tasks themselves; Entire Net-Work processes requests as required, and does not use a session concept when handling data traffic.
A process that has identified itself to the router as being ready to accept requests. Each target maintains a command queue, and calls ADAMPM to communicate. An Adabas nucleus is an example of a target. In an Entire Net-Work environment, all targets are known to all communicators.
A program that sends requests to targets and processes the replies. An Adabas user program is a typical example. A user that is also a target can also receive requests; otherwise, a user receives only replies. A user communicates using ADALNK and the router, and can be any program including Adabas.
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 Entire Net-Work version denotes the system maintenance level. On certain platforms supported by Entire Net-Work, additional levels may exist, such as update package, patch level, service pack and hot fix. |
