ADADBS Utility Messages

#### Search Results

Search

# ADADBS Utility 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-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-182 | ERROR-183 | ERROR-184 | ERROR-186 | ERROR-187 | ERROR-188 | ERROR-189 | ERROR-190 | ERROR-191 | ERROR-194 | ERROR-195 | ERROR-196 | ERROR-197 | ERROR-198 | ERROR-199 | ERROR-200 | ERROR-201 | ERROR-202 | ERROR-203 | ERROR-204 | ERROR-205 | ERROR-206 | ERROR-207 | ERROR-208 | ERROR-209 | ERROR-210 | ERROR-211 | ERROR-212 | ERROR-213 | ERROR-214 | ERROR-215 | ERROR-216 | ERROR-217 | ERROR-218 | ERROR-219 | ERROR-220 | ERROR-221 | ERROR-222 | ERROR-223 | ERROR-224 | ERROR-225 | ERROR-226 | ERROR-229 | ERROR-230 | ERROR-231 | ERROR-232 | ERROR-233 | ERROR-234 | ERROR-235 | ERROR-236 | ERROR-237 | ERROR-238 | ERROR-239 | ERROR-240 | ERROR-241 | ERROR-242 | ERROR-243 | ERROR-245 | ERROR-246 | ERROR-247 | ERROR-248 | ERROR-249 | ERROR-250 | ERROR-251 | ERROR-252 | ERROR-253 | ERROR-254 | ERROR-255 | ERROR-257 | ERROR-258 | ERROR-259 | ERROR-260 | ERROR-261 | ERROR-262 | ERROR-263 | ERROR-264 | ERROR-265 | ERROR-266`

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 reuse of DS or ISNs.
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 the parameter LENGTH, OPTION, or FORMAT
Explanation | The following rules apply: P is the only acceptable value for FORMAT. 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 for the parameter listed in the message 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-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 data set number
Explanation | See the Adabas Utilities documentation for a description of data set 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.
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 value for SECUID
Explanation | An invalid value was specified for the SECUID operator command. Only values of ALLOW, REQUIRE or WARN are allowed.
Action | Supply the correct parameter value and rerun the 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 function is only valid for an Event Replicator Server.
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 input queue (IQUEUE) 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 input queue (IQUEUE) 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-182 | No file number given
Explanation | The mandatory operand, FILE, was not specified with the MUPEX or RECORDSPANNING function.
Action | 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.

ERROR-183 | Invalid MUPECOUNT option (1/2)
Explanation | 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".
Action | 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.

ERROR-184 | MUPECOUNT specification is invalid. The file contains a PE and has records.
Explanation | 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.
Action | 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.

ERROR-186 | Conflicting file options
Explanation | 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.
Action | Correct the file or parameters and rerun the ADADBS job.

ERROR-187 | TIMELIMIT exceeded
Explanation | The RECORDSPANNING or SPANCOUNT functions's time limit (set by the TIMELIMIT parameter) was exceeded.
Action | 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.

ERROR-188 | Invalid RECORDSPANNING request
Explanation | The MODE=OFF parameter of the RECORDSPANNING function cannot be specified for a file that already contains spanned data storage records.
Action | 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.

ERROR-189 | An I/O error occurred
Explanation | An I/O error occurred executing the specified function
Action | Research and correct the cause of the error and rerun the ADADBS job.

ERROR-190 | File specified is not spanned
Explanation | The file specified does not have spanned data storage records enabled.
Action | Specify a file with spanned data storage records enabled and rerun the ADADBS 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.

ERROR-194 | Replication not active for Adabas
Explanation | 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.
Action | Examine the input to ADADBS for correctness. You may have to modify, stop, and restart the Adabas database to allow replication to be active.

ERROR-195 | Anchor file must be specified
Explanation | A value for the ANCHOR parameter must be specified. To perform properly, the ADADBS EXPFILE utility needs to know the number of the anchor file of an expanded file chain.
Action | Supply a valid value for ANCHOR and rerun the job.

