Version 8.2.5
 —  Messages and Codes  —

ADARES Utility Error and Warning Messages

This document describes general and warning ADARES messages.


Top of page

ADARES Errors (ERROR-121 - ERROR-172)

Overview of Messages

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-171 | ERROR-172
ERROR-121 Protection log number mismatch
Explanation

The protection log number specified by the PLOGNUM/FROMPLOG parameter could not be found on the input log tape.

Action

Supply a correct protection log data set and rerun the job.


ERROR-122 FROMCP/FROMBLK not found
Explanation

The start checkpoint/block number specified in the FROMCP/ FROMBLK parameter could not be found on the protection log number "log-number" (the actual log number is shown in the message text).

Action

Supply the correct parameter value and rerun the job.


ERROR-123 Ending block number not found
Explanation

The block number specified in the TOBLK parameter could not be found on the protection log input.

Action

Supply the correct parameter value and rerun the job.


ERROR-124 Invalid log number specification
Explanation

The nucleus is not able to obtain the number of the last block written to the sequential protection log data set for the requested session session-id.

Action

Contact your Software AG technical support representative.


ERROR-125 Dual log modified during copy run
Explanation

User exit 2 of the nucleus is

  • used: the copy run was started twice using the exit; or

  • not used: the nucleus started writing to the part of the dual log being copied before the copy run finished.

Action

Save the ADARES output and contact your Software AG technical support representative.


ERROR-126 Invalid FROMBLK/FROMCP/TOBLK/TOCP values
Explanation

Missing or invalid FROMCP or TOCP specification.

Action

See the Adabas Utilities documentation for further information.


ERROR-127 Database ID mismatch
Explanation

The ADARUN DBID is "dbid-a", but the DDSIIN input data set contains data for DBID "dbid-b", on block "block-number", "session-id". Either the wrong database is accessed, or the utility input parameter specifies a wrong database ID.

Action

Correct the error and rerun the job.


ERROR-128 Inconsistent file list
Explanation

File "file-number" is either a coupled file or part of an expanded file; however, not all corresponding files have been included in the file list.

Action

Supply a correct file list, or specify the IGNORECOUPLE/IGNOREEXP parameters, then rerun the ADARES job.


ERROR-129 Empty PLOG data set for backout
Explanation

PLOGR1/R2 are empty. Backout from disk is not possible.

Action

Save the ADARES output and contact your Software AG technical support representative.


ERROR-130 PLOG data set not yet copied
Explanation

An attempt was made to read from data set (name), but this data set has not been copied.

Action

Run the ADARES function PLCOPY first to save the contents of the dual or multiple protection log data set, then rerun this job.


ERROR-131 TOCP/TOBLK not found on dual protection log
Explanation

The requested checkpoint for backout DPLOG is not on the data set (name).

Action

Supply a correct protection log and rerun the job.


ERROR-132 Invalid value for the parameter 'DSRABN'
Explanation

One of the following is required:

  • a single RABN; or

  • an ascending range of RABNs.

Action

Supply the correct parameter value and rerun the job.


ERROR-133 Conflicting FROMPLOG/TOPLOG parameters
Explanation

For the REGENERATE function, the value for TOPLOG must not be less than the value specified for FROMPLOG. For the BACKOUT function, the inverse must be true: the FROMPLOG value must not be less than the TOPLOG value.

Action

Supply a correct parameter value and rerun the ADARES job.


ERROR-134 Protection log number mismatch
Explanation

The protection log data sets are not supplied in the correct order: the current protection log number has number (log-number-a); the previous had number (log-number-b).

Action

Supply the correct sequence of protection logs and rerun the job.


ERROR-135 TOBLK/TOCP not found on sequential protection log
Explanation

The specified TOBLK does not contain the TOCP. The input has been processed, including the block specified by TOBLK.

Action

Supply the correct parameter value and rerun the ADARES job.


ERROR-136 Invalid block number found
Explanation

The blocks of the current PLOG are not supplied in the correct order, or the first block of a PLOG does not have number 1. The block just read has number (block-number) on protection log number (log-number). The displayed message text contains actual block and log numbers.

