Utilities Error Messages

The 1-N element requires a valid C element. The C element defines the number of values to be processed by the 1-N element. Note that the C element must precede the 1-N element in the same line.

Define a C element before the 1-N element in the same line.

Too many parameters entered for the specified function.

Correct the input line.

Adabas - Adabas replication is only possible if it is permitted by your Adabas license file.

Upgrade your license.

Adabas-to-Adabas replication requires a replication exit (provided by the Adabas Event Replicator).

If you intend to use A2A replication, install the Adabas Event Replicator before starting the nucleus again; in particular, the replication exit is required.

If you have already used A2A replication but you no longer want to use it, perform ADADBM REMOVE_REPLICATION.

During the update of the replication meta data file an Adabas error occurred.

Check the nucleus log for the specific response code.

A certain database ID and file number combination was specified twice as replication target. Obviously this does not work. But a file can be replicated to two targets.

Choose a different target.

Either the file number of the target file or the target database is out of range (beyond 255) or the source file number does not exist. The target database and target file do not have to exist.

Choose valid target values. Make sure the source file exists.

An existing replication ID was used for ADAOPR ADD_REPLICATION.

Choose a different replication ID. If omitted, the next free ID is chosen.

Since the replication is triggered at the end of a transaction NOBT files cannot be replicated.

Option is the keyword specified for ADAOPR CHANGE_REPLICATION. Only certain options are allowed for a status to avoid inconsistences.

The valid keywords are documented.

Consult the table in ADAOPR CHANGE_REPLICATION.

Cascading actions for a referential constraint could cause modifications which would not be replicated if the replication of the primary file is not active.

Specify all connected files with ADAOPR CHANGE_REPLICATION.

Either the topic AUTHZ or the item ACTION could not be located in the configuration file adaauth.ini.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The value of item ACTION in the configuration file adaauth.ini is not valid.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

Address converter is inconsistent with DS.

Unload/export the file in physical sequence and load/import it again.

The file's Address Converter is too fragmented.

Unload/export the file, allocate larger extents, and load/import the file again.

The item AUDIT_FILE is invalid or missing in file adaauth.ini.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The value of the item AUDIT_FILE in the configuration file adaauth.ini is invalid.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The file assigned via the item AUDIT_FILE in the configuration file adaauth.ini could not be located.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

An error has occurred while accessing the file assigned via the item AUDIT_FILE. The file was not accessible; a possible cause for this could be file access permissions.

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE.

The configuration file adaauth.ini could not be found in the given location.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

An error has occurred while accessing the configuration file adaauth.ini. The file was not accessible; a possible cause for this could be file access permissions.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The value of item FORMAT is either invalid or missing in the configuration file, which is assigned via the item AUDIT_FILE.

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Either the topic AUDIT or the item FORMAT could not be located in the configuration file, which is assigned via the item AUDIT_FILE.

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.

The value of the item RBAC_FILE in the configuration file adaauth.ini is either invalid or missing.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The value of the item RBAC_FILE in the configuration file adaauth.ini is not a valid file path.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

The file assigned via the item RBAC_FILE in the configuration file adaauth.ini could not be located.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

An error has occurred while accessing the file assigned via the item RBAC_FILE. The file was not accessible; a possible cause for this could be file access permissions.

Contact your system administrator.

Check the content of and correct the file assigned via the item RBAC_FILE in file adaaudit.ini.

A syntax error has been encountered during the processing the security definitions in the file, which is assigned via the item RBAC_FILE .

Contact your system administrator.

Check and correct the security definitions in the file assigned via the item RBAC_FILE in file adaaudit.ini.

An internal error has occurred.

Contact your nearest support center.

The RBAC system file already exists in the database with the given file number. The database was not modified.

None.

The RBAC system file has been successfully loaded with the given file number.

None.

The file assigned via the item LOG_FILE could not be closed.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Check the content of and correct the file LOG_FILE.

The value of item LOG_FILE is either invalid or missing in the configuration file, which is assigned via the item AUDIT_FILE.

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.

The file assigned via the item LOG_FILE could not be located.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.

The file assigned via the item LOG_FILE could not be opened. The file was not accessible; a possible cause for this could be file access permissions.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Contact your system administrator.

Check the value of LOG_FILE.

The permissions of the directory in which the LOG_FILE is located are insufficient.

All users which are able to execute Adabas utilities require read and write permissions to the Audit Log file, which is located in this directory.

Contact your system administrator.

Check the content of and correct the file LOG_FILE.

The file assigned via the item LOG_FILE could not be written. Possible causes for this could be:

• Insufficient amount of storage/disk space;

• Insufficient permissions to access the file.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Contact your system administrator.

Check the content of and correct the file LOG_FILE.

The value of the item MODE in the configuration file adaauth.ini is either invalid or missing.

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.

Address converter is inconsistent with DS.

Unload/export the file in physical sequence and load/import it again.

The user is not permitted to execute the requested operation on the specified object.

This can occur for one or more of the following reasons:

• The user is not defined;

• The user does not have the required access privileges.

Contact your system administrator.

Check the content of and correct the security definitions in the file assigned via the item RBAC_FILE in file adaaudit.ini.

The conversion to 3-byte address converter could not be done because there are already block numbers which cannot be stored in 3 bytes.

Investigate if the DATA container(s) with the higher RABNs can be removed.

There is no more ASSO space for building the new Address Converter. The message shows the total amount of space needed by the AC_CONVERT function.

Calculate free ASSO space in database and see how much missing. Then add a new ASSO container with sufficient space with ADADBM ADD_CONTAINER or check if you can use ADADBM DEALLOCATE. Alternatively, you can increase the ASSO container by using ADADBM with the EXTEND_CONTAINER parameter.

Physical problem with reading of address converter or FCB corrupted.

