This section provides an overview of new features and new terminology for Adabas Vista version 7.4.
A partitioned or a translation file is defined to Adabas Vista by identifying it by its source database and file number - that is, the database and file number by which the application refers to the file. In Natural terms, this is the database and file number defined in the DDM.
In Adabas Vista version 7.1 and 7.3 - for File Translation only - there was an optional additional attribute that would enable the same source database and file number to be defined multiple times. This allowed clients, processing within the same application against the same source database and file number, to be redirected to different target files. This optional attribute was termed the Environment ID.
With Adabas Vista version 7.4, this concept has been revised and extended for partitioned files. The attribute is now referred to as the Profile ID and not as in earlier versions the Environment ID. Profile IDs can be used, for example, to identify clients that belong to the same geographic location, such as New York, London, or Tokyo.
During conversion to Adabas Vista version 7.4, existing translation rules will maintain the relationship between this and the source database ID and file number. Partition definitions will also be converted to exploit this feature. The combination of Profile ID, source database ID and source file number is known as a source profile.A target category will also be required for each source profile.
The default Profile ID, which will be added to partition definitions during conversion, is left blank. Any applications that previously specified an Environment ID to differentiate between sets of translation rules may now be constrained to a subset of partition definitions, that is, those with the same Profile ID.
Profile is now defined as a unique combination of Profile ID, source database, and file number.
In Adabas Vista version 7.1 and 7.3, a single translation definition (what is now termed a profile) could only have a one-to-one relationship with a defined target database and file number.
With Adabas Vista version 7.4, a single profile may have a one-to-many relationship with a number of defined target database and file numbers using the concept of target category.
A target category identifies the target details that are to be used in the processing of commands issued against a particular profile.
For a translation profile, the target details consist of the target database and file number.
For a partitioned profile, the target details consist of the partition database and file number(s).
A set of target categories could be, for example, the environments through which an application must be migrated before it can go into production, such as Development, Quality Assurance, User Acceptance, and Production. Each target category identifies the target details appropriate to that particular environment.
Note:
The Adabas Vista conversion program (AVIMIG74) will convert all
existing translation rules and partition definitions to a default target
category, which will also be created automatically.
A new option is provided with the Adabas Vista Online Services Maintenance function. The Maintenance screen can be used to define and maintain target categories. One target category must be designated as the default.
The PF10 (Add), (D)isplay and (M)odify options relate to the target category itself.
The (C)opy option can be used to copy just the target category definition, or any source profiles already referring to the target category.
The other options relate to all source profiles which refer to this target category. For example, Publish a target category will upgrade all source profiles for this target category from draft status to published. There are various options that can be specified to allow or prevent overwriting of source profiles if a published version already exists.
At application logon time, the job parameters Profile ID and Target Category define the context in which the client runs. This context may be changed dynamically by means of various APIs that allow modification of Profile ID, Target Category or Context. The client's current Context may also be temporarily suspended and resumed as required by the application.
Job parameters now have a Profile ID and Target Category specified for each job and job type. The default for Profile ID is blank; the default for Target Category is identified on the Maintain Target Categories screen.
Job parameters have been extended with some special options:
Vista ON/OFF for this job
Enable Profile Overrides. Job Profile Overrides can be used to override the job's default Target Category for one or more profiles.
Profile Overrides / Selection by Profile ID - uses the Profile ID to select the appropriate overrides.
Each job parameter may now have associated profile overrides that affect the target category or categories for some source profiles. These may be defined and displayed by specifying the Overrides option against the required job, from the Maintain Job Parameters List screen.
A new override is created using PF10 and specifying a source profile and a target category. For example, a job may default to target category=TEST and switch the access to a test file, but for a specific source profile this may be overridden to target category=PROD and switch the access to a production file. This switching will only occur if the override is published. Draft overrides are ignored.
Each override may be maintained as for other Adabas Vista file definitions using the options Display, Modify, Purge, Copy, Withdraw and Publish.
An API to enable independent access to the configuration file is provided.
An API for use with 3GL programs is provided. See section Application Programming Interface for details of the APIs that are currently supported.
