It is possible to implement Client Versioning without implementing database versioning, but care must be taken to ensure that commands cannot be routed to a database that is not running the appropriate version.
In a re-entrant batch environment, Client Versioning is established by the first task to issue an Adabas call. If that task terminates prior to other tasks which also issue Adabas calls, results are unpredictable.
It is possible to implement Database Versioning without implementing Client Versioning. Commands issued to the database will be automatically routed to the appropriate version of the Add-on product’s database component.
Note:
Implementing Database Versioning will have an impact on the memory
allocation for the database. Memory region sizes may need to be reviewed and
increased as necessary.