The following migration steps should be considered and performed:
To migrate to Adabas Review 4.6 from prior versions, consider and perform the
following migration steps.
If you are migrating from Adabas Review 4.4, run the EXPAND3 job found in the Adabas Review source library to upgrade your version 4.4 (or 4.3 ) repository to a version 4.5 SP1 repository.
If you are migrating from Adabas Review 4.5 SP1, run the EXPAND4 job found in the Adabas Review source library to upgrade your version 4.5 SP1 repository to a version 4.5 SP2 repository.
If you are migrating from Adabas Review 4.5 SP2, run the EXPAND5 job found in the Adabas Review source library to upgrade your version 4.5 SP2 repository to a version 4.6 SP1 repository.
Note:
For example, if you wanted to migrate from Adabas Review 4.4 to Adabas Review 4.6,
you would need to run the three jobs EXPAND3, EXPAND4, and EXPAND5
consecutively.
If your site uses user field definitions, you will probably need to modify them to support architectural changes made to the internal command log record (LORECR). Contact your Software AG support representative for assistance.
If an existing Adabas Review repository file is used with a new Natural FNAT file, the function REGEN ALL needs to be executed. For more information about REGEN ALL, read Regenerating All Display Programs.
Any history file data from Adabas Review releases prior to Adabas Review 4.5 that includes the field CMDRESP must be converted for Adabas Review 4.5 before you run any new reports. In version 4.5, the CMDRESP data was changed to be stored in milliseconds rather than seconds. Software AG provides a conversion routine for you to use that can be run online or in batch. If you need to continue using the old units and the old calculation algorithm for history data, contact your Software AG support representative.
To convert the history data, you must either run the online CONVERT HISTORY command or run a batch job that performs the CONVHIST function. Each is described here.
 |
Warning: This conversion should only be run once against your existing history data; if it is run more than once, you run the risk of altering your older history data more than necessary, rendering it unusable. In addition, the conversion should be performed prior to running any new Adabas Review reports; if you run it after you have run new reports, you run the risk of altering the data in your new reports unnecessarily. |
The conversion routine will update every record in the history file where the CMDRESP value is stored. The time it takes for this program to run depends on the number of records for reports that contain the CMDRESP field. .
On the Adabas Review Natural command line, enter CONVERT HISTORY.
A conversion dialog starts up.
Follow the prompts in the conversion dialog. One prompt requests the number of records that should be converted before an ET is performed (a default of 25 is provided).
When all prompts have been answered, the history records are converted and the final conversion dialog appears, showing its progress.
Create a batch job that runs the CONVHIST command. The syntax of the CONVHIST batch command is:
CONVHIST [nnn | 25]
where nnn is the number of history records that should be converted before an ET is performed (and 25 is the default). The sample batch job might include the following statements:
LOGON SYSREVDB MENU DBID = review-dbid CONVHIST FIN
For complete information on running Adabas Review batch Natural jobs, read Using Adabas Review in Batch Natural . At this time, no sample conversion job is supplied with Adabas Review.
