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 dataset/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 dataset does not satisfy the rules.

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

The field definition table (FDT) from the input dataset 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 dataset does not match the FDT from the file; or

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

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

Check your input dataset 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 dataset.

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 eight Adabas system files is 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 dataset 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.