ADACVT (Convert a Database from a previous Version)

This document describes the utility "ADACVT".

The following topics are covered:

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. A downward conversion is not possible if features introduced with Adabas Version 6.7 were used. Any modifications made using the new features must be removed before you attempt the downward conversion.
  2. 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.
  3. If the spanned record flag is set in the FCB, ADACVT will not perform a downward conversion of a database from Version 6.7 or above to Version 6.6 or below.
  4. If the RBAC system file is loaded, ADACVT will not perform a downward conversion of a database from Version 6.6 or above to Version 6.5 or below, and it will replace the RBAC system file with a loss of user-defined data when converting to Version 6.7.

This utility is a single-function utility.

Procedure Flow

graphics/adacvt.png

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/
SYS$INPUT 		   
ADAINV messages stdout/
SYS$OUTPUT 		  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 = {V630|V640|V650|V660}

DBID

DBID = number

This parameter selects the database to be converted.

CONVERT

CONVERT =  {V610|V620|V630|V640|V650|V660|V670}

This parameter specifies the structure of the destination version and can take the following values:

V610

Converts a database from Version 6.7 to Version 6.1.

V620

Converts a database from Version 6.7 to Version 6.2.

V630

Converts a database from Version 6.7 to Version 6.3.

V640

Converts a database from Version 6.7 to Version 6.4.

V650

Converts a database from Version 6.7 to Version 6.5.

V660

Converts a database from Version 6.7 to Version 6.6.

V670

Converts a database from Version 6.1, Version 6.2, Version 6.3, Version 6.4, Version 6.5 or Version 6.6 to Version 6.7.

Example 1:

ADACVT DBID=number CONVERT=V670

The database with the DBID = number is converted from Version 6.1, 6.2 , 6.3, 6.4, 6.5 or 6.6 to Version 6.7.

Example 2:

ADACVT DBID=number CONVERT=V630

The database with the DBID = number is converted from Version 6.7 to Version 6.3.

Restart Considerations

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