ADASAV Utility Error Messages

The DIB entry in the Utility Communications Block (UCB) that the utility created at the begin of its processing is no longer present at its end. Another utility may have modified files that were supposed to be locked. The result of this utility execution may be inconsistent.

Determine what happened to the DIB entry. Then rerun the utility to ensure utility execution is consistent for all files. If the problem persists, contact your Software AG technical support representative.

The wrong protection log tape has been mounted. The requested protection log has DBID (dbid-a), session number (session-id).

The supplied protection log is from DBID (dbid-b), session number (sess-num-b).

Supply the correct tape and start an ADASAV job using the RESTPLOG function.

One of the following has occurred:

1. The SYN1/SYN4 checkpoint is not contained in the protection log block (block-number); or

2. The SYN2/SYN5 checkpoint is not contained anywhere on the protection log; or

3. Another SYN1/SYN4 checkpoint was encountered before the expected SYN2-SYN5 checkpoint.

The wrong protection log has been mounted, or the wrong SYN1-SYN4 checkpoint has been specified.

Supply the correct protection log and parameters. For case 1 or 2, continue with the RESTPLOG function. For case 3, repeat the RESTONL function.

The RESTORE function expects the RESTn/DDRESTn data sets to be presented in the order in which they were created.

Ensure that input tapes are mounted in correct order; then rerun the job.

One of the following occurred:

• No file numbers, invalid file numbers, or duplicate file numbers were specified in the FILES, FMOVE, NEWFILES, or EXCLUDE parameter.

• More file numbers were specified in the NEWFILES parameter than in the FILES or FMOVE parameter.

• A file specified in the EXCLUDE parameter was not specified in the FILES, FMOVE, or NEWFILES parameter.

Supply the correct parameter value and rerun the job.

Either SAVE or RESTORE is required.

Supply the correct parameter value and rerun the job.

Either SAVE or RESTORE is required: not both.

Supply the correct parameter value and rerun the job.

The value for this parameter must be greater than or equal to 1 and less than or equal to 8. The default value is 1.

Supply the correct parameter value and rerun the job.

Include all files of this expanded file in the file list, then rerun the ADASAV job.

A correct value is in the range 1 to 65,535.

Supply the correct parameter value and rerun the job.

The number of values in the parameter list for PERDRIVE must be equal to the value of the DRIVES parameter.

Supply the correct parameter value and rerun the job.

The incorrect type of ADASAV restore function was used for the type of output save tape from the previous ADASAV SAVE operation.

Use the RESTONL function for restoring a tape saved with the nucleus online, and also provide the associated protection log. Use the RESTORE function for restoring a tape saved with the nucleus offline.

An invalid input for RESTORE is supplied.

The RESTORE input must have been produced by a previous ADASAV SAVE execution.

Supply a correct input and rerun the job.

For the RESTORE FILES function, the restore tape must have been produced by a version 5.1 or above ADASAV SAVE execution.

For the RESTORE (database) or RESTORE GCB function, the restore tape must have been produced by an ADASAV SAVE execution with the same version as is used for the restore.

Supply a correct input and rerun the job.

The ADASAV restore source and destination device types are different. ADASAV restore functions cannot accept different source and output device types or extents.

Respecify the output to the same device type or extent as the restore function source, and resubmit the job. For more information, see the Adabas Utilities documentation.

The save data set cannot be restored because:

• The save data set is a file save data set that can be restored only with RESTORE/RESTONL FILE/FMOVE;

• The save data set is a delta save data set that can be restored only in combination with a full database save data set (using RESTORE DELTA).

The RESTORE database or RESTORE GCB function is abnormally terminated.

Provide the right save data set or specify the correct restore function.

The ADASAV RESTORE Open command received a nucleus response code of (resp-code - explanation). The nucleus is active, which is not allowed during a RESTORE database operation.

Ensure that the correct nucleus has been accessed; if so, shut down the nucleus and then rerun the ADASAV RESTORE job.

Correct either the file number or change the MAXFILE value in the database.

Supply a correct input data set containing the specified file, or remove the file number from the parameter list.

Include all files coupled together in the file list and rerun the job.

Supply a correct file list using the FILE or FMOVE parameter and rerun the job.

Supply a larger value for the parameter specified in place of "value" in the message, and rerun the job. Refer to the Adabas Utilities documentation for more information.

One of the followed is the case:

