This section provides an overview of the enhancements provided with Adabas Vista Version 8.1.
Adabas Vista Online Services (SYSAVI) has been enhanced to provide appropriate support for the new features provided with Version 8.1.
The default value for Error Reporting has been changed from Yes to No in order to avoid unnecessary writes to the job log and console.
The maximum number of Target Categories has been capped at 8. This enables easier online services navigation and maintenance of those translation rules defined to multiple target categories.
Previous settings for read-ahead processing control are no longer necessary. This is now automated internally.
Prior to Version 8.1 it has only been possible to modify a record’s partition criteria if it means the result does not cause the record to move partitions. With Adabas Vista Version 8.1 it is possible to allow a record to move from one partition to another. However, there are some special considerations. First, movement of such a record inevitably means the ISN will change, which is absolutely not a normal programming situation, requiring you to consider some application design issues. Second, in order to enable such a feature you need to activate a specific exit that defines how the record movement is to take place, for the named partitioned files – contact Software AG in order to proceed in this area. In addition, moving from one partition to another may require a distributed transaction which will only be safe if you use Adabas Transaction Manager.
Adabas Vista Version 8.1 now generates transaction directives
(END TRANSACTION, etc) in accordance with standard
distributed transactions making it compliant with the use of Adabas Transaction
Manager.
Software AG strongly recommends that the use of ETID is consistent (identical) across all databases used for a client session.
Translation and partitioning features mean that CID commands may be re-directed to other databases/files which can cause inadvertent clashing of CIDs inside Adabas databases. Consequently the CID handling in Adabas Vista has now been strengthened to avoid this happening.
