Generally, Adabas utilities accept sequential input data sets that were produced as output data sets by utilities of the same version. Utilities of Adabas 8 also accept input data sets produced by utilities of versions prior to Adabas 8. However, utilities for versions prior to Adabas 8 cannot generally work with input data sets produced by Adabas 8 utilities.
This document covers the following topics:
A file can be imported (loaded, stored, or restored) into a database running with an earlier Adabas version as long as it does not use features that are supported only in a later Adabas version.
Generally, restoring a whole database is possible only with the same Adabas release used for creating the save data set. Restoring individual files is possible with the same or any later Adabas release used for creating the save data set.
Using the ADASAV utility of Adabas 8, you can restore files into an Adabas 8 database from a database save or file save data set created with the ADASAV utility from any prior Adabas version (for example, Adabas 7). Likewise, using the ADAREP or ADAULD utilities of Adabas 8, you can print a report or unload a file from a database save or file save data set created with the ADASAV utility from any prior Adabas version. However, you can only restore files from an Adabas 8 database save or file save data set into a database running with Adabas 7.4 if you have applied one of the following zaps to your Adabas 7 installation, as appropriate:
For Adabas 7.4.4 installations, apply zap AU744032.
For Adabas 7.4.3 installations, apply zap AU743099.
For Adabas 7.4.2 installations, apply zap AU742186.
You cannot use an ADAREP or ADAULD utility from an Adabas version prior to Adabas 8 to print a report or unload a file from a save data set created by the ADASAV utility of Adabas 8. If you are using Adabas Delta Save Facility, you cannot merge together delta save data sets created by different versions of the ADASAV utility. After the database has been converted to version 8, the next save operation must be a full save.
Using the ADALOD utility of Adabas 8, you can load a file from an unload data set created using the ADAULD or ADACMP utilities from any prior version of Adabas. However, you can only use the ADALOD or ADACMP utilities from Adabas 7 to load or decompress a file from an unload data set created by the Adabas 8 ADAULD or ADACMP utilities if you have applied one of the following zaps to your Adabas 7 installation, as appropriate:
For Adabas 7.4.4 installations, apply zap AU744033.
For Adabas 7.4.3 installations, apply zap AU743100.
For Adabas 7.4.2 installations, apply zap AU742187.
You can restructure databases and files from an Adabas version prior to Adabas 8 and store them in an Adabas 8 database using ADAORD STORE. However, you cannot store the restructured output of an Adabas 8 database or file in a database running with any prior Adabas version (for example, Adabas 7). If you attempt this, the following warning will be generated and ADAORD will end with a CC=4:
*** Warning: The input dataset is from V8 and will not be processed
Any sequential protection log (PLOG) used for a REGENERATE or BACKOUT function under Adabas 8 must have been created with Adabas 8. Using a sequential PLOG created with Adabas 8 for a REGENERATE or BACKOUT function under any prior Adabas 8 version is not supported.
You cannot run the ADASEL utility of Adabas 8 to select data from a sequential PLOG created by any Adabas version prior to Adabas 8. In addition, you cannot run the ADASEL utility of a prior Adabas version (for example, Adabas 7) to select data from a PLOG created by Adabas 8.
You also cannot run the ADARES COPY utility of Adabas 8 to copy data from a sequential PLOG created by any Adabas version prior to Adabas 8. In addition, you cannot run the ADARES COPY utility of a prior Adabas version (for example, Adabas 7) to copy data from a PLOG created by Adabas 8.
If the database had previously been expanded using the ADADBS INCREASE utility followed by an ADAFRM FROMRABN utility in a previous version, we recommend that you check the size of that database container.
Run an ADAREP utility report to determine the highest RABNs in the container.
Calculate the highest PAM page in the container using the RABN STD block size as shown in the device table for that device type in Device and File Considerations as follows:
Highest PAM Page = (Highest RABN) * (RABN STD Block Size)
Check this value with the highest physical PAM page output from the
following command: /SHOW-FILE-ATTRIBUTES
container-name,ALL . The value in the
HIGH-US-PA field contains the highest physical PAM page (this will have to be
done cumulatively for multiple containers).
If the highest PAM page is less than the highest PAM pages shown in the ADAREP output, accessing the highest RABNs will result in a DMS0922 I/O error.