• An attempt was made to increase MAXISN but the file was defined with NOACEXTENSION; or

• The specified size (in cylinders) is too large.

ADASAV RESTORE expects to get a Response Code returned that indicates that the database is down. However, ADASAV RESTORE was returned a sub code indicating that another utility currently has exclusive control of the database.

Ensure the correct nucleus has been accessed; if so, wait for the other utility to run before running the ADASAV RESTORE.

This file is removed from the file list. ADASAV will continue.

The Associator used for output already contains a database.

The OVERWRITE parameter may be used to overwrite an existing database.

One of the following is the case:

• The Adabas nucleus is active but running without a protection log; or

• A save operation is already active.

Correct the cause of the problem and rerun the job.

The total of all values supplied for this parameter must equal the number of entries in the VOLSER table displayed with this message.

Respecify the PERDRIVE parameter, and rerun the job.

See Adabas Response Codes for the explanation of nucleus response codes.

The proper synchronization of the nucleus protection log (PLOG) and the output of the SAVE run is not possible.

Rerun the ADASAV SAVE job. If the error occurs again, consult your Software AG technical support representative.

The highest value permitted for BUFNO is 255.

Respecify the BUFNO value, then rerun the ADASAV job.

The file ^" file-number-a" is coupled to file "file-number-b", which is not selected for the RESTORE operation (actual file values are displayed in the message text). This RESTORE cannot be serviced because it would result in a logical data inconsistency.

Check the RESTORE function parameter input; correct the error and then rerun the RESTORE job.

The file "file-number-a" is part of an expanded file. It is linked to the file "file-number-b", which is not selected for the RESTORE operation (actual file values are displayed in the message text). This RESTORE cannot be serviced because it would result in a logical data inconsistency.

Check the RESTORE function parameter input; correct the error and then rerun the RESTORE job.

The parameter named in the message (parm) cannot be specified in the same ADASAV run that specifies a range of files in the FILES or FMOVE parameter.

Remove the parameter and rerun the job.

An attempt was made to:

• overwrite an Adabas system file with a disparate system file or a non-system file;

• introduce a second system file into a database where the corresponding system file already exists;

• restore a user-defined system file into a database where the GCBs' system file list is full; or

• restore a checkpoint or security file from Adabas version 5.

Correct the file specification and, if appropriate, rerun the ADASAV job.

The Adabas nucleus must be active to

• check the replication log information for the files being saved; or

• clear the replication log for files being restored.

Start the Adabas nucleus, then rerun the ADASAV job.

Some of the blocks to be saved/restored lie within physically unallocated database storage. Probably an ADADBS or Adabas Online System "increase" was run without first providing the associated physical storage.

Allocate the physical storage, then rerun the ADASAV job.

The "associator|data" RABN "rabn-number" was not found on the restore tape. Either end-of-file (EOF) occurred, or ADASAV found "count" RABN "rabn-number" instead. Either a required tape volume is missing, or the tapes are mounted in the wrong order.

Supply a correct restore tape, then rerun the ADASAV job.

The restore tape does not contain the expected data. All records on the tape must contain references to DBID dbid, session number session-id, and time stamp ttt. A record was found that incorrectly referred to DBID dbid-x, session number session-id-x, and time stamp ttt.

Correct the cause of the incorrect reference, then rerun the ADASAV job.

The Adabas protection log does not contain the expected data. The last record that was read should have contained DBID "dbid", serial number "number", and time stamp >= "ttt". However, it contained instead DBID "dbid-x", serial number "number-x", and time stamp "ttt-x".

Correct the cause of the incorrect reference, then rerun the ADASAV job.

This generic error message is issued after a Delta Save error message. An error occurred while the Delta Save Facility was processing the requested function. The internal response code by Delta Save is shown.

The function is abnormally terminated.

For more information, see the Delta Save error message preceding this message.

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

ADASAV terminates abnormally.

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

The database has a Delta Save logging (DLOG) area installed, but ADASAV was not started with the Delta Save Facility.

ADASAV terminates abnormally.

Specify ADARUN parameter DSF=YES and rerun the job.

There is no full save input to the MERGE function, so the output save data set will be a delta save or an unloaded DSIM data set. The DRIVES parameter is allowed only when a full save data set is merged.

The merge function terminates abnormally.

Remove the DRIVES parameter and rerun the job.

