ADALOD Utility Messages

Overview of Messages

ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | 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-142 | ERROR-143 | ERROR-144 | ERROR-145 | ERROR-146 | ERROR-147 | ERROR-148 | ERROR-149 | ERROR-150 | ERROR-151 | ERROR-152 | ERROR-153 | ERROR-155 | ERROR-156 | ERROR-157 | ERROR-158 | ERROR-159 | ERROR-160 | ERROR-161 | ERROR-162 | ERROR-163 | ERROR-164 | ERROR-165 | ERROR-166 | ERROR-167 | ERROR-168 | ERROR-169 | ERROR-170 | ERROR-171 | ERROR-172 | ERROR-173 | ERROR-174 | ERROR-175 | ERROR-176 | ERROR-177 | ERROR-178 | ERROR-179 | ERROR-180 | ERROR-182 | ERROR-183 | ERROR-184 | ERROR-185 | ERROR-186 | ERROR-187 | ERROR-189 | ERROR-190 | ERROR-192 | ERROR-196 | ERROR-901 | ERROR-902 | ERROR-903 | ERROR-904 | ERROR-905 | ERROR-906 | ERROR-908 | ERROR-909 | ERROR-910 | ERROR-911 | ERROR-912

ERROR-121 Requested restart not possible
Explanation

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).

Action

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


ERROR-122 TEMP data set too small; input record count= count
Action

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


ERROR-123 Missing utility function
Action

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


ERROR-124 Multiple utility functions supplied
Action

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


ERROR-125 Parameter 'ADAMPARM' for non-ADAM-file not permitted
Action

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


ERROR-126 Invalid value for the parameter 'ADAMPARM'
Explanation

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

Action

Supply the correct parameter value and rerun the ADALOD job.


ERROR-128 Parameter 'ADAMDE' for non-ADAM-file not permitted
Action

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


ERROR-129 Parameter 'ADAMDE' mandatory for ADAM file
Action

Supply the correct parameter value and rerun the job.


ERROR-130 Parameter 'ADAMOFLOW' for non-ADAM file not permitted
Action

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


ERROR-131 Invalid value for the parameter 'UQDE': field-name is not a valid descriptor name
Explanation

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.

Action

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


ERROR-132 Invalid 'ADAMDE' field: field-name ; conflicting field attributes or unknown descriptor name
Explanation

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)

Action

Supply the correct parameter value and rerun the ADALOD job.


ERROR-133 Invalid value for the parameter 'ADAMOFLOW'
Explanation

The value must be smaller than DSSIZE.

Action

Supply the correct parameter value and rerun the job.


ERROR-134 Incorrect FDT found in input data set
Explanation

Either the field definition table (FDT) expected in the first record is missing from the data set or the FDT structure read from the data set does not satisfy the rules.

Action

Verify that the input data set is valid. Supply a correct input data set and rerun the job. If the problem persists, contact your Software AG technical support representative for assistance.


ERROR-135 FDT structure mismatch
Explanation

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.

Action

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).


ERROR-136 FDT larger than 4 ASSO blocks
Explanation

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


ERROR-137 The input data set/file DDEBAND or DDISN does not have the record format variable or variable blocked (V or VB)
Explanation

The specified input data set is invalid.

Action

Supply a correct input data set and rerun the ADALOD job.


ERROR-138 invalid USERISN isn-number found input record count = count
Explanation

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.


ERROR-139 ISNPOOL overflow ('LIP' parameter value too small) count records already read from DDISN
Explanation

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

Action

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


ERROR-142 Duplicate USERISN isn-number found
Explanation

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.


ERROR-143 file-type file already present
Explanation

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

Action

Check the current system file assignments on the ADAREP report.


ERROR-144 Already 10 Adabas system files defined
Explanation

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

Action

Check current system file assignments on the ADAREP report.


ERROR-145 Invalid FDT format
Explanation

The structure of the input FDT is incorrect.

Action

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


ERROR-146 Invalid list of DELISNS
Explanation

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

Action

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.


ERROR-147 Invalid ISN range
Explanation

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

