ADARES Utility Error and Warning Messages

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

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

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

Supply the correct parameter value and rerun the job.

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

Supply the correct parameter value and rerun the job.

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.

Contact your Software AG technical support representative.

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.

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

Missing or invalid FROMCP or TOCP specification.

See the Adabas Utilities documentation for further information.

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.

Correct the error and rerun the job.

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.

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

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

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

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

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

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

Supply a correct protection log and rerun the job.

One of the following is required:

• a single RABN; or

• an ascending range of RABNs.

Supply the correct parameter value and rerun the job.

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.

Supply a correct parameter value and rerun the ADARES job.

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

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

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

Supply the correct parameter value and rerun the ADARES job.

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.

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

The ADARES statement did not specify an ADARES function.

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

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

Supply the correct PLOG tapes and rerun the ADARES job.

Sessions to be copied include both PLOG and SAVE sessions.

Supply the correct input tapes and rerun the ADARES job.

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

Supply the correct input tapes and rerun the ADARES job.

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

Rerun the job with the ADARUN parameter MODE=MULTI.

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

ADARES terminates abnormally.

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

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.

ADARES terminates abnormally.

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

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

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

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.

Correct the error and rerun the job.

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.

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

Valid values are ALLOCATION={FORCE | NOFORCE}.

Supply the correct parameter value and rerun the job.

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

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

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

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.

Supply the correct parameter value and rerun the job.

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

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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.

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

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

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

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.

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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.

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

An error occurred while processing a protection record.

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

The block numbers are not increasing sequentially.

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

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

Supply the correct intermediate data sets.

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

Correct the JCL and resubmit the job.

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.

Correct the input and resubmit the MERGE CLOG job.

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

Correct the JCL and resubmit the job.

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

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.

ADARES detected an empty input data set.

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

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

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.

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.

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.

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

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

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

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

Ensure that clearing the PPT was intended.

There are no PLOGs to be copied.

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

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.