The save data set input for the merge function is incomplete. End-of-file was encountered when Associator or Data Storage RABN "num" was expected. Possibly a required tape volume is missing or input tape volumes have been concatenated so that an end-of-file mark was encountered before the last tape.

The merge function terminates abnormally.

Supply complete input data sets and rerun the job.

The save data set input for the merge function is incomplete. Associator or Data Storage RABN "num2" was found when RABN "num1" was expected. Possibly a required tape volume is missing or input tapes are mounted in the wrong order.

The merge function terminates abnormally.

Supply complete input data sets and rerun the job.

The combination of parameters and input save data sets is invalid:

• DRIVES>1 is not allowed for RESTORE GCB, RESTORE FILE, or RESTORE FMOVE with DELTA;

• Concatenation of delta save input data sets is not allowed for RESTORE GCB, RESTORE FILE, or RESTORE FMOVE with DELTA.

The RESTORE DELTA function terminates abnormally.

Correct the arrangement of input save data sets and rerun the job.

The full save tape was omitted the restore operation but the current status of the database does not allow this. One of the following was detected:

• The function is not RESTORE database.

• The Associator failed to open. The full save data set probably had not been successfully restored in a previous run. An ADAIOR error text is given.

• No Delta Save logging (DLOG) area is installed in the database.

• Delta Save logging is not enabled; that makes this operation invalid.

• The database has been modified since the last restore operation: the Adabas nucleus has been active, the DLOG area is not empty.

• The database has been modified since the last restore operation: a utility has changed the file indicated in the message.

• The database has been modified since the last restore operation: the DLOG header block was altered.

• A file excluded from the previous restore must now also be excluded but has not been.

• A file specified as excluded was not excluded from the previous restore.

The delta restore function terminates abnormally.

Provide the full save data set for the delta restore operation and rerun the job.

The database layout was changed by an ADADBS ADD, INCREASE, or DECREASE function (or by the equivalent Adabas Online System function). Later on, a delta save data set was produced that is now input to the restore function. ADASAV is not able to handle the changed GCBs in the second phase of the delta restore process.

The changed GCBs are written to the database. Then the delta restore function terminates abnormally.

There are two possible ways to correct this problem:

• Merge all input save data sets and restore the resulting merged full save data set; or

• Rerun the delta restore function without the full save data set, starting with the first delta save data set not yet restored; doing this causes ADASAV to bypass the earlier, old image of the GCBs.

An attempt was made to restore one or more files from a database with "x"-byte RABNs into a database with "y"-byte RABNs.

The requested function cannot be performed.

The maximum compressed record length defined for file "file-number" is too big to be compatible with the Work block size.

The file can be restored only into a database with a larger Work block size.

Use the ADADEF NEWWORK function to define a new Work data set with a larger block size so that you can restore the file.

The secondary address converter extent allocated by the nucleus during an online save could not be restored to the current address converter due to conflicting device types.

Remove the MAXISN parameter for this file and rerun the RESTONL FMOVE function.

The NEWFILES parameter must not be specified for expanded files or physically coupled files.

Remove the corresponding file number assignment from the NEWFILES list and rerun ADASAV.

For an online SAVE FILE operation or a SAVE FILE with UTYPE=EXU, all component files of an expanded file chain and all files that are coupled must be specified explicitly in the FILES parameter (see the ADAU15 message(s) above this error message).

Correct the FILES parameter and rerun the job.

The specified file was not being restored in a RESTONL operation that was interrupted and thus may not be selected for the RESTPLOG function.

Correct the RESTPLOG parameter input and rerun the job.

Valid values are ALLOCATION=FORCE | NOFORCE.

Supply the correct parameter value and rerun the job.

The DIB entry that ADASAV wrote at the beginning of the SAVE operation was no longer present at the end. It may have been removed by a nucleus that was incorrectly started with parameter IGNDIB=YES. A parallel nucleus or utility may have updated the database while ADASAV was running. The save data set may be inconsistent.

Investigate the cause of the error. Correct it and rerun the job. Do not use the save data set.

A database defined as an Event Replicator Server (created with REPTOR=YES) must not contain user files or system files not related to replication.

Do not attempt to restore files other than CHECKPOINT, SECURITY, REPLICATOR, or SLOG on Event Replicator Servers. Correct the parameters and rerun the job.

The ADASAV utility determined the nucleus was active without a DIB entry.

