This document describes migration tasks you need to perform for this release of Adabas Review. It covers the following topics:
To migrate to Adabas Review 5.3 SP1 from prior versions, consider and perform the following migration steps.
Adabas Review under Natural
Verify that any Adabas Review display programs or objects you have written or modified have unique names that do not begin with RD*, RX*, SR*, SX*, CR*, CX*, CS*, PU-* or BUFFERPOOL (these prefixes are reserved for use by Adabas Review programs). This will ensure that this migration process does not overwrite them.
INPL the Adabas Review programs and DDMs from the INPL data set distributed with this release into the SYSREVDB library as described in Install Adabas Review under Natural, in your Adabas Review installation instructions.
If an existing Adabas Review repository file is used, sample report Scheduling File Usage will be added to the repository and display program SR-00041 or SX-00041 will be generated (depending on the DISPLAY mode). This happens when SYSREVDB will be started for the first time.
If the Adabas Review Natural programs will be INPLed into an existing SYSREVDB library, the GDA timestamp will change with a new version. Thus, to be able to run the existing display programs, the function RECAT ALL needs to be executed. This function will be automatically triggered at the start of SYSREVDB, when user exit P-UEXIT1 will be re-cataloged because of a GDA timestamp conflict. For more information about RECAT ALL, read Recataloging All Display Programs.
Note
Your user exits and RVCALL* program modifications will be kept and
re-cataloged.
Adabas Review Repository
If new fields are added to the Adabas Review Repository, you must run an EXPAND job to migrate an existing repository from a previous version to the current version.
If you are migrating from Adabas Review 5.2 SP1 or Adabas Review 5.2 SP2 to Adabas Review 5.3 SP1, no EXPAND job is needed because the repository did not change.
