Version 7.4.4
 —  Messages and Codes  —

ADARES Error and Warning Messages

The following message groups are described:


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.

User Action:

Supply a correct protection log dataset 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).

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

User 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 dataset for the requested session"session-id".

User Action:

If there is a valid EOF mark on the input dataset, add the NONUC parameter and rerun the job.


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.

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

User 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 dataset 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.

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

User Action:

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


ERROR-129 EMPTY PLOG DATASET FOR BACKOUT
Explanation:

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

User Action:

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


ERROR-130 PLOG DATASET NOT YET COPIED
Explanation:

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

User Action:

Run the ADARES function PLCOPY first to save the contents of the dual or multiple protection log dataset, 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 dataset (dataset-name).

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

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

User Action:

Supply a correct parameter value and rerun the ADARES job.


ERROR-134 PROTECTION LOG NUMBER MISMATCH
Explanation:

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

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

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

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

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

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

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

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

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

User Action:

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


ERROR-143 ERROR DURING DSIM DATASET PROCESSING
Explanation:

An error occurred while the Delta Save Facility was processing (building) the delta save images (DSIM) dataset. The DSIM dataset 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 dataset.

System Action:

ADARES terminates abnormally.

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

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

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

User 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}.

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

User 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 GCB.

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 GCB has been damaged.

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

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

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

User Action:

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


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.

User 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 dataset supplied for the protection or command log merge process in an Adabas cluster environment.

User 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 dataset supplied for the protection or command log merge process in an Adabas cluster environment.

User 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 dataset supplied for the protection or command log merge process in an Adabas cluster environment.

User Action:

Contact your Software AG technical support representative.


ERROR-157 INCORRECT { MERGIN1 | MERGIN2 } FILE SUPPLIED
Explanation:

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

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

User 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 dataset.

User 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 dataset in the parallel participant table (PPT).
4 An error occurred reading the PLOGR2 or CLOGR2 dataset 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.
User 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.

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

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

User Action:

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


ERROR-164 THE INTERMEDIATE DATASET DID NOT CONTAIN AS MANY RECORDS AS EXPECTED
Explanation:

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

User Action:

Supply the correct intermediate datasets.


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.

User 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 datasets supplied to the ADARES MERGE CLOG function was in error. The input is expected to be sequential datasets and CLOGLAYOUT=5 must have been used to create the original CLOG.

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

User Action:

Correct the JCL and resubmit the job.


ERROR-168 THE NUMLOG PARAMETER SPECIFIED WAS xx BUT yy DATASETS WERE SUPPLIED
Explanation:

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

User Action:

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


ERROR-169 AN EMPTY DATASET WAS SUPPLIED AS INPUT TO THE MERGE CLOG FUNCTION
Explanation:

ADARES detected an empty input dataset.

User Action:

Remove the dataset and adjust the NUMLOG value; or supply a valid datasest. 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 dataset(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. 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 DATASET 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 DATASETS.
WARNING - INPUT INTERMEDIATE DATASET IS INVALID
Explanation:

NOPPT was specified and an invalid intermediate dataset 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.

User 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 DATASETS.
Explanation:

Prior to the warning, the following should be seen: "The Associator dataset(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 datasets.


Top of page