Action

Correct the parameter values and then rerun the ADALOD job.


ERROR-148 File file-number is not/cannot be anchor of an expanded file
Explanation

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.


ERROR-149 Compressed record too long
Explanation

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.


ERROR-150 Invalid ISN to be deleted (was) found
Explanation

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.


ERROR-151 Increasing MAXISN not allowed
Explanation

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

Action

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


ERROR-152 Conflicting USERISN options
Explanation

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.

Action

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.


ERROR-153 Invalid ISN for hyperdescriptor desc-name
Explanation

The ISN returned from the hyperdescriptor exit

  • 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)


ERROR-155 Adabas nucleus required
Explanation

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.

Action

Start the nucleus, then rerun the ADALOD job.


ERROR-156 Conflicting owner-ID length
Explanation

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).

Action

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


ERROR-157 Conflicting usage of 'LOWNERID' and 'ETID'
Explanation

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.

Action

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


ERROR-158 Invalid owner-ID in input record
Explanation

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

Input record count = (count)

Action

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


ERROR-159 Undefined ETID
Explanation

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.

Action

Specify an parameter value, then rerun the ADALOD job.


ERROR-160 Descriptor value too long
Explanation

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

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

Action

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


ERROR-161 Conflicting parameter parameter
Explanation

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

Action

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


ERROR-162 Hyperdescriptor ISN changed in non-USERISN file
Explanation

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

Action

Correct the USERISN setting of the file.


ERROR-163 Invalid value for parameter 'ALLOCATION'
Explanation

Valid values are ALLOCATION={FORCE | NOFORCE}.

Action

Supply the correct parameter value and rerun the job.


ERROR-164 TEMP block size too small
Explanation

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.

Action

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


ERROR-165 Conflicting file encodings
Explanation

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

Action

Adjust the file encodings and rerun the job.


ERROR-166 Wide fields exist, but the database is not UES-enabled
Explanation

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

Action

Enable the database for universal encoding and rerun the job.


ERROR-167 Error initializing collating user exit - return code=return-code
Explanation

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

Action

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


ERROR-168 Collating user exit not loaded
Explanation

The collation descriptor user exit requested is not loaded.

Action

Load the exit and rerun the job.


ERROR-169 Conflicting '{RPLKEY|RPLDSBI}' parameter.
Explanation

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

Action

Supply the correct parameter value and rerun the job.


ERROR-170 Invalid 'RPLKEY'-Field: 'field-name'
Explanation

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

Action

Supply the correct parameter value and rerun the job.


ERROR-171 RPLTARGETID is specified but the database is not enabled for replication.
Explanation

RPLTARGETID is not valid unless replication is active.

Action

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


ERROR-172 RPLTARGETID = DBID or greater than 65535 is not allowed.
Explanation

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

Action

Supply the correct parameter value and rerun the job.


ERROR-173 RPLTARGETID is not allowed for ciphered files.
Explanation

Ciphered files may not be replicated.

Action

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


ERROR-174 A REPLICATOR file may only be loaded on an Event Replicator Server.
Explanation

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

Action

Investigate the cause of the error.


ERROR-175 Error loading module ADARPU: reason
Explanation

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

Action

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


ERROR-176 Load of a new file with RPLLOAD=YES requires a non-zero RPLTARGETID
Explanation

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.

Action

Supply the correct parameter value and rerun the job.


ERROR-177 ADALOD terminated due to the above replication related errors
Explanation

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

Action

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


ERROR-178 Update with RPLLOAD=YES may only be executed with a replicated file
Explanation

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

Action

Correct the error and rerun the job.


ERROR-179 An Event Replicator database may only contain the files CHECKPOINT, SECURITY, REPLICATOR, and SLOG
Explanation

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.

Action

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


ERROR-180 MU/PE index size mismatch during update.
File index size = n byte(s).
DDEBAND index size = n byte(s).
Explanation

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 ADACMP or ADAULD input. To determine what size indices are used in a file, run an ADAREP report.

Action

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.


