Version 8.2.5
 —  Utilities  —

REVERT: Revert Database to Lower Version

The REVERT function starts from the Adabas version of the last nucleus session.

graphics/util_adacnv_revert.png

This document covers the following topics:


Essential Parameter and Subparameter

TOVERS: Target Version

The version of Adabas database (version and revision level) to achieve at the end of the ADACNV run. The TOVERS parameter value must be a version lower than the source version.

The version format is vr indicating the version and release level; for example, 81.

Top of page

Optional Parameter

IGNPPT: Ignore Parallel Participant Table PLOG Entries

When reverting from a version of Adabas that uses the parallel participant table (PPT) structure to a lower version of Adabas, an error is printed and conversion fails if the system detects one or more protection logs (PLOGs) from the current version that have not been copied/merged.

If IGNPPT is specified, the utility will continue processing in spite of the uncopied/unmerged PLOGs.

NOUSERABEND: Termination without Abend

When a parameter error or a functional error occurs while this utility function is running, the utility ordinarily prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump). If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.

Note:
When NOUSERABEND is specified, we recommend that it be specified as the first parameter of the utility function (before all other parameters). This is necessary to ensure that its parameter error processing occurs properly.

PLOGDEV: Multiple PLOG Device Type

PLOGDEV specifies the physical device type on which the multiple protection log data sets to be reverted is contained. If PLOGDEV is not specified, the device type specified by the ADARUN DEVICE parameter is used.

RESTART: Rerun after Point of No Return

If ADACNV terminates abnormally after the point-of-no-return, that is, after all changed blocks have been written to DD/FILEA, the RESTART parameter instructs ADACNV to begin its run by reading the contents of DD/FILEA and continue by writing them to the database.

TEST: Test Conversion

The TEST parameter tests the feasibility of the reversion operation without actually writing any changes to the database.

Top of page

Reversion Considerations

The following is a list of special reversion considerations for ADACNV.

All Versions
From Version 8 to Any Prior Version

If a database makes use of any of the following extended features of Adabas 8, ADACNV will not allow you to revert the database to a version prior to Adabas 8:

If you want to complete the backward conversion, you must first remove any file with these new features from the Adabas database.

The use of the following other new features provided in Adabas 8 do not prevent backward conversion to Adabas 7.4, but, of course, the new features cannot be used in Adabas 7.4:

From Version 7.1 to 6.2
From Version 6.2 to 6.1

Top of page

Example

The following example indicates that the database should be converted back (reverted) to a version 8.1 Adabas database.

ADACNV REVERT TOVERS=81

Top of page