Version 7.4.4
 —  Messages and Codes  —

ADADBS Error Messages

Overview of Messages

ERROR-114 | ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | 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-140 | ERROR-141 | 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-154 | 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-172 | ERROR-173 | ERROR-174 | ERROR-175 | ERROR-176 | ERROR-178 | ERROR-179 | ERROR-191

ERROR-114 INVALID VALUE FOR PARAMETER ASSOPFAC OR DATAPFAC
Explanation:

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

Action:

Correct the parameter value and rerun the job.


ERROR-121 INVALID ENCODING VALUE (1-4095)
Explanation:

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

Action:

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


ERROR-122 INVALID FILE NUMBER SPECIFICATION
Explanation:

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

Action:

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


ERROR-123 INVALID VALUE FOR THE PARAMETER MODE
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-124 INVALID VALUE FOR THE PARAMETER PRTY
Explanation:

A valid value is in the range 1 through 255.


ERROR-125 INVALID VALUE FOR THE PARAMETER ASSOSIZE/DATASIZE
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-126 INVALID VALUE FOR A SIZE PARAMETER
Explanation:

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

Action:

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


ERROR-127 INVALID VALUE FOR PARAMETER LENGTH, OPTION, OR FORMAT
Explanation:

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.

Action:

Supply the correct parameter value and rerun the job.


ERROR-128 INVALID VALUE FOR THE PARAMETER TODATE
Explanation:

The parameter TODATE must be specified in the format:

TODATE=YYYYMMDD

Action:

Supply the correct parameter value and rerun the job.


ERROR-129 MANDATORY PARAMETER USER ID MISSING
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-130 INVALID VALUE FOR THE PARAMETER DESCRIPTOR
Explanation:

The value is one of the following:

  • missing;

  • not found in the FDT; or

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-131 INVALID VALUE FOR THE PARAMETER NAME
Explanation:

A valid value for the NAME parameter is required.

Action:

Supply the correct parameter value and rerun the job.


ERROR-132 JOBNAME OR IDENT PARAMETER MISSING
Explanation:

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.

Action:

Supply the correct parameter value and rerun the job.


ERROR-133 INVALID OR MISSING FIELD NAME
Explanation:

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.

Action:

Supply the correct parameter value and rerun the job.


ERROR-134 INVALID VALUE FOR THE PARAMETER parameter
Explanation:

The only valid values are yes or no.

Action:

Supply the correct parameter value and rerun the job.


ERROR-135 MISSING PARAMETER FOR OPERCOM FUNCTION
Explanation:

At least one valid operator command must be supplied.

Action:

Supply a valid operator command and rerun the job.


ERROR-136 INVALID VALUE FOR THE PARAMETER AALT/DALT
Explanation:

One of the parameters AALT or DALT is mandatory. You cannot use both.

Action:

Supply one of the parameter values, and rerun the job.


ERROR-137 SIZE MUST BE SPECIFIED IN CYLINDERS
Explanation:

ASSOSIZE and/or DATASIZE cannot be specified in blocks.

Action:

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


ERROR-138 SIZE MUST BE SPECIFIED IN BLOCKS
Explanation:

ASSOSIZE and/or DATASIZE cannot be specified in cylinders.

Action:

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


ERROR-139 INVALID DATASET NUMBER
Explanation:

See the Adabas Utilities documentation for a description of dataset numbers.

Action:

Supply the correct parameter value, and rerun the job.


ERROR-140 INVALID VALUE FOR MAXDS, MAXNI OR MAXUI
Explanation:

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

Action:

Supply a correct parameter value and rerun the job.


ERROR-141 MISSING FUNCTION PARAMETER
Explanation:

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

Action:

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


ERROR-142 INVALID RABN RANGE FOR NEWALTS
Explanation:

The range must specify RABNs within a single existing extent defined in the general control block (GCB). Refer to the report list provided by the ADAREP utility.

Action:

Respecify the range value correctly, and rerun the ADADBS job.


ERROR-143 INVALID VALUE FOR PGMREFRESH
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-144 INVALID VALUE FOR PARAMETER REVIEW
Explanation

The values NO, LOCAL or hub are allowed.

Action