Unload/export the file in physical sequence and load/import it again.

Item SEPARATOR invalid or missing in ‘string’

Contact your system administrator.

Check the contents of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.

See nucleus response code 77.

See nucleus response code 77.

Refer to nucleus response codes, response nnn.

The shared memory required by Adabas cannot be created or attached due to resource problems.

Check the Linux kernel parameters that relate to the resources and increase them if necessary. Check the documentation of your operating system for

• shmget error ENOSPC or

• shmat error EMFILE

The shared memory region cannot be attached. The reason for this may be missing user rights, for example a terminal server user does not have the "create global objects" user right.

Assign the appropriate user rights to the user.

The ADAM key option and the CIPHER option of ADAFDU are incompatible.

Select either ADAM or CIPHER but not both.

The specified ADAM parameter does not fit to the ADAM key.

Check the format of the ADAM field name and see the documentation on how to use the ADAM parameter.

The ADAM key specified by the parameter ADAM_KEY was not present.

Check the FDT specification.

An ADAM key must not have one of these options.

Check the FDT specification.

The given ADAM parameter cannot be used the ADAM ISN option.

Correct ADAM_KEY or ADAM_PARAMETER.

An ADAM key is not permitted for multiple-value fields or for fields within periodic groups.

Check the FDT specification.

An ADAM key must not be a special descriptor.

Check the ADAM_KEY parameter of ADAFDU.

An ADAM key does not have the unique option in the FDT.

Check the FDT specification.

An error occurred in the replication exit provided, for example, by the Adabas Event Replicator. ‘error’ describes the error that occurred.

Refer to the documentation of the product that provided the replication exit.

A fatal error occurred in the replication exit provided, for example, by the Adabas Event Replicator. ‘error’ describes the error that occurred.

Refer to the documentation of the product that provided the replication exit.

The APU definition gives the number of receivers. The total number is calculated as the number of APUs multiplied with the number of receivers. The number of defined tcpreceivers was less than the calculated number of receivers and changed to the number of calculated receivers. For an active APU definition, the number of tcpreceiver should be a multiple of the number of APUs.

To avoid this message, set the value of the TCPRECEIVER parameter accordingly.

There was a problem reading and validating the Adabas license file. Running without license restricts the ADATCP resources.

Activate a valid Adabas license file.

Each receiver of ADATCP has its own attached memory. The available free memory was too small for the Adabas call.

Increase the value of the nucleus parameter TCPATB.

There was a problem reading and validating the Adabas license file. Running without license restricts the ADATCP resources.

Activate a valid Adabas license file.

Each receiver thread has reached he maximum number of connections, and new connections are therefore not accepted. The number of connections was either defined by the nucleus parameter TCPCONNECTIONS or restricted by a missing license.

Increase the number of connections per thread, or install the appropriate license.

The initialization of ADATCP failed during database startup. It can be that the listen thread or a receiver thread could not be started. A detailed reason (error message) is given in the message.

Check the error message for the reason of the failure. A reason can be, for example, that the listen port is already in use by another application.

An Entire Net-Work license is needed to enable remote TCP/IP access. There was a problem reading and validating the license file. A detailed error message is provided.

Check the detailed error message and, for example, activate a valid Entire Net-Work (WCP) license file.

The database is active and defined in the dbmapping file of the Adabas Client, but is not reachable via TCP/IP. There is a configuration mismatch, either the database is not ADATCP-enabled, or the dbmapping file entry is not correct, e.g. a different port number in the mapping file and in the nucleus parameters.

Check the configuration for correctness and make sure the database is online. If the database still cannot be reached, remove the database entry from the mapping file; then the IPC mechanism will be used.

There was a problem reading and validating the Adabas license file. Running without a license restricts the ADATCP resources.

Activate a valid Adabas license file.

The initialization of ADATCP SSL failed during database startup. A detailed reason is provided in the the error message.

Check the error message for the reason for the failure. This can be, for example, that the SSL listeing port is already in use by another application, or that something went wrong while validating the certificates.

Informational messages issued during startup of the SSL subsystem.

None.

A system call used to configure the asynchronous I/O driver failed.

Check that the driver is correctly installed (use errno number as help).

A field without the NC or NU option can only be added as a descriptor (with the DE option) if the file is empty.

Add the field without the DE option and invert the field with ADAINV afterwards.

The open system call on the asynchronous I/O driver failed.

Check that the driver is correctly installed (use errno number as help).

An error occurred while performing an asynchronous I/O. A following ERRNOM message gives you more details about the error. Note that the reason for an errno(5): I/O error may not only be a real I/O error, but also one of the following:

• Not all required operating system patches are applied (see Installation).

• The system parameters, in particular AIO_LISTIO_MAX are not set correctly (see Installation).

Instead of increasing AIO_LISTIO_MAX, you can also set the ADANUC parameter BFIO_PARALLEL_LIMIT (see Utilities).

Verify that the required operating system patches are applied, and that the system parameters are correct. If these points are OK, check your hardware.

An error occurred when reading from the asynchronous I/O driver.

Check that the driver is correctly installed. If it is correctly installed. call your nearest support center (tell them the errno number as a help).

An error occurred when writing the asynchronous I/O driver.

Check that the driver is correctly installed. If it is correctly installed. call your nearest support center (tell them both numbers as a help).

A TEMP or SORT container file is already being used by another user.

Create another TEMP or SORT, or wait until the other user terminates.

Asynchronous IO error.

Send the output to your nearest support center.

The amount of space preallocated for a container file is different from the size specified with ADAFRM or ADADBM.

Correct the preallocation, or correct the SIZE parameter for ADAFRM or ADADBM.

A problem occurred during space allocation in a disk section (e.g. space bottleneck).

Check second message for a detailed analysis of the problem.

