The ADACNV utility converts (CONVERT) an Adabas database from version 5.2 or above to a higher version, and the reverse (REVERT).
 |
Warning: Before you convert a database, you must terminate all active nucleus or utility jobs normally. |
To ensure database integrity, ADACNV writes changed blocks first to intermediate storage; that is, to the sequential dataset DD/FILEA. After all changed blocks have been written out to DD/FILEA, a "point of no return" is reached and the changed blocks are written to the database. If ADACNV terminates abnormally after the "point of no return", the RESTART parameter can be used to begin the ADACNV run by reading the contents of DD/FILEA and writing them out to the database.
The TEST parameter is provided to check the feasibility of a conversion or reversion without writing any changes to the database. It is therefore not necessary to terminate all activity on the database before running ADACNV when you use the TEST parameter.
Internally, the utility converts or reverts one version at a time until the target version is attained. It is therefore important to ensure that all requirements for conversion or reversion between the current and target database levels have been met before you execute ADACNV without the TEST parameter.
Before a conversion or reversion begins, ADACNV checks the status of the database:
The DIB must be empty; that is, no Adabas nucleus or utility may be active or have been terminated abnormally. If RESTART is specified, the DIB must contain the entry of ADACNV, which includes a time stamp.
For conversion from version 5.2, the checkpoint block 8 must have enough free space to accommodate the expanded 24-byte header used for version 5.3 and above. For reversion to version 5.2, the checkpoint blocks 20-24 must be empty.
The Work dataset must not have a pending autorestart.
If this check is successful, ADACNV locks the database and creates a DIB entry.
For reversions, ADACNV checks whether any features are used that do not exist in the target version and returns a message if any are found.
The procedure for converting or reverting an Adabas database is as follows:
If the nucleus is active, use ADAEND to stop it.
Use ADARES PLCOPY/CLCOPY to copy all protection and command logs.
For your installation, this may be done automatically with user exit 2.
Wait until the logs have been copied.
Optionally, back up the database (full or delta).
Execute the ADACNV utility.
Start the nucleus of the version to which you have converted or reverted.
Important:
To ensure database integrity, DD/FILEA must be defined
permanently and be deleted only after ADACNV has completed successfully. The
DD/FILEA dataset must not be defined as a temporary dataset that is
automatically deleted at the end of the job.