Supply the correct parameter value and rerun the job.


ERROR-145 INVALID ADABAS STATE FOR "TRAN SUSPEND/RESUME"
Explanation:

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


ERROR-146 TRESUME TIMER EXPIRED BEFORE RESUME OCCURRED
Explanation:

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


ERROR-147 "TRAN SUSPEND" ALREADY IN PROGRESS
Explanation:

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.


ERROR-148 NO PREVIOUS "TRAN SUSPEND" TO RESUME
Explanation:

No TRAN SUSPEND job has been started.


ERROR-149 INVALID WHEN ADABAS IS "MODE=SINGLE"
Explanation:

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


ERROR-150 ET-SYNC FAILED
Explanation:

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

Action:

Contact your Software AG technical support representative.


ERROR-151 TARGET is invalid.
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-152 Parameters NOKEY and KEY are mutually exclusive.
Explanation:

Specifying both NOKEY and KEY is not allowed.

Action:

Supply the correct parameter value and rerun the job.


ERROR-153 Conflicting parameter for replication OFF.
Explanation:

Additional parameters are not allowed.

Action:

Supply the correct parameter value and rerun the job.


ERROR-154 Invalid KEY for replication. The specified KEY field <field> is not defined as a descriptor on the file to be replicated.
Explanation:

A replication key field must be defined as a descriptor.

Action:

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


ERROR-155 Invalid KEY for replication. The specified KEY field <field> does not exist on the file to be replicated.
Explanation:

The specified replication key field must exist.

Action:

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


ERROR-156 Invalid replication request.
Explanation:

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

Action:

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


ERROR-157 Invalid replication request.
Explanation:

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

Action:

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


ERROR-158 Invalid FILE for replication.
Explanation:

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

Action:

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


ERROR-159 Invalid replication request.
Explanation:

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

Action:

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


ERROR-160 Parameters ACTIVATE and DEACTIVATE are mutually exclusive.
Explanation:

Specifying both ACTIVATE and DEACTIVATE is not allowed.

Action:

Supply the correct parameter value and rerun the job.


ERROR-161 Invalid value for parameter DSBI.
Explanation:

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

Action:

Supply the correct parameter value and rerun the job.


ERROR-162 Conflicting parameter for replication ON.
Explanation:

ACTIVATE / DEACTIVATE may not be specified.

Action:

Supply the correct parameter value and rerun the job.


ERROR-163 Event Replicator Server function only allowed for Event Replicator database
Explanation:

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

Action:

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


ERROR-164 The specified destination destination was not found.
Explanation:

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

Action:

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


ERROR-165 The specified subscription subscription was not found.
Explanation:

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

Action:

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


ERROR-166 The specified DBID was not found.
Explanation:

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

Action:

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


ERROR-167 The specified FILE/DBID was not found.
Explanation:

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

Action:

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


ERROR-168 The specified destination destination was already active|inactive.
Explanation:

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

Action:

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


ERROR-169 The specified FILE/DBID was already active|inactive.
Explanation:

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

Action:

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


ERROR-170 The specified subscription subscription was already active|inactive.
Explanation:

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

Action:

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


ERROR-172 Invalid value for DBID.
Explanation:

DBIDs greater than 65535 are not allowed.

Action:

Supply the correct parameter value and rerun the job.


ERROR-173 {CLOSE | OPEN} failed for specified destination destination-name
Explanation:

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

Action:

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


ERROR-174 The specified input queue queue-name was not found.
Explanation:

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

Action:

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


ERROR-175 {CLOSE | OPEN} failed for specified input queue queue-name
Explanation:

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

Action:

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


ERROR-176 Missing parameter: DESTINATION or IQUEUE required
Explanation:

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

Action:

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


ERROR-178 The specified destination dest-name may not be active
Data still exists on the SLOG system file for this inactive destination
Explanation:

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.

Action:

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


ERROR-179 The specified DBID/file may not be activated
The SLOG has been suspended for database-related input transactions and one or more transactions exist on the SLOG system file for this inactive DBID/file
Explanation:

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

Action:

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


ERROR-191 Replication may not be turned on for a file with spanned data storage records.
Explanation:

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

Action:

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.


Top of page