ERROR-196 | INSERT or REMOVE must be specified
Explanation | Either the INSERT or REMOVE parameter must be specified for the ADADBS EXPFILE utility function. They are mutually exclusive parameters.
Action | Supply either the INSERT or REMOVE parameter, as appropriate, and rerun the job.

ERROR-197 | Specified field is not a descriptor
Explanation | The field specified in the FIELD parameter was not a descriptor. When specifying the NOUQ option in an ADADBS CHANGE operation, the field must be a unique descriptor (DE,UQ option) field.
Action | Correct the parameter values for the ADADBS CHANGE operation and rerun it.

ERROR-198 | Specified descriptor is not unique
Explanation | The field specified in the FIELD parameter was not a unique descriptor. When specifying the NOUQ option in an ADADBS CHANGE operation, the field must be a unique descriptor (DE,UQ option) field.
Action | Correct the parameter values for the ADADBS CHANGE operation and rerun it.

ERROR-199 | Insufficient work space for Online Reorder
Explanation | The internal workarea is insufficient for the requested reorder.
Action | Contact your Software AG technical support representative for assistance.

ERROR-200 | Invalid function specified
Explanation | The nucleus did not recognize the call it received. An invalid function or value was specified.
Action | Correct the parameter values and utility function specifications as required and rerun the job.

ERROR-201 | Invalid function for current NnLOG
Explanation | An invalid value was specified for the current NCLOG or NPLOG specifications. Running the ADADBS ADDCLOG, ADDPLOG, DELCLOG, or DELPLOG utility functions is invalid when running with dual CLOGs or PLOGs.
Action | Make sure the Adabas nucleus startup job specifies the NCLOG and NPLOG ADARUN parameters and that it is not using dual CLOGs and PLOGs. Then verify that the settings of the NCLOG and NPLOG ADARUN parameters are set to integers in the range 2 through 8 (inclusive). Correct any invalid parameters and rerun the job.

ERROR-202 | ENQ for PPT failed
Explanation | An error occurred during the PPT enqueue process.
Action | Contact your Software AG technical support representative for assistance.

ERROR-203 | No PPT entries found
Explanation | No entries were found in the current PPT.
Action | Obtain an PPTPRINT and contact your Software AG technical support representative for assistance.

ERROR-204 | PPT not consistent or invalid request
Explanation | The entry Adabas is trying to locate in the PPT was not found.
Action | Check the current PPT structure and make sure the requested function was valid and that the correct data set was specified for the ADADBS run. make appropriate corrections and rerun the job.

ERROR-205 | Error with DDnLOGRx data set
Explanation | An error occurred during an attempt to process the specified CLOG or PLOG data set in the Adabas startup JCL.
Action | Check your startup JCL, make appropriate corrections, and retry the function.

ERROR-206 | Dataset name length error
Explanation | The nucleus detected an invalid length in the parameter passed to it.
Action | Contact your Software AG technical support representative for assistance.

ERROR-207 | Dataset already in use
Explanation | The CLOG or PLOG data set that was requested in the ADADBS run to be added or deleted is already in use.
Action | Specify a CLOG or PLOG data that is not in use and retry the function.

ERROR-208 | xLOG data set must be supplied
Explanation | The CLOG or PLOG data set to be added or deleted using the ADADBS function must be specified in the Adabas startup JCL.
Action | Correct the startup JCL, restart Adabas, and retry the function.

ERROR-209 | SLOG file can only be {deleted|refreshed} with RPLPARMS=NONE
Explanation | The Event Replicator Server SLOG file can only be deleted or refreshed when the Event Replicator Server is started with the ADARUN parameter RPLPARMS set to "NONE."
Action | Restart the Event Replicator Server with RPLPARMS=NONE.