An overflow on a raw disk section occurred. Please note, that his error may occur, even though there is still enough free space on the disk section. The reason for this is that the space reserved for the directory describing the contents of the disk section is limited, and the error occurs if there are too many entries in the disk section.

Move data from the disk section to the file system.

The specified file is already present in the database.

Check the file number.

There is not enough free ASSO space to increase the Address Converter of the file to store the user-defined ISN.

Increase the size of the ASSO container.

Only a wildcard is permitted.

Use an asterisk `*'.

The same parent field is already used within another phonetic descriptor.

Check the file number or the parent-field name.

The descriptor to be set as unique is already defined as unique.

Check the file number or the field name.

A nucleus is already active for this database.

Check if there is really an Adabas nucleus for this database. (Linux only: if not, use showipc -k <dbid> to remove the shared memory resources and restart the nucleus.)

The required file is already locked.

None.

The specified option is already set in the nucleus.

None.

The keyword's abbreviation is not unique.

Make the keyword unique.

During auto restart, some errors have occurred. Check preceding messages for detailed error information. The nucleus can operate normally on all files on which no errors have occurred.

Repair the errors. See also the messages ARIXER and ERRFIL.

The consistency check failed during an autorestart.

Make a copy of the WORK container file and send the copy to your nearest support center.

During auto restart, an error in the index of this file occurred. The index for this file is destroyed and must be rebuilt using ADAINV REINVERT.

Rebuild the index using ADAINV REINVERT.

If an auto restart is required after a nucleus crash, the nucleus may require the same resources as the previous session, in particular the number of users (NU) and the size of the buffer pool (LBP) should not be decreased. In order to avoid that the auto restart fails, the nucleus checks that these parameters are not decreased before starting the auto restart.

Increase the parameter values accordingly for the next nucleus start.

The last session was not terminated properly, but the WORK used in the current session does not contain the information needed for auto restart. The database may be in an inconsistent state.

Restore/regenerate the database using ADABCK and ADAREC.

The size specified for the Associator is too small to contain the FCB and FDT blocks.

Use a larger ASSO size.

An asynchronous IO failed. The utility is aborted.

Check for problems with the device. Is the device online and writeable? If a logical volume spans several physical devices, are they all accessible? Try to access the affected devices using operating system commands. Have a look at system log files for appropriate error messages.

Access to a sequential file failed because of a structure mismatch. The file is not a sequential Adabas file, or it is a sequential file of an unexpected type, or it was generated on a wrong platform (most sequential Adabas files generated on a high-order-byte first platform cannot be processed on a low-order-byte first platform and vice versa).

Check the assignment of the associated environment variable.

An ADABCK DUMP function is active and blocking the nucleus. The nucleus must wait until ADABCK has completed.

Wait for the DUMP function to complete.

There is only one ADABCK DUMP function permitted if the nucleus is online or going to be online, but there is more than 1 DUMP function currently active.

Wait until all ADABCK DUMP functions have completed (or only one backup still active).

The nucleus has disabled a ADABCK DUMP function because it did not respond within 10 minutes. The backup got back control later and found this situation, so it aborted.

Check your adabck process.

A restore operation from a backup that was created without the option PARALLEL=MULTI_PROCESS cannot be performed using the PARALELL=MULTI_PROCESS option.

Perform the restore operation without the PARALELL=MULTI_PROCESS option.

A backup that was created with the option PARALLEL=MULTI_PROCESS cannot be restored to a platform with a different endian mode.

Create a backup without the option PARALELL=MULTI_PROCESS if data is to be restored on a platform with a different endian mode.

ADABCK can restore a database from a backup file that was created on a different platform: all data that are dependent on the endian mode are converted into the target format (swapped). However, it is not possible to convert the data structures that were used by earlier releases at the same time.

Use a more recent backup.

An ADABCK DUMP function is active while the nucleus is starting up. The processes must synchronize with each other.

If the nucleus cannot proceed then check the ADABCK process (via the ps command). If the ADABCK process does not respond within 10 minutes, the nucleus will disable the backup run and will start up.

An Adabas command was returned with an error (the response code is displayed as 'orig rsp'). This resulted in the command being backed out in order to reverse any changes. However, the backout did not succeed due to the error displayed as 'response'. The nucleus cannot continue, because its data are inconsistent.

Restart the database. This will result in consistent data.

The specified ending date/time is earlier than the specified beginning date/time or the current date/time.

Correct the beginning or ending value.

The specified tape device cannot be written by Adabas because the blocking factor is not supported.

Change the blocking factor on the tape device. It must either be variable or a multiple of 1024.

An invalid range of RABNs was detected in the FCB for the specified file.

The file in question cannot be used in this situation. To repair this, Unload/export the file, delete it, redefine it with ADAFDU, the load/import it again.

While restoring files, the requested range of RABNs of 'string' type is not available.

Use ADAREP's LAYOUT function to check the required blocks.

Another ADABCK DUMP function is active. Only one online backup is possible at one time.

Identify the running ADABCK process. Check the UCB with ADAOPR DIS=UCB and check with the ps command (ps -ef). Note that an ADABCK process can be active although there is no entry in the UCB.

The specified backup file does not contain any data.

Check the setting of the environment variable and the associated file.

During ADABCK a corrupted index block is found which will not be dumped to the backup file.

To verify that the block is not a relevant block, ADAVFY's INDEX function should be performed. If ADAVFY succeeds then the backup file is ok, the block in question will be reformatted if using the RESTORE function by ADABCK. If ADAVFY signals errors the index is corrupted. The given backup file cannot be used; the file must be repaired first with the REINVERT function of ADAINV.

The container sizes are insufficient or have different block sizes when restoring a complete database. The specified container file must have at least as many blocks as given in the message.

Check and compare the SUMMARY functions of ADAREP (database) and ADABCK (backup file).

The target database is restored or overlayed completely with the encryption settings provided by the control parameter ENCRYPTION, and should not already exist.

Choose a target database that does not already exist.

LOGGING=IO is switched on and an I/O from an unexpected container is going to be logged, so command logging has been deactivated.

Because this is an unexpected error, contact your nearest support center; you can re-enable command logging with ADAOPR's LOGGING function.

The backup copy file has a structure error with printed information. This backup copy file cannot be used as input for a restore.

Run ADABCK's DUMP function again.

This message provides additional information to the BKIREC message.

When restoring a database with multiple backup tapes, a tape was inserted in the incorrect sequence.

Insert the tapes in the correct sequence.

During ADABCK's RESTORE function, the NEW_DBID request cannot be satisfied and is ignored because of mismatches in the disk section.

Check the disk section of the current database and use ADADBM's NEW_DBID function.

The requested function can only be executed if a complete database is being restored.

Check the selected parameters.

The backup copy is not complete, the previous dump has not finished successfully.

This backup copy cannot be used, try another one.

During an online backup the nucleus went down abnormally. This will be detected by ADABCK at the end of this session.

Perform autorestart for the Adabas nucleus and restart the backup.

It is not possible to restore a database while the Adabas nucleus is active.

Shut down the nucleus and start the restore again.

A parallel backup failed due to an error of an associated subprocess. The error number is the exit status of this process.

Look at the subsequent error message that is displayed together with this one.

The synchronisation between ADANUC and ADABCK during an online backup was lost due to the 'reason'.

Restart the online backup with ADABCK. If it fails again, contact your nearest support centre.

The nucleus is within its startup phase and has not yet finished. ADAOPR will wait for10 seconds, ADAORD for 180 seconds, to finish the nucleus startup.

One or more container files are located on a READONLY / WORM device which cannot be written to.

A block device path name was used where a raw device path name was required.

Use raw device path name.

A checkpoint name has been supplied but no corresponding block number.

Supply the block number where the checkpoint name is to be found.

The block size on the output file is too small.

Use an output device with a larger block size.

The block at the given offset 'number' of the sequential Adabas file identified by 'path' has an unexpected block size.

The file is corrupted. You cannot work with it. If you cannot determine the reason for the data set corruption, contact your nearest support center.

The WORK block size must be larger than the largest ASSO block size, and the first ASSO extent must have a block size of at least 2KB.

Change the block size of ASSO or WORK.

Within an ADABCK restore, the block sizes between the database and the backup file are incompatible.

Check the block sizes of the database and the backup file.

When a container is being created on a WORM disk, this warning message gives the amount of unused space (in units of blocks of the specified block size).

This is an informational message and just informs you about wasted disk space. You could repeat the function to make use of that space also.

The specified RABN was allocated to a file but not contained in the GCB.

Run ADAVFY to check the FCB.

The session has been explicitly aborted (ADAOPR ABORT).

None.

The database contains overlapping FCB extents.

Run ADAVFY to check the FCB.

An internal error has occurred.

Contact your nearest support center.

IMPORT encountered a record, which is smaller than the block size of the user-defined device.

Choose a device (with the DSRABN parameter) with a greater block size and rerun IMPORT.

A smaller block size than the original block size was specified for an ADAM file. The specification of the block size could also be given indirectly by specifying DSRABN.

Correct the input line and rerun ADAORD.

A smaller block size than the original block size was specified for an ADAM file.

Correct the input line and rerun ADAORD.

This is a warning message to indicate that when you use the RESTORE=* function of ADABCK, some files will disappear because there are more files contained in the current database than on the dump file.

An invalid response has been detected during a BT.

Restart the database. This will result in consistent data.

The ACB interface only supports records buffers less than 64 kilobytes.

Use the ACBX interface for the Adabas call, or decrease the record buffer size for the Adabas call.

The CSA dump file cannot be opened.

Check that the file name is correct and check the file's access privilege.

The given string is too long.

Enter a string that does not exceed the length given by the error message.

The given string is too short.

Enter a string that is not shorter than the length given by the error message.

A block number has been supplied but no corresponding checkpoint name.

Supply the checkpoint name to which the block number belongs.

The checkpoint file contains invalid data.

Contact your nearest support center.

An error has occurred while opening or writing the command log file. The command log feature is now disabled, the nucleus continues normally.

Check the environment of NUCCLG. You can reactivate the command logging later on with ADAOPR FEOF=CLOG.

The new command log file could not be opened with an ADAOPR FEOF or LOGGING function.

Look in the nucleus log file to find the detailed error message.

This message is issued in each run of ADACMP. If records are compressed, it is an informational message. It is issued as a warning message if zero records are compressed. This may be because the input file does not contain any records or because the structure of the records does not agree with the FDT.

Check the ADACMP input file CMPIN and the FDT.

The specified PLOG/WORK block is corrupted.

Verify the consistency of the database.

Connection error due to inactive database or incorrect address or portnumber.

Please check the remote DB status.

Connection error due to incorrect protocol.

Please check the protocol.

Connection error due to invalid argument.

Please check the connection argument.

Verify the consistency of the database.

If you apply a hotfix to a wrong Adabas version, unexpected errors can occur. In order to avoid such errors, Adabas checks whether a hotfix that is applied to an Adabas version really has this Adabas version as prerequisite. If this is not the case, this error message is returned.

Remove the hotfix from the wrong Adabas version, and apply it to the correct Adabas version.

An Adabas file has allocated RABNs that are located in the last container file (REMOVE_CONTAINER function) or in that part of the last container file that is to be deallocated (REDUCE_CONTAINER function).

All RABNs to be deallocated must be returned to the Free Space Table.

Control parameter, ‘string’ not supported with the use of ADATCP connection string.

Please refer to the Adabas documentation, on which control parameter is not supported with ADATCP connection string.

Cannot write changes to the INI file.

Check subsequent messages for a detailed error reason.

A field's standard format cannot be converted to the required format.

None.

An overflow has occurred in the checkpoint block. The utility action has been carried out but will not be reflected in the checkpoints of the database.

Start the nucleus to transfer the entries in the checkpoint block to the checkpoint file. The ADANUC option AUTORESTART_ONLY can be used.

An internal checkpoint I/O (e.g. during a utility action) failed with a response code. The nucleus will shut down in the same way as ADAOPR CANCEL.

Analyze the response code given in the message and do the required action. Then restart the nucleus and the failed checkpoint will be recovered.

A descriptor that is contained in or derived from a periodic group cannot be used to control the unload sequence.

Use a different descriptor or unload in physical or ISN sequence.

The utility checkpoint could not be written because of response code 'number'.

Refer to the response code description and perform its action. It is just a warning, the utility will continue.

Adabas cannot be run on a machine with more CPUs than the license allows.

Run Adabas on a machine with less CPUs or upgrade your license.

A system call that was performed during the copy (move) process aborted.

See the subsequent 'errno' message.

The database size is restricted by license, so that a bigger database cannot be used or created.

Check your license for the currently-allowed database size, and either create a smaller database or upgared your license.

The required data set could not be created. The reason is given in a subsequent error message.

See the subsequent error message.

A CSA dump file could not be created or written due to an operating system error. See 'errno' and 'error text' for a detailed problem analysis.

The container file size registered in the database (GCB) and the size found in the raw section are not identical.

Check the settings of the environment variables that point to the container files. Use ADADEV's LAYOUT function and ADAREP's SUMMARY function and compare the values given for the container file size.

The container file in a file system is smaller than the size registered in the database (GCB).

Check the settings of the environment variables that point to the container files. Compare the file size with the size given by ADAREP's SUMMARY function.

The maximum size of Adabas container file has been exceeded.

Reduce the file size.

The current database is not a Version 6.1, Version 6.2 or Version 6.3 database.

None: ADACVT cannot be used to convert unsupported database versions.

ADACVT conversion to an older version is not allowed because encryption is not supported in that version.

None.

Conversion to the destination version is not permitted. Please refer to the CONVERT parameter for information about the conversions that are supported.

Use one of the valid keywords.

The size of the FDT is larger than the maximum FDT size allowed in the target version of the conversion. Specifically, the FDT may be too large because more than 926 fields have been defined, which was the maximum up to Adabas Version 6.1.

Remove all files where the FDT is too large.

AUTOSTART is disabled if ADACVT converts to a previous Adabas version.

Use the destination Adabas version to register the database for AUTOSTART.

ADACVT conversion to an older version is not allowed because of new features used.

Remove all files that use new Adabas features.

The spanned record flag was introduced in Version 670. When this flag is set, it is not possible to convert back to a previous version.

Clear the spanned record flag.

ADACVT conversion to an older version is not allowed because referential integrity is not supported in that version.

Drop all referential integrity constraints.

A double allocation has been detected between two or more files or a file and the free space table.

Run ADAVFY without any options to determine which parts of which files are affected. Contact your nearest support center with the output of ADAVFY.

The maximum number of blocks allowed for DATA is 16777215.

Correct the value for the parameter DATASIZE.

No data is loaded into DS RABN.

Restore and regenerate file and contact your nearest support center.

DS RABN is corrupted.

Do one of the following:

• Unload/export the file in physical sequence, decompress, compress and load/import it again (some data will be lost in the RABN), or

• Restore and regenerate file and contact your nearest support center.

Inconsistency between DS and FCB.

Unload/export the file in physical sequence and load/import it again.

No data is loaded into DS of file.

Restore and regenerate file and contact your nearest support center.

If RABN 'number' does not exist in DS, the FCB is corrupted.

Unload/export the file in physical sequence and load/import it again.

Inconsistency between DS and FCB.

Unload/export the file in physical sequence and load/import it again.

The nucleus aborted, a dump is automatically taken. Additional information concerning the reason is contained in the *.LOG file.

Check the reason for the abort, contact your nearest support center if necessary.

The specified database cannot be accessed for the reasons given in the message.

Correct the input line or assignment.

Summary message of ADAVFY, checked file contains errors.

Look at the displayed error messages and act accordingly.

A function was executed without the mandatory DBID parameter being set.

Set the DBID parameter.

A mismatch occurred between the DBID parameter and the database ID of the assigned ASSO data set.

Enter the correct database ID or exit the utility and assign correct data sets.

Operation not allowed to define DBID and Connection String together.

Please either specify the DBID or Connection String parameter only.

The nucleus session is now not active.

Reenter the DBID parameter in order to access the new session.

The nucleus session is now not active.

Reenter the DBID parameter in order to access the new session.

One of the following situations has occurred:

• You aren't using a license file - there are some restrictions if you use Adabas without a license file, in particular the size of the database is limited.

• Your license file has expired, in which case Adabas behaves as if you were using it without a license file.

• You are using a license file with a limitation in the size of the database.

Use an appropriate license file. You can activate the license file via the DBA workbench.

Either the database containers or an Adabas sequential file, for example a backup file created by ADABCK, belong to a different Adabas version. Please note that Adabas sequential files created with lower Adabas versions can usually be processed with a higher Adabas version, but not vice versa.

Use an appropriate Adabas version to process the database containers or Adabas sequential files. If you have to load data stored in an Adabas sequential file with a newer Adabas version into a lower version database, you can first load the data to a newer version database, and then convert the database to the lower version with ADACVT, and then create an Adabas sequential file that belongs to the lower version. However, this is only possible if no features of the higher version were used which were not available in the lower version.

The database which is to be started with OPTIONS=READONLY had been used for updates in the previous session. The previous session had not been terminated properly.

Restart the nucleus with OPTIONS=AUTORESTART_ONLY. After the nucleus has terminated, start it with OPTIONS=READONLY.

The database which is to be started with OPTIONS=READONLY had been used with OPTIONS=XA in the previous session. There are still open global transactions.

Start the nucleus with OPTIONS=XA, terminate all remaining global transactions, shut down the nucleus. Then start it with OPTIONS=READONLY.

The database which is to be started with OPTIONS=READONLY had been used with OPTIONS=XA in the previous session. There are still pending global transactions.

Start the nucleus with OPTIONS=XA, terminate all remaining global transactions, shut down the nucleus. Then start it with OPTIONS=READONLY.

The user tried to copy/move an Adabas container which is at the moment used by a nucleus or an update utility.

A PE/MU count byte was converted (new length or format). This means that the FDT written to the ADADCU output file DCUFDT does not represent the standard PE/MU decompression output.

Edit the DCUFDT/DCUOUT file.

The format/edit mask conversion has been performed for a field.

None.

The count byte was written to the output file, but not all of the elements of the PE/MU group were included.

Edit the DCUFDT/DCUOUT file.

The specified format buffer contained a literal for which a field name has to be set.

Edit the DCUFDT file.

No count byte was written to the DCUOUT file. The field is represented as a PE/MU group in DCUFDT, which means that the record structure does not match the FDT.

Edit the DCUFDT/DCUOUT file.

A field name occurred more than once in the format buffer. Field names must be unique, which means that a new field name has to be set.

Edit the DCUFDT file.

This message is issued if MU and PE not found in FDT of DCUDTA file.

No Action Required.

This message is issued in each run of ADADCU. If records are decompressed, it is an informational message. It is issued as a warning message if zero records are decompressed. This may be because there are no records in the input file DCUDTA or because the records have the wrong structure.

Check the input file DCUDTA.

RABNs can only be deallocated from the start or end of an extent. Otherwise the database would be fragmented.

Specify correct values for the RABN and SIZE parameters.

The extent to be deallocated is totally in use, no more unused space is present.

The VERIFY function of ADAINV has found inconsistencies between index and data storage.

Use the REINVERT function of ADAVFY to repair the index.

The same descriptor name has already been specified.

Correct the input line.

An attempt was made to delete one or more Adabas system files.

If you want to delete replication system files, use the function ADADBM REMOVE_REPLICATION. Deletion of other system files is not allowed as they are required by the Adabas nucleus.

A descriptor that is based on a multiple-value field may not be used to control the sequence in which a file's data records are exported.

Check the field name.

A descriptor that is based on a field defined with SQL null-value representation (NC) may not be used to control the sequence in which a file's data records are exported because this will result in data records being lost.

Check the field name.

The specified descriptor is defined on the sequential input file for ADAMUP's ADD function, but is not present in the database file to be updated.

Check the input file assignment(s) and the database file to be updated. ADAMUP's DE_MATCH=SUBSET can be used to continue.

Descriptor defined without unique status.

Check the file number or field name.

A descriptor that is based on a field defined with null value suppression (NU) may not be used to control the sequence in which a file's data records are exported because this will result in data records being lost.

Check the field name.

If using ADAFIN, the given function cannot be used because the file is active (i.e. opened by another user).

Check the file usage by displaying the user queue with ADAOPR.

The file system on which the current PLOG file is located is full. The nucleus is abnormally terminated.

Either make space available in the file system, or assign the PLOG to another file system that has enough free space. Then restart the nucleus.

A non-existent device was specified.

Correct the input line and rerun ADAORD.

The FDT file generated by ADADCU must be modified to be used as input file for an Adabas utility.

Check the FDT file and perform the necessary changes.

When processing an Adabas backup copy, the NOONLINE switch was used to allow unloading in one pass. However, this is only possible if there are no online data storage blocks for the file to be unloaded.

Rerun ADAULD without setting the NOONLINE switch.

An invalid CSA dump address was specified.

Correct the area parameter value.

The DATA padding factor must not be changed for ADAM files.

Rerun ADAORD without changing the DATA padding factor.

The referential constraint ‘refname’ does not exist.

Specify the correct name of the referential constraint.

The data set assigned contains no data.

Assign the correct data set.

The file's Data Storage is too fragmented.

Export and reimport the file; the KEEP_LAYOUT option must not be specified. Alternatively, unload the file and then delete it. Redefine the file using larger extents and then mass-add the unloaded file.

An error has been detected in data set `string', record `number', at offset `number'. The type of error is specified by a subsequent message.

Provide the correct input.

The DATA block size must not be decreased for ADAM files.

Correct the DSSIZE parameter and rerun ADAORD.

The ASSO space required to store the DSST blocks is not available, or the maximum number of DSST extents (15) has already been allocated.

If the error occurs during ADAFRM or when executing ADADBM's ADD_CONTAINER function with the NOCONTIGUOUS_DSST switch set, check whether the maximum number of DSST extents has been exceeded. If this is the case, reduce the number of DATA extents with different block sizes (ADAFRM), or make sure that the block size matches the block size of the previous DATA extent (ADADBM). If the error occurs when executing ADADBM's ADD_CONTAINER function with the CONTIGUOUS_DSST switch set, use a larger ASSO size, reduce the DATA extent size or free some space adjacent to the DSST allocation so the allocation can be made contiguously.

The DST parameter is not compatible with the RECORDS_STRUCTURE = NEWLINE_SEPARATOR parameter.

Instead of using the DST parameter, use the FIELDS parameter and specify the daylight saving time indicator(s) explicitly.

Multiple occurrences of ISN 'number' were detected in the DATA.

Run the verify utility ADAVFY and contact your nearest support center.

The provided ‘field’ cannot be used with the value provided in ‘area’.

Either remove the ‘field’ or use correct ‘area’.

‘field’ must be provided with the value mentioned in ‘area’.

Provide the ‘field’ parameter.

Adabas Analytics detected an unrecoverable error and initiated the termination of the Adabas nucleus process.

Restart the ealconfig configuration tool.

Worker thread number id lost his connection to the Adabas Analytics Server and it was configured (ON_ERROR) to abort the nucleus.

Start the Adabas Analytics Server and restart the database or change the configuration of this database.

Worker thread number id lost his connection to the Adabas Analytics Server and it was configured (ON_ERROR) to ignore this error.

Restart the Adabas Analytics Server.

The NUCELG file could be created during startup.

Check whether the file can be created, or if the NUCELG file location is valid.

Adabas Analytics detected an unexpected situation and generated a warning message in the nucleus log file. An error code is returned.

Contact your nearest support center.

Adabas Analytics detected an unexpected situation with the filtering of events and generated a warning message in the nucleus log file. An error code is returned.

Contact your nearest support center.

The file number provided is out of range for the Json element index in the eventtype.json file.

Enter a correct range specification (1-32000).

Adabas Analytics detected an unrecoverable error during initialization and initiated the termination of the Adabas nucleus process. An error code is returned.

Contact your nearest support center.

The provided trigger found in “condition” for the eventtypes.json file is invalid for the mentioned Json element index.

Enter a valid trigger value.

Found duplicate field in the output field of eventtype.json file and skip to register the eventtype.

Remove the duplicate field.

The event type area for the event type defined in the event types file at line ‘number’ is not valid.

Check the spelling of the event type definition.

One of the event type fields for the event type defined in the event types file at line ‘number’ is not valid.

Check the spelling of the event type definition.

Unable to parse eventtypes.json file due to missing or invalid file.

The event type field name for the event type defined in the event types file at line ‘number’ is not valid.

Check the spelling of the event type definition.

The event type field provided in the output_fields is invalid for Json element index of the eventtypes.json file.

Enter a valid value.

The file number provided in the Json element index in the eventtype.json file is invalid.

Enter a valid file number.

The provided trigger found in the eventtypes.json file is invalid for the mentioned Json element index.

Enter a valid trigger value.

An event could not be stored in the NUCELG file. A file write operation error occurred.

Check the permissions and whether the file can be written.

The Adabas Analytics Server cannot be reached and the configured number of retries (parameter MAX_RETRIES) to connect again has been reached.

Start the Adabas Analytics Server and restart Adabas.

Found invalid field for the eventtype and skip to register the eventtype.

Remove the invalid fields.

During Adabas startup, the worker thread id could not create a socket connection to the Analytics Server. Depending on the configured ‘ON_ERROR’ action the nucleus terminates or tries to reconnect.

Start the Analytics Server.

Internal record structure corrupted in DS RABN.

Do one of the following:

1. Unload/export the file in physical sequence, decompress, compress and load/import it again (this will lose some data), or

2. Restore and regenerate file and contact your nearest support center.

A required elementary field has not been supplied.

Correct the input line.

A mismatch occurred between the DBID parameter and the database ID of the assigned NUCELG file.

Enter the correct database ID or exit the utility and assign correct NUCELG file.

This element type is not permitted in this context.

Correct the input line.

The keywords allowed for the LOGGING parameter have changed. The parameter is set to "OFF" by Adabas. This yields the behaviour expected by the user when specifying ENABLED.

Change your input scripts to avoid this warning.

An error occurred while deleting files during the reorder phase.

Contact your nearest support center.

You tried to define a descriptor value larger than the maximum supported descriptor value size, although the descriptor is defined without the TR option.

Either redefine the descriptor with the TR option or change the descriptor vaalue.

The input file contains invalid data for the required format.

Correct the input file or check the FDT.

The input record is too short for the defined FDT.

Correct the FDT or the input file.

For ADACMP: a user-supplied PE count (which was specified in the input record) is invalid.
For ADADCU: a PE count is too big.

For ADACMP: correct the input file.
For ADADCU: increase the setting of the ADADCU parameter MUPE_C_L.

For ADACMP: a user-supplied MU count (which was specified in the input record) is invalid.
For ADADCU: an MU count is too big.

For ADACMP: correct the input file.
For ADADCU: increase the setting of the ADADCU parameter MUPE_C_L.

A user-supplied ISN is invalid.

Correct the input file.

An unexpected overflow of an internal buffer occurred.

Contact your nearest support center.

A compressed record is larger than the DATA block size for the specified file.

Allocate a DATA extent with a larger block size.

A field has been truncated and this record has been omitted from the DCUOUT file.

If a format buffer is being used, provide a length parameter for the field. If the standard FDT is being used, change the standard length, using ADADBM, and unload the file.

The decompressed record created by ADADCU is larger than the ADADCU parameter MAX_DECOMPRESSED_SIZE. The reason for the large record size may be:

• Multiple fields or periodic groups with large MU or PE counts.

• LOB values

Increase the value of MAX_DECOMPRESSED_SIZE.

A record in the DATA file has an erroneous structure.

Run the RECORD option of ADAVFY and send the output together with the unloaded file and an export copy of the file to your nearest support center.

An NC-option field being decompressed by ADADCU was null, which is not permitted without the S-element of that field. This can happen if the NULL_VALUE option of ADAFDU is not used.

Use the FIELD option of ADADCU and specify all NC-option fields together with their S-elements (for example: AAS,AA,BBS,BB, ...) or use the NULL_VALUE option of ADADCU.

Descriptor value found for more than one record.

Check the conflicting ISNs.

An ISN provided with the input data exceeds the limit (MAXISN) in effect for the file.

Use a different ISN or extend the file's Address Converter.

The ISN to be deleted was not in use in the file's Address Converter.

Check the ISNs supplied.

An error occurred during an asynchronous I/O operation. action is the type of I/O operation; either 'read' or 'write'. dsname and rabn identify the container and RABN where the error occurred. err contains the error number and the textual description of the error (as returned by the operating system).

Depending on the error type, check your I/O devices including the network (in case of remote access), the file system, the contents and/or permissions of the datasets.

Error in connecting the database.

Check the TCP configuration for correctness and make sure the database is online.

During auto restart, an error occurred in the file indicated in the subsequent message. The file's contents are destroyed.

Rebuild the file using ADABCK RESTORE=file and ADAREC REGENERATE=file.

While updating the index, an error resulted in a nucleus response code.

Ensure that the correct BACKUP was restored; that the PLOGs were regenerated in the correct order; that the correct file was reloaded when reloading a file; that the nucleus was started with OPTIONS=UTILITIES_ONLY and that the correct utilities have been rerun.

A system call aborted.

See the subsequent 'errno' text and contact your nearest support center if necessary.

This message specifies field, ISN, and offset where the error occurred. A subsequent error description is displayed in a second line.

While processing the protection log, an executed command resulted in a nucleus response code.

Examine the block at the record number associated with the error response, e.g. a file may not have been restored, with ADABCK, with the correct dump. This results in the file being in a state different to that when the original command was executed.

An error occured during semaphore operations. The reason is usually that IPC resources were not removed following the crash of another nucleus or utility process.

Delete IPC resources with showipc -k and try again.

Error in the Adabas code - an unexpected internal error number occurred.

Report the error to your nearest support center, so that the Adabas development team can fix the error.

Cannot remove event type because it was not found.

Correct the name of the event type to be removed.

The external backup feature is already active, and the nucleus is in synchronization mode.

Use the EXT_BACKUP=CONTINUE function if you want to continue processing.

The selected function conflicts with the initiated external backup mode, which can lead to the execution of some functions being denied.

Wait until the external backup mode has terminated.

The external backup feature has not been started.

Use the EXT_BACKUP=PREPARE function first.

The external backup cannot be initiated because it conflicts with an Adabas utility that has exclusively locked some resources.

Ensure that no Adabas utility that performs updates is active when you want to initiate an external backup.

This is a warning message that the given file is near the end of the maximum number of FCB extents permitted. Program execution continues normally.

This file is a candidate for reorganizing later on (e.g. with ADAORD). In this case, allocate enough space for 'type' to avoid extending.

An invalid RABN extend has been found for a file.

Search for lost RABNs with the LOST option of ADAVFY and recover them using the ADADBM utility.

It is not possible to change a sequential file which has the status "during creation" or a TEMP or SORT container which is locked.

None.

The first character of field name is not alphabetic.

Correct the field name.

A utility has terminated while updating the Address Converter or the Data Storage, leaving the file in an inconsistent state.

Use ADAULD to unload the file in physical sequence, then reload it using ADAMUP. It is, however, not generally possible to determine which records have already been added/deleted. Therefore, if a backup copy is available, the file should be restored and then regenerated if necessary.

ADAVFY was executed while the nucleus was active. Some of the inconsistencies detected for file 'fnr' can be repaired.

Shutdown nucleus and rerun ADAVFY.

All errors detected by ADAVFY could be repaired.

None.

ADAVFY has detected that the file has invalid extent entries.

Either restore the file from a backup, or, if the invalid extent is not a DS, you can unload the file in physical sequence and load it again as a new file.

The file control block of the file is partially corrupted.

Contact your nearest support center.

The file control block (FCB) for the specified file cannot be accessed.

Contact your nearest support center.

FCB of file is partially corrupted.

Unload/export the file in physical sequence and load/import it again.

FCB of file is partially corrupted.

Unload/export the file in physical sequence and load/import it again.

FCB of file is partially corrupted.

Unload/export the file in physical sequence and load/import it again.

FCB of file is partially corrupted.

Unload/export the file in physical sequence and load/import it again.

FCB of file is partially corrupted.

Unload/export the file in physical sequence and load/import it again.

A RABN count in the FCB that is used for DS reusage, is invalid.

With adadbm remove and re-add the space reusage flag for this file: adadbm db=xx reuse=nods, file=yy adadbm db=xx reuse=ds, file=yy

A count in the FCB that is used for ISN reusage, is invalid.

Use adadbm to remove and re-add the ISN reusage flag for this file: adadbm db=xx reuse=noisn, file=yy adadbm db=xx reuse=isn, file=yy

A utility has terminated abnormally while rebuilding the index, leaving the index in an inconsistent state. When using ADAREC, the index has been marked as not accessible due to an index response during regenerate.

Use ADAINV to reinvert all descriptors or use ADAULD to unload the file in physical sequence and reload it using ADAMUP.

FCB of file is partially corrupted.

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.

FCB of file is partially corrupted.

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.

While loading a user exit the requested function was not found in the accessed shared library.

Check your environment variable pointing to the shared library and check the entry points within the shared library.

The FDT file contains a line that is more than 132 characters long.

Correct the FDT file.

(This explanation applies to all error messages beginning with the letters "FDT", except for those listed below). The FDT of the file to be verified is corrupted.

Restore and regenerate file and contact your nearest support center.

Field change not allowed.

Use only allowed field change options.

A structural mismatch has been detected between the FDT contained on the sequential input file and the associated FDT in the database file to be updated.

Check the assignments. The FDT keyword can be used to display both FDTs.

There are too many entries defined in the FDT.

Decrease the number of entries in the FDT, or use a larger block size for ASSO1.

A mismatch at field `string' has been detected between the FDT contained on the sequential input file and the associated FDT in the database.

Check the format, default length and options of the conflicting field. The FDT keyword can be used to display both FDTs.

ADAMUP can add data to an empty file with a different FDT, but only if NEW_FDT has been specified.