ADADBS Error Messages

The value for a padding factor must be in the range 1 to 90%.

Correct the parameter value and rerun the job.

A valid encoding value is in the range 1 through 4095.

Supply a valid encoding value for the parameter and rerun the job.

Depending on the function to be performed, one or more file numbers must be supplied.

Supply the correct parameter value and rerun the job. Refer to the Adabas Utilities documentation for more information.

Either ON or OFF is required to specify the new mode for DS or ISN reusage.

Supply the correct parameter value and rerun the job.

A valid value is in the range 1 through 255.

One of the parameters ASSOSIZE or DATASIZE is mandatory. You cannot use both.

Supply the correct parameter value and rerun the job.

Either the xxSIZE parameter specified an incorrect value, or more than one xxSIZE parameter was specified.

Supply the correct parameter value and rerun the job. Only one SIZE parameter can be specified. The value must be specified in blocks. Choose one of the following sizes:

• ACSIZE

• DSSIZE

• NISIZE

• UISIZE

The following rules apply:

• Only one of the LENGTH, OPTION, or FORMAT parameters can be specified.

• If specified, the value of the LENGTH parameter must be greater than zero and less than or equal to the permitted maximum according to the requested field's format.

• If specified, the only OPTION parameter value permitted is LA.

Supply the correct parameter value and rerun the job.

The parameter TODATE must be specified in the format:

TODATE=YYYYMMDD

Supply the correct parameter value and rerun the job.

The priority is assigned to a specific user which is uniquely identified by its user ID. The user ID parameter is missing.

Supply the correct parameter value and rerun the job.

The value is one of the following:

• missing;

• not found in the FDT; or

• found in the FDT, but is not a descriptor.

Supply the correct parameter value and rerun the job.

A valid value for the NAME parameter is required.

Supply the correct parameter value and rerun the job.

Specify at least one of these parameters. Data integrity may be lost if the whole DIB block is reset. The DDIB operator command may be used to obtain information about the current contents of the DIB.

Supply the correct parameter value and rerun the job.

One of the following conditions exists:

• Field name is missing;

• Field name not found in FDT;

• Field is a group, subdescriptor.....;

• Field has FI option.

Supply the correct parameter value and rerun the job.

The only valid values for the parameter listed in the message are YES or NO.

Supply the correct parameter value and rerun the job.

At least one valid operator command must be supplied.

Supply a valid operator command and rerun the job.

ASSOSIZE and/or DATASIZE cannot be specified in blocks.

Supply the correct parameter value in number of cylinders and rerun the job.

ASSOSIZE and/or DATASIZE cannot be specified in cylinders.

Supply the correct parameter value in number of blocks and rerun the job.

See the Adabas Utilities documentation for a description of data set numbers.

Supply the correct parameter value, and rerun the job.

The values for these parameters must be specified in blocks and must not be larger than 65,535.

Supply a correct parameter value and rerun the job.

The specific ADADBS function was not specified in the ADADBS job.

Specify the appropriate function parameter as described in the Adabas Utilities documentation, and rerun the ADADBS job.

Only "yes" or "no" are allowed as parameter values.

Supply the correct parameter value and rerun the job.

The values NO, LOCAL or hub are allowed.

Supply the correct parameter value and rerun the job.

An online database or file save is executing, or Adabas is still processing the last TRAN SUSPEND and TRAN RESUME function.

You ran the TRAN RESUME job, but the timer set by TRESUME (defaults to 120 seconds unless set in the JCL) had already expired. Once the timer expires, Adabas immediately begins to return to "normal status".

A TRAN SUSPEND is running. Either the timer must expire or a TRAN RESUME job must be successfully executed before another TRAN SUSPEND job can be started.

No TRAN SUSPEND job has been started.

Adabas is running in single-user mode. MODE=MULTI is required.

The ET-SYNC was not successful; the database cannot be quiesced.

Contact your Software AG technical support representative.

Replication with TARGET = DBID, NUCID, 0, or greater than 65535 is not allowed.

Supply the correct parameter value and rerun the job.

Specifying both NOKEY and KEY is not allowed.

Supply the correct parameter value and rerun the job.

Additional parameters are not allowed.

Supply the correct parameter value and rerun the job.

A replication key field must be defined as a descriptor.

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

The specified replication key field must exist.

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

REPLICATION ON was attempted for a file that is already replicated.

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