ERROR-182 RPLTARGETID is not allowed for files with spanned data storage records
Explanation

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.

Action

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.


ERROR-183 Base file base-fnr does not fit to LOB file lob-fnr
Explanation

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.

Action

Specify correct FILE and BASEFILE parameters and try again.


ERROR-184 LOB file lob-fnr does not fit to the base file base-fnr
Explanation

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.

Action

Specify correct FILE and LOBFILE parameters and try again.


ERROR-185 Parameter parm-name not allowed for LOB file
Explanation

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

Action

Load the LOB file without this parameter.


ERROR-186 DDISN/DELISN delete of an ISN with a LOB reference is not allowed.
ISN = nnnnnn
Explanation

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.

Action

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.


ERROR-187 ANCHOR parameter not allowed for a file with LOB fields
Explanation

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

Action

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


ERROR-189 The database is active but the utility communications block (DIB) is missing the nucleus entry
Explanation

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

Action

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


ERROR-190 SYFMAXUV parameter value is invalid. A value between 0 and 20 is required.
Explanation

An invalid value was specified for the SYFMAXUV parameter. A value between 0 (zero) and 20 is expected.

Action

Correct the parameter setting and try again.


ERROR-192 RPLINITERROR parameter value is invalid. Valid values are ‘CONTINUE’ or ‘FAIL’. Supply the correct parameter value and rerun the job.
Explanation

An invalid value was specified for the RPLINITERROR ADALOD LOAD parameter. The RPLINITERROR parameter specifies the behavior of the ADALOD LOAD utility if replication errors occur when ADALOD LOAD replication is requested (the RPLLOAD parameter is set to YES or FILE). Valid settings for the RPLINITERROR parameter are "CONTINUE" or "FAIL".

Action

Correct the invalid parameter specification and try again.


ERROR-196 An SLOG system file may only be loaded on a Reptor database.
Explanation

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

Action

Correct the parameters and rerun the job.


ERROR-901 Unexpected Event Replicator Server response rc, subcode sc , location loc. Replication has failed due to the above errors. ADALOD will continue but the changes will not be replicated. Replication has been deactivated for file fnr.
Explanation

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. ADALOD LOAD replication was requested during the run (RPLLOAD was set to "YES" or "FILE"), but failed. ADALOD LOAD processing will continue because the RPLINITERROR parameter was set to "CONTINUE".

The last line ("Replication has been deactivated for the file fnr") appears only if the RPLERRORDEACTFILE parameter was set to "YES". The file number for which replication was deactivated is given in the message.

Action

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 to resolve any errors. If necessary, contact your Software AG support representative for further assistance.


ERROR-902 Duplicate Replication jobs for the same file are not allowed
Explanation

Multiple replication jobs cannot run concurrently for the same file.

Action

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


ERROR-903 RPLCLEANUP was issued for this ADALOD token
Explanation

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.

Action

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


ERROR-904 Event Replicator Server id replication pool overflow
Explanation

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

Action

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


ERROR-905 Database dbid not defined to Event Replicator Server id
Explanation

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.

Action

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.


ERROR-906 Event Replicator Server id, no active subscription or destination for file number.
Explanation

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.

Action

First verify and correct (as necessary) the file number or the 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.


ERROR-908 The versions of ADALOD and ADARPU are incompatible
Explanation

ADALOD and ADARPU are internally not the correct versions.

Action

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.


ERROR-909 Internal error in ADARPU+offset
Register contents at time of error:
R0-R3 ##### ##### ##### #####
R4-R7 ##### ##### ##### #####
R8-R11 ##### ##### ##### #####
R12-R15 ##### ##### ##### #####
Inform your DBA
Explanation

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

Action

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


ERROR-910 ADARPU cannot load program ADAMGT
Explanation

ADARPU could not load program ADAMGT.

Action

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.


ERROR-911 ADAMSG is incompatible with ADARPU
Explanation

ADARPU has detected an invalid version of ADAMSG.

Action

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.


ERROR-912 The source database Adabas version is not compatible with the Reptor Adabas version
Explanation

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 Server.

Action

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