Version 7.4.4
 —  Messages and Codes  —

ADACNV Error Messages

The following message groups are described:


Top of page

Conversion Errors (ERROR-121 - ERROR-140)

Overview of Messages

ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-128 | ERROR-129 | ERROR-130 | ERROR-131 | ERROR-132 | ERROR-133 | ERROR-134 | ERROR-135 | ERROR-136 | ERROR-137 | ERROR-138 | ERROR-139 | ERROR-140
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-124 CONVERSION NOT POSSIBLE BECAUSE THE CHECKPOINT BLOCK EXTENSION IS NOT EMPTY
Explanation:

The CP block extension (RABN 20-24) is not empty. Conversion to version 5.2 is not possible.

Action:

To clear the CP block extension, restart the nucleus; then end the nucleus normally.


ERROR-125 CONVERSION NOT POSSIBLE BECAUSE OF PENDING AUTORESTART
Explanation:

The Work dataset 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 ("blocksize" 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 SECURITY FILE BLOCK TOO LARGE
Explanation:

Security-by-value conversion expands the data records, which then do not fit into the data block.

Action:

Run ADAORD REORDATA on the security file with a larger padding factor; then rerun the ADACNV job.


ERROR-128 VERSION 6 FEATURE IS USED, BACKWARD CONVERSION IMPOSSIBLE
Explanation:

One of the following version 6 features was used:

  • 4-byte RABN

  • DBID greater than 255

  • maximum number of files in the database more then 255

Conversion to version 5 is not possible.

Action:

Remove version 6 features and rerun the ADACNV job.


ERROR-129 FILE file-number HAS VERSION 6 FEATURE ON, BACKWARD CONVERSION IMPOSSIBLE
Explanation:

Version 6 feature 4-byte ISN was used. Conversion to version 5 is not possible.

Action:

Remove version 6 features and rerun the ADACNV job.


ERROR-130 DLOG AREA IS NOT EMPTY. ADADSF HAS BEEN USED, CONVERSION TO VERSION 5.2 NOT POSSIBLE
Explanation:

The Adabas Delta Save Facility was used. ADADSF cannot run under version 5.2.

Action:

Switch ADADSF off and rerun the ADACNV job.


ERROR-131 FILE file-number HAS VERSION 5.3 FEATURE ON, BACKWARD CONVERSION IMPOSSIBLE
Explanation:

Version 5.3 feature was used. Conversion to version 5.2 is not possible.

Action:

Remove version 5.3 features 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 file-number HAS VERSION 7.1 FEATURE ON, BACKWARD CONVERSION IMPOSSIBLE
Explanation:

Version 7.1 feature was used. Conversion to version 6 is not possible.

Action:

Remove version 7.1 features and rerun the ADACNV job.


ERROR-134 CONVERSION NOT POSSIBLE BECAUSE PROTECTION LOG HAS NOT BEEN COPIED
Explanation:

The PLOGRn dataset is not free. Conversion fails.

Action:

Run ADARES PLCOPY to free the PLOG dataset(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 PLOGR n ERROR FOR NUCID= nucid, DSNAME= plog-name
Explanation:

The parallel participant table (PPT) entry contains a protection log (PLOG) dataset with the specified number and name. ADACNV was unable to open the dataset. The dataset 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 dataset 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) dataset with the name and number specified. ADACNV was unable to read the first block of this dataset. The dataset 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 databases.
Explanation:

Backward conversion of an Event Replicator database 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 PPT-AREA ALLOCATION FAILED
Explanation:

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

Action:

Correct the error and rerun the job.


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 | COX01I | COX02I | COX03I
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.

Action:

Run ADAORD REORDB after conversion.


COX01I ADACOX EXIT Vv.r.1 date ACTIVE
Explanation:

Informational message showing the version and assembly date of the ADACOX module.


COX02I ADACOX CONVERTING source TO target
Explanation:

Informational message indicating that conversions from source to target will be done by ADACOX.


COX03I ADACOX source TO target COUNT number AVG time (usec)
Explanation:

Informational message at session termination. This message is output only if ADACOX has performed conversions between source and target encodings. number shows the number of conversions and time the average time for conversion in microseconds.


Top of page