ERROR-210 | Replicator file can only be {deleted|refreshed} when RPLPARMS is set to NONE or PARMS
Explanation | The Event Replicator Service Replicator system file can only be deleted or refreshed when the Event Replicator Server is started with the ADARUN parameter RPLPARMS set to "NONE" or "PARMS".
Action | Restart the Event Replicator Server with RPLPARMS=NONE or RPLPARMS=PARMS.

ERROR-211 | NUCID must be supplied
Explanation | No nucleus ID was specified during an attempt to run the ADADBS utility function to dynamically add or delete a CLOG or PLOG data set in a cluster environment. The NUCID parameter is required in a cluster environment.
Action | Specify the nucleus ID where you are trying to add or delete the CLOG or PLOG data set using the NUCID parameter and try again.

ERROR-212 | DDnPLOGRx must be copied. Then retry function.
Explanation | The PLOG data set identified in the message (DDn PLOGRx) has not been copied.
Action | Copy or format the specified data set and retry the function.

ERROR-213 | Invalid record buffer length
Explanation | The record buffer length is invalid.
Action | Contact your Software AG technical support representative for assistance.

ERROR-214 | Missing or too many fields in FIELDLIST
Explanation | The FIELDLIST parameter is missing or contains more than 800 fields.
Action | Investigate the cause of the error. Either supply a FIELDLIST parameter or reduce the number of fields listed on the FIELDLIST parameter. Then rerun the job.

ERROR-215 | Field does not exist in the FDT
Explanation | The FIELDLIST parameter contains a field that does not exist in the FDT for the file.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-216 | Field is a descriptor
Explanation | The FIELDLIST parameter contains a descriptor field. Descriptor fields cannot be deleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-217 | Field is a parent of a Sub-, Super-, Hyper-, Phonetic, or Collating descriptor
Explanation | The FIELDLIST parameter contains a subdescriptor, superdescriptor, hyperdescriptor, phonetic descriptor, or collating descriptor field. These types of fields cannot be deleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-218 | Additions 1 field setting is invalid
Explanation | The Additions 1 field for an Adabas command contains an invalid value.
Action | Contact your Software AG technical support representative for assistance.

ERROR-219 | Duplicate fieldname detected in FIELDLIST
Explanation | The FIELDLIST parameter contains a duplicate field; a field is listed more than once.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-220 | Function not allowed for LOB file
Explanation | The file specified in the FILE parameter is a large object (LOB) file. You cannot delete fields from a LOB file.
Action | Correct the FILE parameter specification and then rerun the job.

ERROR-221 | Field is parent of Subfield or Superfield
Explanation | The FIELDLIST parameter contains a subfield or superfield. These types of fields cannot be deleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-222 | Trying to delete a field already deleted
Explanation | The FIELDLIST parameter in an ADADBS DELFN run includes a field that was already deleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-223 | Trying to undelete a non-deleted field
Explanation | The FIELDLIST parameter in an ADADBS UNDELFN run includes a field that has not been deleted, so it cannot be undeleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-224 | File is security protected
Explanation | The file specified in the FILE parameter is security protected, but no value was specified for the PASSWORD parameter.
Action | Supply a valid password in the PASSWORD parameter and try again.

ERROR-225 | Invalid FDT detected
Explanation | The FDT for the file specified in the FILE parameter is invalid.
Action | Contact your Software AG technical support representative for assistance.

ERROR-226 | Trying to delete a field that has the NN option on
Explanation | The FIELDLIST parameter contains a field that has the NN option on. Fields with the NN option on cannot be deleted.
Action | Correct the FIELDLIST parameter specification and then rerun the job.

ERROR-229 | ddname could not be opened ior-rsp - reason Sub-code = subcode
Explanation | The data set identified by the DD name (ddname) given in the message could not be opened during a dynamic add or increase attempt. Possible causes include a misspelling or a JCL error. The ADAIOR response code (ior-rsp), the error text (reason) associated with the response code, and the system error code (subcode) are given in the message. The system error code, if nonzero, should be reported if you contact Software AG technical support about this error.
Action | Investigate the cause of the error. Correct it and rerun the job. If you need additional assistance, contact your Software AG technical support representative; be sure to provide the reason and system error code.