A REPLICATION MODIFY or REPLICATION OFF was attempted for a file that is not currently replicated.

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

A replicated file must exist on the database and may not be an Adabas system file or ciphered.

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

REPLICATION ACTIVATE was attempted for a file that already has replication activated.

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

Specifying both ACTIVATE and DEACTIVATE is not allowed.

Supply the correct parameter value and rerun the job.

The only valid values for DSBI are "ON" or "OFF".

Supply the correct parameter value and rerun the job.

ACTIVATE / DEACTIVATE may not be specified.

Supply the correct parameter value and rerun the job.

The ADADBS Event Replicator Server function is only valid for an Event Replicator database.

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

The destination listed in the message is not defined to the Event Replicator Server.

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

The subscription listed in the message is not defined to the Event Replicator Server.

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

The specified DBID is not defined to the Event Replicator Server.

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

The specified file for the specified DBID is not defined to the Event Replicator Server.

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

The Event Replicator Server detected the destination listed in the message was already active or inactive.

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

The Event Replicator Server detected the specified file for the specified DBID was already active or inactive.

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

The Event Replicator Server detected the subscription listed in the message was already active or inactive.

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

DBIDs greater than 65535 are not allowed.

Supply the correct parameter value and rerun the job.

ADADBS detected that the Event Replicator Server could not CLOSE or OPEN the destination listed in the message.

Investigate the cause of the error. The Event Replicator Server job log will provide more details on why the request failed.

The input queue (IQUEUE) listed in the message is not defined to the Event Replicator Server.

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

ADADBS detected that the Event Replicator Server could not CLOSE or OPEN the input queue (IQUEUE) listed in the message.

Investigate the cause of the error. The Event Replicator Server job log will provide more details on why the request failed.

Either DESTINATION or IQUEUE must be specified for the OPEN and CLOSE functions.

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

An attempt was made to activate the destination named in the message (dest-name) while transactions for the destination still exist on the SLOG system file from the last time it was activated.

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

An attempt was made to activate a DBID/file combination that was deactivated because the SLOG system file was full.

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

The mandatory operand, FILE, was not specified with the MUPEX or RECORDSPANNING function.

Supply the correct parameter value and rerun the job. For more information, read about the MUPEX and RECORDSPANNING functions of the ADADBS utility in your Adabas utilities documentation.

A value other than "1" or "2" was specified for the MUPECOUNT parameter in an ADADBS MUPEX function run. The only valid values for MUPECOUNT are "1" or "2".

Supply the correct parameter value and rerun the job. For more information, read about the MUPEX function of the ADADBS utility in your Adabas utilities documentation.

To set the MUPECOUNT parameter to "1", the file must either be empty or have no PE fields. To set the MUPECOUNT to "2", the file cannot contain a PE field that is part of a DE field unless the file is empty.

Supply the correct parameter value or release the descriptors and rerun the job. For more information, read about the MUPEX function of the ADADBS utility in your Adabas utilities documentation.

One of the following circumstances occurred:

• The file specified is a system file.

• The file specified is a coupled file.

• The file specified is an ADAM file.

• The file specified is a replicated file.

• Only privileged commands are permitted against this file.

• The file specified is in load status.

• MIXDSDEV is not permitted for spanned data storage files.

Correct the file or parameters and rerun the ADADBS job.

The RECORDSPANNING or SPANCOUNT functions's time limit (set by the TIMELIMIT parameter) was exceeded.

Change the TIMELIMIT parameter value and rerun the job. For more information, read about the RECORDSPANNING and SPANCOUNT functions of the ADADBS utility in your Adabas utilities documentation.

The MODE=OFF parameter of the RECORDSPANNING function cannot be specified for a file that already contains spanned data storage records.

Ensure that the specified file contains no spanned data storage records and then rerun the ADADBS job. For more information, read about the RECORDSPANNING function of the ADADBS utility in your Adabas utilities documentation.

An I/O error occurred executing the specified function

Research and correct the cause of the error and rerun the ADADBS job.

The file specified does not have spanned data storage records enabled.

Specify a file with spanned data storage records enabled and rerun the ADADBS job.

Replication may not be turned on for a file with spanned Data Storage records.

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

Input information to ADADBS is requiring that the Adabas database have REPLICATION=YES (replication must be active) specified in the parameters to accomplish the request. However, replication for the database is not active.

Examine the input to ADADBS for correctness. You may have to modify, stop, and restart the Adabas database to allow replication to be active.