ADACVT (Convert a Database from a previous Version)

#### Search Results

Search

# ADACVT (Convert a Database from a previous Version)

This document describes the utility "ADACVT".

The following topics are covered:

- Functional Overview

- Procedure Flow

- Checkpoints

- ADACVT Control Parameters

- Restart Considerations

## Functional Overview

The utility ADACVT converts an existing database in place. The conversions performed are described below.

ADACVT enables the conversion of a database in both directions:

- From a previous version to the current version and;

- From the current version to a previous version.

When converting a database

- The nucleus must not be active or;

- The nucleus must not have an AUTORESTART pending;

- The nucleus must not have utility entries in the utility control block (UCB).

Prior to converting a database, it is highly recommended that you:

- Use ADABCK to dump the database;

- Use ADAVFY'S FIELD and INDEX functions to verify the consistency of the database.

  Note
  The verification of the database can be done either before or after dumping the database.

The new Adabas version works best if the database is registered in the ADABAS.INI file. If the database is not registered, but a corresponding DBxxx.INI file is available, then ADACVT adds the database into the ADABAS.INI file.

During the conversion, the new structure level and the AUTOSTART option are adapted in ADABAS.INI.

Notes:

1. In general, a downward conversion is not possible if features introduced with a previous Adabas version are not supported by the target version. Any modifications made using features not supported in the target version must be removed before you attempt the downward conversion. For example, if the spanned record feature is used, ADACVT will not perform a downward conversion of a database to Version 6.6 or below. Similarly, ADACVT will not convert an encrypted database to a version that did not support encryption.
2. If the RBAC system file is loaded, ADACVT will not perform a downward conversion to Version 6.5 or below. ADACVT will replace the RBAC system file with a loss of user-defined data when converting to the current version.
3. If you perform a downward conversion of a database that contains collating descriptors created with ICU version 5.4, you must execute ADAINV REINVERT with ADAINV of the target version for these collation descriptors, following successful execution of ADACVT.
4. If the Azure Key Management System is used, ADACVT will not perform a downward conversion to versions prior to 7.2.

This utility is a single-function utility. For more information about single- and multi-function utilities, Adabas Basics, Using Utilities.

## Procedure Flow

Data Set | Environment Variable/ Logical Name | Storage Medium | Additional Information
--- | --- | --- | ---
Associator | ASSOx | Disk |
Data storage | DATAx | Disk |
Sort storage | SORTx TEMPLOCx | Disk | Administration Manual, temporary working space
Control statements | stdin |  |
ADAINV messages | stdout |  | Messages and Codes
Temporary storage | TEMPx | Disk |

## Checkpoints

On successful completion, ADACVT writes a SYNP checkpoint.

## ADACVT Control Parameters

The following control parameters are available:

         M    DBID = number

         M    CONVERT = {target version}

### DBID

    DBID = number

This parameter selects the database to be converted.

### CONVERT

    CONVERT = {target version}

This parameter specifies the structure of the destination version. It can take values of the format V<major version number><minor version number>0. For example:

> V670

>   Converts a database from version nn0 to Version 6.7.

or

> Vnn0

>   Converts a database to version nn0.

Note
In the above description nn is the current version of Adabas; the 1st digit denotes the major version, the 2nd digit the minor version.

#### Example:

    ADACVT DBID=number CONVERT=V700

An attempt is made to convert the database with the DBID = number to Version 7.0.

## Restart Considerations

If ADACVT is unable to restart after a crash, restore the original database from the backup and run the utility again.

### On this page

- Functional Overview
- Procedure Flow
- Checkpoints
- ADACVT Control Parameters
- Restart Considerations