ERROR-230 | ddname I/O error reading RABN rabn ior-rsp – reason * The dataset is not formatted or * The dataset has not yet been increased or * The newly increased area is not formatted.
Explanation | During a dynamic database add or increase attempt, an error occurred reading the data set identified by the DD name (ddname) given in the message. Possible causes include an unformatted data set, a data set that has not yet been increased, or a newly increased data set area that has not been formatted. The RABN (rabn) that ADADBS tried, but failed to read, the ADAIOR response code (ior-rsp) and explanation (reason) are given in the message.
Action | Investigate the cause of the error. Correct it and rerun the job. If you need additional assistance, contact your Software AG technical support representative; be sure to provide the reason.

ERROR-231 | RPLCHECK issued to a non-Reptor Adabas
Explanation | The RPLCHECK operator command was issued in an ADADBS OPERCOM utility run against a database that was not an Event Replicator Server. The RPLCHECK command can only be issued against Event Replicator Servers.
Action | Verify that this is the command you want to run. If it is, verify that you are running it against an Event Replicator Server.

ERROR-232 | Command invalid for non-cluster Adabas
Explanation | The operator command was issued in an ADADBS OPERCOM utility run against a database that was not running as a cluster nucleus (CLUSTER=SYSPLEX or CLUSTER=LOCAL). The command can only be issued against a cluster nucleus.
Action | Verify that this is the command you want to run. If it is, verify that you are running it against a cluster nucleus.

ERROR-233 | Invalid value for parameter MXCANCEL
Explanation | The value specified for the MXCANCEL parameter is invalid. MXCANCEL values must be greater than or equal to 15.
Action | Supply the correct parameter value and rerun the job.

ERROR-234 | Invalid value for parameter MXCANCELWARN
Explanation | The value specified for the MXCANCELWARN parameter is invalid. MXCANCELWARN values must either be zero (0) or a value greater than or equal to 4 and less than the value of the MXCANCEL parameter.
Action | Supply the correct parameter value and rerun the job.

ERROR-235 | Invalid value for parameter MXMSG
Explanation | The value specified for the MXMSG parameter is invalid. MXMSG values must be greater than or equal to 15 and less than or equal to 32767.
Action | Supply the correct parameter value and rerun the job.

ERROR-236 | Invalid value for parameter MXMSGWARN
Explanation | The value specified for the MXMSGWARN parameter is invalid. MXMSGWARN values must either be zero (0) or a value greater than or equal to 4 and less than the value of the MXMSG parameter.
Action | Supply the correct parameter value and rerun the job.

ERROR-237 | Invalid value for parameter MXSTATUS
Explanation | The value specified for the MXSTATUS parameter is invalid. MXSTATUS values must either be zero (0) or a value that is greater than or equal to 15.
Action | Supply the correct parameter value and rerun the job.

ERROR-238 | Invalid value for parameter MXWTOR
Explanation | The value specified for the MXWTOR parameter is invalid. MXWTOR values must either be zero (0) or a value greater than or equal to 15 and less than or equal to 64800.
Action | Supply the correct parameter value and rerun the job.

ERROR-239 | File nnnn is greater than the MAXFILES defined for the database
Explanation | The file number specified is invalid. The file number must be less than the MAXFILES defined for the database.
Action | Supply the correct parameter value and rerun the job.

ERROR-240 | Invalid file range specified
Explanation | The file range is invalid, for example the starting value is less than the ending value.
Action | Correct the file range and rerun the job.

ERROR-241 | Duplicate keyword parameter or missing, “CHANGE'' function request
Explanation | Invalid parameters were provided to the ADADBS CHANGE function.
Action | Supply the correct parameter values and rerun the job.

