Version 8.2.5
 —  Messages and Codes  —

ADACNV Utility Error Messages

This document describes conversion errors that might occur.


Top of page

Conversion Errors (ERROR-121 - ERROR-146)

Overview of Messages

ERROR-121 | ERROR-122 | ERROR-123 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-132 | ERROR-133 | ERROR-134 | ERROR-135 | ERROR-136 | ERROR-137 | ERROR-138 | ERROR-139 | ERROR-140 | ERROR-141 | ERROR-142 | ERROR-144 | ERROR-145 | ERROR-146
ERROR-121 Version to-version not supported
Explanation

Version number specified with parameter "TOVERS" is not supported by ADACNV.

Action

Change the parameter to a supported version and rerun the utility.


ERROR-122 Conversion not permitted for version 5.1 and below
Explanation

The current version of the database is 5.1 or below. Conversion could only be performed from version 5.2 and above.

Action

Convert the database to version 5.2 by starting and stopping the version 5.2 Adabas nucleus, then rerun ADACNV.


ERROR-123 Conversion not possible because the DIB block is not empty
Explanation

The DIB block is not empty, conversion is not possible.

Action

Shut down the Adabas nucleus, wait for all utilities to complete, and rerun ADACNV.


ERROR-125 Conversion not possible because of pending autorestart
Explanation

The Work data set is not empty. Conversion is not possible.

Action

To remove the pending autorestart, restart the nucleus and end it normally.


ERROR-126 DDFILEA block size too small
Explanation

The DDFILEA block size ("block size" bytes) is too small to write a record with a length of "length" bytes.

Action

Assign DDFILEA to a device type with a larger sequential block size.


ERROR-127 Conversion to version vr not possible.
FDT for file fn does not fit into 4 ASSO blocks.
Explanation

You cannot convert to the version listed in the message (vr) because the file listed in the message (fn) does not fit into four Associator blocks.

Action

Delete the file listed in the message (fn) and rerun the ADACNV job.


ERROR-132 DDFILEA (FILEA) structure mismatch
Explanation

DDFILEA (FILEA) has an invalid structure. This is probably a job control (JCL) statement error.

Action

Correct any error and rerun the ADACNV job.


ERROR-133 File fn has version vr feature on, backward conversion impossible
Explanation

You cannot convert to the version you requested because at least one version vr feature was used for the file listed in the message (fn).

Action

Remove the version vr features and rerun the ADACNV job.


ERROR-134 Conversion not possible because protection log has not been copied
Explanation

The PLOGRn data set is not free. Conversion fails.

Action

Run ADARES PLCOPY to free the PLOG data set(s); then rerun the ADACNV job.


ERROR-135 Conversion not possible because alternate RABNS are assigned
Explanation

Alternate RABNs are not supported by Adabas version 7.2 and above.

Action

Use ADAORD to reorder the database before converting it from a version of Adabas version 7.1 or below to Adabas version 7.2 or above.


ERROR-136 Open PLOGRn error for NUCID= nucid, DSNAME= plog-name
Explanation

The parallel participant table (PPT) entry contains a protection log (PLOG) data set with the specified number and name. ADACNV was unable to open the data set. The data set may have been deleted, or it may not be cataloged, or it may contain PLOG data that has not yet been copied.

Action

Provide access to the specified data set or use the IGNPPT parameter and rerun the job.


ERROR-137 I/O error reading PLOGRn for NUCID= nucid , DSNAME= plog-name
Explanation

The parallel participant table (PPT) entry contains a protection log (PLOG) data set with the name and number specified. ADACNV was unable to read the first block of this data set. The data set has probably been destroyed.

Action

Determine the cause of the error; correct it and rerun the job.


ERROR-138 Conversion is not permitted for Event Replicator Servers.
Explanation

Backward conversion of an Event Replicator Server is not supported prior to Adabas version 7.4.

Action

Investigate the cause of the error.


ERROR-139 Conversion is not permitted when a {REPLICATOR | SLOG} file is loaded.
Explanation

Backward conversion of a database is not possible when a Replicator or SLOG system file is loaded.

Action

Investigate the cause of the error.


ERROR-140 ASSO RABN allocation failed
An attempt was made to allocate n ASSO blocks
Explanation

The allocation of the PPT area failed. An attempt was made to allocate n ASSO blocks.

Action

Correct the error and rerun the job.


ERROR-141 Conversion back to V74 not possible
Explanation

The database has more than five physical ASSO or DATA extents. It cannot be reverted back to an Adabas 7 database.

Action

Contact your Software AG technical support representative for assistance.


ERROR-142 Conversion back to V74 not possible
Explanation

One or more system file numbers is greater than 255.

Action

Adjust the system file numbers so they are less than 255 and try again.


ERROR-144 Conversion not required
Explanation

The Adabas version of the database is the same as the version requested in the ADACNV run.

Action

No action is required for this informational message.


ERROR-145 Conversion back to V74 not possible. More than 6 user system files exist.
Explanation

Adabas 7 allowed a maximum of six user system files (files loaded with the SYSFILE option). More than six user system files currently exist.

Action

Unload, delete, and reload the additional user system files without the SYSFILE option. Then rerun this utility.


ERROR-146 Conversion back to V74 not possible. Unknown system file nnnnn exists.
Explanation

The user system file identified in the message (nnnnn) exists in the reserved area of the GCB.

Action

Unload, delete, and reload the system file with the SYSFILE option to place the file number in the correct area of the GCB. Then rerun this utility.


Top of page

Other Conversion Messages

Overview of Messages

Conversion to version yy feasible | Point of no return reached | Conversion from version xx to version yy started | Conversion is completed | The mirror table (ASSO RABN 7) has been cleared | The BUB (ASSO RABN 2) has been cleared Alternate RABN definitions were found but no alternate RABNS were assigned | Security by value converted normally | Some FST entries are deleted
Conversion to version yy feasible
Explanation

In the first phase of conversion, this message is printed to indicate that the conversion of the database is possible.


Point of no return reached
Explanation

The ADACNV utility has begun its final pass. Any abend after this point requires a new run of the utility with the RESTART parameter.


Conversion from version xx to version yy started
Explanation

In the first phase of conversion, a conversion step has started.


Conversion is completed
Explanation

The conversion step has been successfully completed.


The mirror table (ASSO RABN 7) has been cleared
Explanation

Adabas Reflective Database is not supported by Adabas version 7 and above.


The BUB (ASSO RABN 2) has been cleared
Alternate RABN definitions were found but no alternate RABNS were assigned
Explanation

Alternate RABNs are not supported by Adabas version 7.2 and above.


Security by value converted normally
Explanation

Security-by-value conversion has been successfully completed.


Some FST entries are deleted
Explanation

At least one FST entry does not fit into one FST block due to the FST structure change. The entry or entries with the smallest RABN range(s) are deleted.

ADACNV finishes with a warning and response code 4 (ADARSP004).

Action

Run ADAORD REORDB after conversion.


Top of page