Action

Supply the correct sequence of protection logs and rerun the job.


ERROR-137 Missing function parameter
Explanation

The ADARES statement did not specify an ADARES function.

Action

Supply an ADARES function (BACKOUT, CLCOPY, COPY, MERGE, PLCOPY, REGENERATE, REPAIR) and rerun the ADARES job.


ERROR-138 DBID mismatch
Explanation

On PLOG number (log-number), block number (block-number), DBID (dbid-a) was found, but the PLOG DBID parameter value is (dbid-b).

Action

Supply the correct PLOG tapes and rerun the ADARES job.


ERROR-139 DDSIIN input error
Explanation

Sessions to be copied include both PLOG and SAVE sessions.

Action

Supply the correct input tapes and rerun the ADARES job.


ERROR-140 DDSIIN input error
Explanation

Timestamps are not ascending in session number "session-id". The block in error has number (block-number).

Action

Supply the correct input tapes and rerun the ADARES job.


ERROR-141 Parameter parameter not allowed in MODE=SINGLE
Explanation

The parameter parameter cannot be specified in single-user mode.

Action

Rerun the job with the ADARUN parameter MODE=MULTI.


ERROR-142 Parameter parameter not allowed without DSF
Explanation

The parameter is only available when the Delta Save Facility is installed.

System Action:

ADARES terminates abnormally.

Action

If the Delta Save Facility is installed, specify ADARUN DSF=YES and rerun the job.


ERROR-143 Error during DSIM data set processing
Explanation

An error occurred while the Delta Save Facility was processing (building) the delta save images (DSIM) data set. The DSIM data set has not been built correctly. The reason for the error is indicated by a preceding Delta Save error message. This ADARES error message is only issued if the COPY function is executed without a sequential output data set.

System Action:

ADARES terminates abnormally.

Action

Determine and eliminate the cause of the error; then rerun the job.


ERROR-144 Parameter AUTOBACKOUT not allowed
Explanation

The AUTOBACKOUT parameter is allowed only when the TOCP parameter value is also specified.

Action

Correct the input parameter specifications, then rerun the ADARES job.


ERROR-145 Invalid EXCLUDE parameter
Explanation

The file number provided in the message either has not been specified at all for REGENERATE/BACKOUT, or has been specified twice in the EXCLUDE parameter.

Action

Correct the error and rerun the job.


ERROR-146 File excluded from REGENERATE
Explanation

The REGENERATE function excluded one or more files from the regeneration. Possible causes:

  • The nucleus returned a response code for the file.

  • ADARES encountered a utility checkpoint on the PLOG that pertained to the file, indicating a problem with the setup of the job (for example, wrong RAID parameter; wrong PLOG).

If a file is excluded from regeneration in a job built by the Adabas Recovery Aid, an internal error is indicated.

Action

Determine the cause of the error and correct the job. If necessary, contact your technical support representative for help restarting the recovery process.


ERROR-147 Invalid value for parameter 'ALLOCATION'
Explanation

Valid values are ALLOCATION={FORCE | NOFORCE}.

Action

Supply the correct parameter value and rerun the job.


ERROR-148 Nucleus 'NU' parameter value too small
Explanation

Currently, more than `NU' number of users have open transactions.

Action

Increase the nucleus `NU' value and rerun the job.


ERROR-149 Missing or mismatching RLOGDEV parameter
Explanation

The specified or implied RLOGDEV parameter does not match the RLOG device type stored in the GCBs.

RLOGDEV parameter = device type
RLOG device type = device type

The RLOGDEV parameter must be correct so that ADARES COPY/PLCOPY executions can be recorded in the recovery log even if the GCBs have been damaged.

Action

Supply the correct parameter value and rerun the job.


ERROR-150 Error occurred during CLCOPY, PLCOPY, or PPT DEQ
Explanation

An error occurred while dequeuing multiple protection or command logs during the copy process in a nucleus cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-151 Error occurred during CLCOPY, PLCOPY, or PPT ENQ
Explanation