Check the job to ensure the correct ASSO, DATA, and WORK data sets are specified for the given DBID.

One or more of the parameters listed in the message were specified in the ADASAV run without a corresponding FILES or FMOVE parameter.

Supply the correct parameter and rerun the job.

The value of the RPLDSBI parameter (value) for the file listed in the message (fnr) is incorrect. It must be YES, NO, or empty.

Supply the correct parameter value and rerun the job.

The values of parameters RPLACTIVE, RPLDATA, RPLDSBI, or RPLKEY must not be specified because the file is not replicated (RPLTARGETID is OFF or 0). The specified parameter (parameter-name), its value (parameter-value), and the file number (fnr) of the ADASAV run are given in the message.

The value of the RPLKEY parameter (parameter-value) for the file (fnr) is invalid. It must be either a two-character field name, OFF, or empty.

Correct the parameter value and rerun the job.

The value of the RPLACTIVE parameter (parameter-value) for the file (fnr) is invalid. It must be either YES, NO, or empty.

Correct the parameter value and rerun the job.

The value of the RPLDATA parameter (parameter-value) for the file (fnr) is invalid. It must be either YES, NO, CREATE, or empty.

Correct the parameter value and rerun the job.

Parameters RPLACTIVE, RPLDATA, RPLDSBI, and RPLKEY are not allowed if the target database for the restore is not replicated.

Correct the parameter values and rerun the job.

Parameters RPLTARGETID, RPLACTIVE, RPLDATA, RPLDSBI and RPLKEY are not allowed for ADASAV functions other than RESTORE/RESTONL FILES, FMOVE, and GCB (with the FILES parameter).

Correct the parameter values and rerun the job.

ADASAV was unable to load modules ADARPV for the reason listed in the message. ADASAV calls ADARPV when the RPLLOAD parameter is set to YES or FILE.

Investigate the cause of the error, correct it, and rerun the job.

An ADASAV communication to the Event Replicator Server has failed with the response (rc) and subcodes (sc) listed in the message. The location (loc) is also listed in the message.

Verify and correct (if necessary) the ADASAV parameters and JCL. Refer to the response code descriptions for information about the response code and subcode. If necessary, contact your Software AG support representative for assistance.

Multiple replication jobs cannot run concurrently for the same file.

Verify and correct (if necessary) the replication job parameters to ensure the correct information is provided for replication. If problems persist, contact your Software AG support representative for assistance.

An RPLCLEANUP was issued for the Event Replicator Server. This removed the ADASAV token and communication to the Event Replicator Server is no longer possible for this job.

Determine why the operator RPLCLEANUP command was issued. Prepare for file recovery as necessary before rerunning ADASAV.

The replication pool for the Event Replicator Server listed in the message (id) has an overflow condition, which is a critical error.

Refer to the Event Replicator Server job's system log for error messages which may provide possible actions to take to resolve this problem.

The Adabas database with the database ID (dbid) listed in the message is not defined to the Event Replicator Server (id) listed in the message.

Verify and correct the JCL or input parameters for the ADASAV run. If they are correct, modify the Replicator system file definitions. Then try the ADASAV run again.

No active destination or subscription could be found for the file listed in the message (number) on the Event Replicator Server (id) named in the message.

First verify and correct (as necessary) the file number or the Event Replicator Server target ID for the ADASAV run. If they are correct, modify the Replicator system file subscription and destination definitions to ensure a definition exists for the file. Then try the ADASAV run again.

The versions of ADASAV and ADARPV are internally incorrect.

Verify and correct (if necessary) the JCL allocation of libraries and input parameter to ADASAV. If problems persist, contact your Software AG support representative for assistance.

ADARPV has failed with an internal error at the offset given in the message.

Contact your Software AG support representative for assistance, and provide details of the failure.

Program ADARPV cannot load program ADAMGT.

Verify and correct (if necessary) the JCL allocation of libraries and input parameters to ADASAV. If problems persist, contact your Software AG support representative for assistance.

Program ADARPV has detected an invalid version of program ADAMSG.

Verify and correct (if necessary) the JCL allocation of libraries and input parameters to ADASAV. If problems persist, contact your Software AG support representative for assistance.

The version of Adabas or the Event Replicator used by the Adabas database is not the same as the version of the Adabas or Event Replicator used by the Event Replicator Server.

Resolve the discrepancy in the Adabas and Event Replicator Server Adabas versions before you try again.