ADALOD Error Messages

This error may occur for one of the following reasons:

• There is no job to be restarted.

• A fundamental parameter value has been changed.

• The previous job abended before reaching the first restart point (the file is not in load status).

• The previous job abended in a state from which no restart is possible (the file is in load status).

Correct the cause of the error, and rerun the ADALOD job.

Supply a larger TEMP data set/file. See the Adabas Utilities documentation for information about calculating TEMP space.

Supply either LOAD or UPDATE as the ADALOD function in the parameter input and rerun the ADALOD job.

Supply either LOAD or UPDATE as the ADALOD function in the parameter input and rerun the ADALOD job.

Either add the parameter ADAMFILE or remove the ADAMPARM parameter and rerun the ADALOD job.

The value for this parameter must be in the range 1 to 255.

Supply the correct parameter value and rerun the ADALOD job.

Either supply the parameter ADAMFILE as well, or remove the ADAMDE parameter. Rerun the ADALOD job.

Supply the correct parameter value and rerun the job.

Either supply the parameter ADAMFILE as well, or remove the `ADAMOFLOW' parameter. Rerun the ADALOD job.

The field to be defined as a unique descriptor is invalid. Either it is a simple field and not a descriptor, or the field name is unknown, or it is a descriptor in a periodic group. Probable cause is a misspelling of the descriptor name.

Supply the correct UQDE parameter value and rerun the ADALOD job.

An ADAM descriptor must meet all the following:

• Be a single field (no MU option)

• Be a unique descriptor

• Not be contained in a periodic group

• Not have the NU option

• Have a default length (cannot be variable)

Supply the correct parameter value and rerun the ADALOD job.

The value must be smaller than DSSIZE.

Supply the correct parameter value and rerun the job.

One of the following is the case:

• The field definition table (FDT) expected in the first record is missing, or

• The FDT structure read from the input data set does not satisfy the rules.

Check whether the input data set is valid. Supply a correct input data set and rerun the job.

The field definition table (FDT) from the input data set and the FDT from file "file-number" are not the same (the displayed message text contains an actual file number).

One of the following has happened:

• The file is to be updated and the FDT from the input data set does not match the FDT from the file; or

• The file has been deleted with "KEEPFDT" and the FDT from the input data set does not match that old FDT; or

• The FDT from the input data set does not match the FDT from the anchor of the expanded file.

Check your input data set and your FILE and ANCHOR parameters. If the ADALOD LOAD function was being run, consider using the IGNFDT parameter (refer to the Adabas Utilities documentation for more information).

System restriction: the FDT is too large for the device type in use. A load is not possible.

Supply a correct input and rerun the ADALOD job.

The USERISN "isn-number"

• is greater than MAXISN or less than MINISN; or

• does not belong to any ISN range of the expanded file.

The displayed message text contains actual ISN and count values.

Each single ISN requires four bytes, each ISN range requires eight bytes of storage.

Increase the size of the ISN pool (LIP). Supply the correct parameter value and rerun the ADALOD job.

ADALOD requires these values in units of blocks. The value must be in the range 1B to 65535B.

Supply the correct parameter value and rerun the ADALOD job.

One of the following occurred:

• The supplied USERISN was already present in the file being processed; or

• The ISN appeared twice in the input data set.

The record cannot be added.

The requested system file is already present. The file cannot be loaded.

Check the current system file assignments on the ADAREP report.

A maximum of ten Adabas system files (files loaded with the SYSFILE file type) are already present. The file cannot be loaded.

Check current system file assignments on the ADAREP report.

The structure of the input FDT is incorrect.

Ensure that your input data set was created using the ADACMP or ADAULD utility.

The DELISN parameter list is wrong, or the input from the DDISN file contains incorrect data.

Check for

• descending or overlapping ISN ranges

• the same ISN specified more than once

• invalid record length (not a multiple of 4 or 8)

The accessed ISN was "isn-number" (the displayed message contains an actual ISN value). Check your input and rerun the ADALOD job.

The ISN range defined by MINISN and MAXISN is invalid. The range conflicts with another ISN range of the expanded file.

Correct the parameter values and then rerun the ADALOD job.

The specified file is

• part of an existing expanded file, but not the anchor file; or

• a coupled or multiclient file and therefore cannot be an anchor file.

Input record count = "count-a" Length of record = "count-b" bytes Maximum record length = "count-c" bytes

The record is longer than allowed by the MAXRECL parameter or by the characteristics of the data storage device.

At least one ISN of the "range"

• is greater than MAXISN or less than MINISN; or

• does not belong to any ISN range within the expanded file.

The file has been loaded with the NOACEXTENSION parameter. It is therefore not possible to increase MAXISN.

Remove the MAXISN parameter, and then rerun the ADALOD job.

There are two possible situations:

1. The existing file is defined with the USERISN option, but the records from the input file are not defined with the USERISN option.

2. The USERISN options for the file to be loaded and those from the anchor of the expanded file do not match.

Respectively:

1. Consider using the USERISN option for the records from the input file, correct the file, and rerun the ADALOD job.

2. Check your input file and the USERISN parameter, correct any error, and then rerun the ADALOD job.

The ISN returned from the hyperexit

• is less than MINISN or greater than MAXISN; or

• belongs to another part of the expanded file.

Original ISN: (isn-number) Modified ISN: (isn-number) Record count: (count)

The Adabas nucleus must be active when

• a file is being loaded that has file selection criteria (expanded file component); or

• records are being loaded with a new owner ID.

Start the nucleus, then rerun the ADALOD job.

One of the following caused the message to occur:

• The LOWNERID parameter value is not in the range 0-8; or

• The ETID owner ID is longer than LOWNERID (or longer than the owner ID length of the file to be updated).

Supply the correct LOWNERID value, then rerun the ADALOD job.

The input file is being loaded/added

• with owner IDs, but the owner IDs are not present and the ETID parameter is missing; or

• without owner IDs, but the ETID parameter is specified.

Supply the correct parameter value for one or both of the parameters, then rerun the ADALOD job.

The owner ID is too long to fit into the record of the file being loaded or added.

Input record count = (count)

Specify an appropriate owner ID, then rerun the ADALOD job.

One of the following is the case:

• The user ID referred to by the ETID parameter is not defined; or

• The user has not been assigned an owner ID.

Specify an parameter value, then rerun the ADALOD job.

A descriptor value together with the owner ID is longer than 253 bytes.

Input record count = (count) Descriptor name = (desc-name)

Specify an appropriate combination of owner ID and descriptor value, then rerun the ADALOD job.

The "parameter" parameter is invalid as given or implied. It must be the same as for the anchor of the expanded file.

Specify the correct parameter value, then rerun the ADALOD job.

The ISN assigned to a descriptor value was modified by a hyperexit but the file is not a USERISN file. Changing hyperdescriptor ISNs is only permitted in USERISN files.

Correct the USERISN setting of the file.

Valid values are ALLOCATION={FORCE | NOFORCE}.

Supply the correct parameter value and rerun the job.

An attempt to store data in a temp block failed because the temp block size is not large enough to hold the amount of data to be stored.

Choose a temp device type with block size equal to or greater than the Associator block size plus 16. Then rerun the job.

The file encodings on the input tape do not match the existing file. They must be the same as the existing file.

Adjust the file encodings and rerun the job.

A file with wide-character (W) format fields cannot be loaded until the database is UES enabled.

Enable the database for universal encoding and rerun the job.

An error occurred while the collation descriptor user exit was being initialized.

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

The collation descriptor user exit requested is not loaded.

Load the exit and rerun the job.

The RPLKEY or RPLDSBI parameter (as specified in the message) is invalid as given or implied. It is only valid when RPLTARGETID is specified.

Supply the correct parameter value and rerun the job.

The field to be defined as a replication key is invalid. Either the field name is undefined, or it is not a descriptor.

Supply the correct parameter value and rerun the job.

RPLTARGETID is not valid unless replication is active.

Investigate the cause of the error. Correct it and rerun the job.

Loading a file with RPLTARGETID = DBID is not allowed. The valid range for RPLTARGETID is 1 through 65535.

Supply the correct parameter value and rerun the job.

Ciphered files may not be replicated.

Investigate the cause of the error. Correct it and rerun the job.

The Replicator or SLOG system file may only be loaded on a database that has been defined as an Event Replicator database.

Investigate the cause of the error.

ADALOD was unable to load module ADARPU for the reason listed in the message.

Investigate the cause of the error. Correct it and rerun the job.

When loading a new file when replication has been activated using the RPLLOAD=YES parameter, a target Event Replicator Server must be specified by the RPLTARGETID parameter.

Supply the correct parameter value and rerun the job.

A replication error caused ADALOD to terminate. An earlier error message explains the detailed cause of the error.

Investigate the cause of the error. Correct it and rerun the job.

When updating a file with replication activated by specifying the RPLLOAD=YES parameter, the file must already be defined as replicated.

Correct the error and rerun the job.

A database defined as an Event Replicator Server (created with ADADEF DEFINE REPTOR=YES) must not contain user files or system files not related to replication.

Do not attempt to load files other than CHECKPOINT, SECURITY, REPLICATOR, or SLOG files.

The size of the MU/PE indices in the target Adabas file do not match the size of the indices in the input data. ADALOD processing has stopped.

As of Adabas 8, an MU/PE index can be either one or two bytes. When doing an update to an existing file with compressed input from either an ADACMP or ADAULD run, it is possible that the size of the MU/PE indices in the existing Adabas file will not match the size of the indices in the ADCMP or ADAULD input. To determine what size indices are used in a file, run an ADAREP report.

Correct the settings for the compressed MU/PE sizes, if appropriate, using the ADACMP MUPEX and MUPECOUNT parameters and retry. If errors persist, contact your Software AG support representative.

An attempt was made to specify the ADALOD RPLTARGETID parameter for a file that contains spanned records. Replication is not allowed for files containing spanned records.

Review and correct the parameters specified in the ADALOD run and ensure that you are not trying to replicate a file containing spanned records. Then try running the job again.

When asked to load a LOB file, ADALOD found that the file specified in the BASEFILE parameter is not suitable for use as the base file for this LOB file, for one of the following reasons:

• The supposed base file does not contain large object (LB) fields.

• The file's LOB information does not refer to the specified LOB file.

• The file's UES encoding information is different from that of the LOB file.

Specify correct FILE and BASEFILE parameters and try again.

When asked to load a base file, ADALOD found that the file specified in the LOBFILE parameter is not suitable for use as a LOB file for this base file, for one of the following reasons:

• The supposed LOB file is not a LOB file.

• The file's LOB information does not refer to the specified base file.

• The file's UES encoding information is different from that of the base file.

Specify correct FILE and LOBFILE parameters and try again.

The parameter specified in the message (parm-name) cannot be used for a LOB file.

Load the LOB file without this parameter.

When performing ADALOD UPDATE operations on a large object (LOB) base file, you are not allowed to delete ISNs that contain references to LOB values that are outsourced in the associated LOB file. This is true whether deleting ISNs using the DELISN keyword or a DDISN data set to specify the ISNs to be deleted.

The file is now in an inaccessible state.

Restore the file from backup or reload it and remove the DDISN/DELISN deletion of the ISN(s) containing LOB references. Then resubmit the ADALOD UPDATE job.

A file with large object (LB) fields cannot be an expanded file.

Load the file as a simple (non-expanded) file. Consider using the ISNSIZE=4 parameter setting.

The ADALOD utility determined the nucleus was active without a DIB entry.

Check the job to ensure the correct ASSO, DATA, and WORK data sets are specified for the given DBID.

An ADALOD communication to the Event Replicator Server has failed with the response and subcodes listed in the message and at the location listed in the message.

Verify and correct (if necessary) the ADALOD parameters and JCL. Refer to the Adabas response code descriptions for information about the response code and subcode. If necessary, contact your Software AG support representative for further assistance.

There cannot be multiple ADALOD jobs concurrently executing with the same file number replicated.

Verify and correct (if necessary) the ADALOD job parameters for correct information concerning replication. If problems persist, contact your Software AG support representative for assistance.

An RPLCLEANUP was issued for the Event Replicator Server. This removed the ADALOD token and communication to the Event Replicator Server is no longer possible for this job.

Determine why the operator RPLCLEANUP command was issued. Prepare for file recovery as necessary before rerunning ADALOD.

The replication pool for the Event Replicator Server listed in the message has an overflow condition, which is a critical error.

Refer to the Event Replicator Server job’s system log for error messages, which may provide possible actions to take to resolve the problem.

The Adabas database with the database ID (dbid) listed in the message is not defined to the Event Replicator Server (id) listed in the message.

Verify and correct the JCL or input parameters for the ADALOD run. If they are correct, modify the Replicator system file definitions. Then try the ADALOD run again.

No active destination or subscription could be found for the file listed in the message (number) on the Event Replicator Server (id) named in the message.

First verify and correct (as necessary) the file number or Event Replicator Server target ID for the ADALOD run. If they are correct, modify the Replicator system file subscription and destination definitions. Then try the ADALOD run again.

ADALOD and ADARPU are internally not the correct versions.

Verify and correct (if necessary) the JCL allocation of libraries and input parameters to ADALOD. If problems persist, contact your Software AG service representative for assistance.

Verify and correct (if necessary) the JCL allocation of libraries or input parameters to ADALOD. If problems persist, contact your Software AG service representative for assistance.

ADARPU has failed with an internal error at the offset given in the message.

Contact your Software AG support representative and provide details of the failure.

ADARPU could not load program ADAMGT.

Verify and correct (if necessary) the JCL allocation of libraries and input parameters to ADALOD. If problems persist, contact your Software AG service representative for assistance.

ADARPU has detected an invalid version of ADAMSG.

Verify and correct (if necessary) the JCL allocation of libraries and input parameters to ADALOD. If problems persist, contact your Software AG service representative for assistance.

The version of Adabas or the Event Replicator used by the Adabas database is not the same as the version of Adabas or Event Replicator used by the Event Replicator database.

Resolve the discrepancy in Adabas or Event Replicator versions before you try again.