An error occurred while enqueuing multiple protection or command logs during the copy process in a nucleus cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-152 ADARES BACKOUT DPLOG not allowed for a cluster database.
Explanation

The ADARES function BACKOUT DPLOG may not be used for an Adabas cluster database. ADARES BACKOUT may be used, but a merged protection log is required as input.

Action

Use the PLCOPY function to merge the protection logs and supply the sequential data set.


ERROR-153 Invalid NUMLOG parameter specified
The value specified was nn
Explanation

When manually merging command logs in an Adabas cluster environment, the NUMLOG parameter maximum number is 32.

Action

Specify the correct number of cluster command logs to be merged.


ERROR-154 {OPEN | CLOSE} error on {MERGIN1 | MERGIN2} file
Explanation

An error occurred while opening or closing the intermediate data set supplied for the protection or command log merge process in an Adabas cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-155 Read error on {MERGIN1 | MERGIN2} file. System error=nnnnnnnn
Explanation

An error occurred while reading the intermediate data set supplied for the protection or command log merge process in an Adabas cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-156 Write error {MERGIN1 | MERGIN2} file. System error=nnnnnnnn
Explanation

An error occurred while writing to the intermediate data set supplied for the protection or command log merge process in an Adabas cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-157 Incorrect {MERGIN1 | MERGIN2} file supplied
Explanation

An incorrect intermediate data set was supplied for the protection or command log merge process in an Adabas cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-158 Inconsistency detected with header flag partial merge indicator is not set correctly
Explanation

During the protection or command log merge process in an Adabas cluster environment, an inconsistent indicator was detected for the merge status of a log.

Action

Contact your Software AG technical support representative.


ERROR-159 Invalid {READ | WRITE} container function requested for merge process
Explanation

An error occurred when attempting a read or write to the PLOG or CLOG data set.

Action

Contact your Software AG technical support representative.


ERROR-160 Internal processing error encountered with the merge process - subcode n
Explanation

An internal protection or command log processing error was detected with one of the following subcodes:

1 An attempt was made to open a log multiple times.
2 The log I/O table is full.
3 An error occurred reading the PLOGR1 or CLOGR1 data set in the parallel participant table (PPT).
4 An error occurred reading the PLOGR2 or CLOGR2 data set in the parallel participant table (PPT).
5 Neither log was selected for the merge process.
6 An error occurred in the log buffering.
7 The log buffer flag is incorrect.
8 An internal error occurred while processing log records. An attempt was made to read past end-of-file.
9 An internal error occurred while attempting to update the log status at the end of the merge process.
Action

Contact your Software AG technical support representative.


ERROR-161 Invalid PPT detected
Explanation

An invalid parallel participant table (PPT) was detected in an Adabas cluster environment.

Action

Contact your Software AG technical support representative.


ERROR-162 The PLOG merge process encountered an invalid protection record
Explanation

An error occurred while processing a protection record.

Action

Save the ADARES output and contact your Software AG technical support representative.


ERROR-163 The PLOG merge detected an internal error writing the merged records
Explanation

The block numbers are not increasing sequentially.

Action

Save the ADARES output and contact your Software AG technical support representative.


ERROR-164 The intermediate data set did not contain as many records as expected
Explanation

The input contains xxx number of records but yyy number of records were expected.

Action

Supply the correct intermediate data sets.


ERROR-165 The JCL supplied for the ADARES PLCOPY NOPPT produced an error
Explanation

ADARES detected that either no DD statements were provided or the DD statement was in error for the PLCOPY NOPPT function.

Action

Correct the JCL and resubmit the job.


ERROR-166 Invalid input was supplied to the MERGE CLOG function
Explanation

One or more of the data sets supplied to the ADARES MERGE CLOG function was in error. The input is expected to be sequential data sets and CLOGLAYOUT=5 must have been used to create the original CLOG.

Action

Correct the input and resubmit the MERGE CLOG job.


ERROR-167 The JCL supplied for the ADARES MERGE CLOG function produced an error
Explanation