ERROR-242 | Invalid FILE number specified for auditing
Explanation | The ADADBS AUDITING function is only valid for files participating in auditing (are included in an ADAANP FILE group).
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-243 | The specified FILE was already active|inactive
Explanation | The database detected the file identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-245 | AUDITSERVER function only allowed for use with the Audit Server
Explanation | The ADADBS AUDITSERVER function is only valid for an Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-246 | The specified destination destination was not found
Explanation | The destination identified in the message is not defined to the Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-247 | The specified subscription subscription was not found
Explanation | The subscription identified in the message is not defined to the Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-248 | The specified destination destination was already active|inactive
Explanation | The Audit Server detected the destination identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-249 | The specified subscription subscription was already active|inactive
Explanation | The Audit Server detected the subscription identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-250 | Missing parameter: DESTINATION required
Explanation | ADADBS detected that the required parameter `DESTINATION` was missing.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-251 | Missing parameter: DESTINATION or SUBSCRIPTION required
Explanation | ADADBS detected that the required parameter `DESTINATION` or `SUBSCRIPTION` was missing.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-252 | SUBSCRIPTION parameter not allowed for OPEN or CLOSE: only DESTINATION
Explanation | ADADBS detected invalid parameter SUBSCRIPTION with OPEN or CLOSE.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-253 | The specified subscription subscription was not activated|deactivated
Explanation | The Audit Server detected an unexpected response code from an attempt to activate or deactivate the subscription identified in the message.
Action | Investigate the cause of the error. Correct it and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative.

ERROR-254 | Auditing not active for Adabas
Explanation | The database is not an auditing database (`ADARUN AUDITING=YES`).
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-255 | NUCID specified for a non-cluster Adabas DBID
Explanation | The `NUCID=` parameter was specified for a non-cluster Adabas database.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-257 | {CLOSE | OPEN} failed for specified destination destination
Explanation | ADADBS detected that the Audit Server could not CLOSE or OPEN the destination identified in the message.
Action | Investigate the cause of the error. The Audit Server job log will provide more details on why the request failed.

ERROR-258 | The specified destination destination cannot be activated.Data still exists on the SLOG system file for this inactive destination.
Explanation | An attempt was made to activate the destination identified in the message while items for the destination still exist on the SLOG system file from the last time it was active.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-259 | The specified destination destination was already open|closed
Explanation | The Audit Server detected the destination identified in the message was already open or closed for all tasks.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-260 | The specified destination destination was not activated|deactivated
Explanation | The Audit Server detected an unexpected response code from an attempt to activate or deactivate the destination identified in the message.
Action | Investigate the cause of the error. Correct it and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative.

ERROR-261 | 'In-parallel' option not allowed for the specified function
Explanation | Specifying INPARALLEL=YES is not valid for the given function.
Action | Remove the INPARALLEL=YES parameter.

ERROR-262 | Invalid value for AUDITLOG Only the value 'CONSOLE' is allowed.
Explanation | Invalid parameter specified. Only the value "CONSOLE" is allowed.
Action | Supply the correct parameter values and rerun the job.

ERROR-263 | FEOFAL applies to an Audit Server only
Explanation | The ADADBS OPERCOM FEOFAL can only be applied to an Adabas Audit Server.
Action | Ensure the target of the FEOFAL command is an Adabas Audit Server.

ERROR-264 | FEOFCL does not apply to an Audit Server
Explanation | The ADADBS OPERCOM FEOFCL cannot be applied to an Adabas Audit Server.
Action | Ensure the target of the FEOFCL command is not an Adabas Audit Server. For Adabas Audit Servers, use the FEOFAL command.

ERROR-265 | Invalid value for parameter AUDCONNECT
Explanation | Only valid DBIDs, auditing server IDs, or ALL are allowed.
Action | Supply the correct parameter value and rerun the job.

ERROR-266 | Function not permitted for cluster nucleus/Replicator/Audit Server
Explanation | The specified command is not permitted for cluster nuclei, Replicators, or Audit Servers.
Action | Verify this is the command you want to run. If so, verify that is not running against one of the above database types.