The Versioning Tool has the following components:
Client Versioning is used when, for example, different transactions in the same CICS job require the use of different versions of System Coordinator and its co-products.
The Client Versioning component enables Adabas commands to be routed to different Adabas link modules based on Job Name (for Batch) or Transaction ID (for CICS) with each Adabas link module using a different version of the supported Add-on products.
Database Versioning allows multiple clients, each running a single version of the Add-on products, to access the same database.
The Database Versioning component ensures client and daemon messages issued from multiple versions of the Add-on products are serviced correctly by the appropriate version of the Add-on product’s database component.
Multiple version support in the daemon is achieved by running a separate daemon for each required version. The daemon does not support multiple versions in a single daemon instance.
The implementation of Client and/or Database Versioning necessitates all version-related Add-on product modules to be suffixed with a particular identifier. Daemon Versioning allows you to use these same re-named product modules in the Adabas System Coordinator and Adabas SAF Security daemons.
This enables the use of a common versioning library, with common module suffixes, for Adabas databases and daemon tasks.