ADARES detected that either no DD statements were provided or the DD statement was in error for the MERGE CLOG function.

Action

Correct the JCL and resubmit the job.


ERROR-168 The NUMLOG parameter specified was xx but yy data sets were supplied
Explanation

The ADARES MERGE CLOG function parameter NUMLOG specified a different number of data sets (xx) from the number that were actually supplied as input to the function (yy).

Action

Change the NUMLOG parameter specification or change the input data sets specified so that the two values (xx and yy) match. Then resubmit the job.


ERROR-169 An empty data set was supplied as input to the MERGE CLOG function
Explanation

ADARES detected an empty input data set.

Action

Remove the data set and adjust the NUMLOG value; or supply a valid data set. Then resubmit the job.


ERROR-170 Parameter SBLKNUM is only allowed if NOPPT
Explanation

The SBLKNUM parameter is only allowed in conjunction with the NOPPT parameter.


ERROR-171 The PPT is required for a PLCOPY from a cluster database. This is not possible because the open of the ASSO failed. Please rerun PLCOPY with NOPPT specified and the PLOG DD-statements supplied in the JCL.
Explanation

Prior to ERROR-171, the following should be seen: "The Associator data set(s) could not be opened. nn - return code explanation." Processing continues.

The open of the ASSO failed. After checking the PLOGs, it was determined that the PLOG to be copied was from a cluster database. Either the ASSO must be restored or the PLCOPY NOPPT function must be executed copy off the PLOGs. All pertinent PLOG DD-statement from the cluster should be supplied as input to the NOPPT function.


ERROR-172 Incorrect PLOGs supplied
Explanation

This error occurs if you attempt to run a regenerate using PLOGs that are not at the Adabas 7.2 or 7.4 level (or later). ADARES cannot use PLOGs from a backlevel version.

Action

If you need to run an ADARES job that spans Adabas versions, the ADACNV utility must be part of the recovery process. Here is an example of the recovery steps:

  1. Run an ADASAV RESTORE job against the old version database.

  2. Start the nucleus of the old version database.

  3. Run an ADARES job using ADARES REGENERATE PLOGNUM=old-plognr, where old-plognr is the PLOG number for the old database.

  4. Shut down the nucleus of the old version database.

  5. Run an ADACNV CONVERT job on the old version database to produce a new version database.

  6. Start the nucleus of the new version database.

  7. Run an ADARES job using ADARES REGENERATE PLOGNUM=new-plognr , where old-plognr is the PLOG number for the new database.


Top of page

ADARES Warning Messages

Overview of Messages

Warning - Input intermediate data set is invalid | Warning - The PPT has been cleared | The PPT indicates that there are currently no PLOGS to be copied for this database | Warning - CLOG is from a cluster database. A normal CLCOPY will run, since the PPT is not accessible. A subsequent CLOG MERGE must be run to merge the CLOG data sets.
Warning - Input intermediate data set is invalid
Explanation

NOPPT was specified and an invalid intermediate data set was supplied. Some of the protection records may be missing from the merged output.

System Action:

Since NOPPT was specified, processing continues and a condition code of 4 is returned.


Warning - The PPT has been cleared
Explanation

The parallel participant table (PPT) has been cleared since the last merge. Protection log data may be lost.

System Action:

Processing continues under the assumption that the database has been restored.

Action

Ensure that clearing the PPT was intended.


The PPT indicates that there are currently no PLOGS to be copied for this database
Explanation

There are no PLOGs to be copied.

Action

Determine the cause of the error. If necessary, contact your Software AG technical support representative for assistance.


Warning - CLOG is from a cluster database. A normal CLCOPY will run, since the PPT is not accessible. A subsequent CLOG MERGE must be run to merge the CLOG data sets.
Explanation

Prior to the warning, the following should be seen: "The Associator data set(s) could not be opened. nn - return code explanation." Processing continues.

The open of the ASSO failed. After checking the CLOGs, it was determined that the CLOG to be copied was from a cluster database. A normal CLCOPY (non-merge) will run. A subsequent CLOG should run to merge the CLOG data sets.


Top of page