DSFnnn-Delta Save Facility Messages

The nucleus has been started with ADARUN parameter DSF=YES. Delta Save functions can be performed in this nucleus session.

This is a Delta Save Facility status message. Delta save operations require a Delta Save logging (DLOG) area, which must be created.

To run with Delta Save, use the Adabas Online System "Install DSF" function to define the logging area.

This is a Delta Save Facility status message. Delta save operations are not possible.

This is a Delta Save Facility status message. Delta save operations are possible in this status.

This message indicates how much of the Delta Save logging (DLOG) area is being used. The second line of the message is only printed if the DLOG area usage is 90 percent or more; that is, nearly full. If the area overflows, delta save operations will no longer be possible.

If DLOG area overflow is pending, perform a delta save operation before the area overflows.

Initialization of the Delta Save logging (DLOG) area was interrupted. The DLOG area must be installed again.

Remove the DLOG area and install it again.

Initialization of the Delta Save logging (DLOG) area was interrupted. An online full save operation was completed but Delta Save logging was not enabled at the end of the save. Delta save operations are still not possible.

Remove the DLOG area and install it again. Perform another full save operation.

This message, which is printed during shutdown of the Adabas nucleus, indicates the number of I/O operations initiated by Delta Save during the current nucleus session.

Unless this message is displayed, an online full save operation with the Delta Save Facility is not successful, even though ADASAV may have already closed the output save dataset.

The Delta Save logging area is reset. If Delta Save logging was disabled, it will be enabled.

Unless this message is displayed, an online delta save operation is not successful, even though ADASAV may have already closed the output save dataset.

The Delta Save logging area is reset.

This message follows messages DSF005, DSF011, or DSF012. It displays the delta save identification of the most recent completed full or delta save operation. "fsnum" is the full save number, and "dsnum" is the number of the delta save operation.

This message follows messages DSF011 and DSF013 if Delta Save logging was previously disabled. It was enabled at the end of the operation. Delta save operations are now possible.

A "Disable DSF" command was issued by Adabas Online System.

Delta Save logging will be disabled.

The reason for this follows from a preceding message. Delta save operations are no longer possible.

Perform a full save operation before retrying a delta save operation.

An "Install DSF" or "Change DLOG Area" command has been issued through Adabas Online System.

The Delta Save logging area is now being initialized. Message DSF018 indicates that initialization is complete.

An "Install DSF" or "Change DLOG Area" command was completed.

A "Remove DSF" command was performed, or the nucleus was started with DSF=NO and has removed the Delta Save logging area.

The volume of changes made to the database exceeded the capacity of the Delta Save logging (DLOG) area. The DLOG area is full. No more delta save operations are possible.

Delta Save logging will be disabled.

Perform a full save operation before retrying a delta save operation. Increase the DLOG area or the frequency of delta save operations in order to avoid future DLOG area overflow.

An I/O error occurred within the Delta Save logging (DLOG) area on the specified Associator RABN.

If Delta Save logging is enabled, it will be disabled.

Determine the cause of the I/O error and eliminate it. Remove the DLOG area and install it again.

An I/O error occurred on the first block (the specified RABN) of the Delta Save logging (DLOG) area.

Warning: Warning: Do not try to execute a delta save operation if this error occurs. Even though the delta save may end successfully, the output may be invalid.

The Delta Save Facility terminates the nucleus abnormally.

Determine the cause of the I/O error and eliminate it. Remove the DLOG area and install it again.

An inconsistency was detected in the specified block ("rabn") of the Delta Save logging (DLOG) area. "rabn" is the Associator block number, "rr" is an internal reason code, "xxxx" the offset within the block where the error appeared.

If Delta Save logging is enabled, it will be disabled.

Determine the cause of the problem; consult your Software AG technical support representative if necessary. Remove the DLOG area and install it again.

An inconsistency was detected in the specified block ("rabn") of the Delta Save logging (DLOG) area. "rabn" is the Associator block number.

If Delta Save logging is enabled, it will be disabled.

Determine the cause of the problem; consult your Software AG technical support representative if necessary. Remove the DLOG area and install it again.

An attempt to disable Delta Save logging failed because the nucleus was started with READONLY=YES.

Another attempt will be made to disable Delta Save logging in the next nucleus session.

Shut down the nucleus and restart it with READONLY=NO so that Delta Save logging can be disabled.

An internal cross-check detected that database blocks were written that had not been logged by Delta Save. The type (Asso/Data) and range of RABNs written are displayed.

Delta Save logging will be disabled.

This is a serious problem. Contact your Software AG technical support representative. Perform a full save operation before retrying a delta save operation.

The Delta Save Facility was not able to obtain sufficient memory for its operation. The number of bytes of memory specified by "count" were requested.

The start of the nucleus session is ended.

Increase the region/partition of the nucleus job/task or decrease the memory requirements derived from the nucleus parameters.

The version of the Delta Save Facility software and the version of the Delta Save logging (DLOG) area are different and incompatible.

If Delta Save logging is enabled, it will be disabled.

Remove the DLOG area and install it again.

The format of the Delta Save logging (DLOG) area is converting from version "xx" to version "yy". This occurs during conversion of an older Adabas version to a newer one.

Depending on the versions of the Delta Save Facility (that is, "xx" and "yy"), Delta Save logging may be disabled if it is enabled.

If Delta Save logging is disabled, perform a full save operation before retrying a new delta save operation.

An internal error occurred at the specified "offset" in module ADADSFN. "reason-code" is an internal reason code. The register settings at the time of the error are shown.

If Delta Save logging is enabled, it will be disabled.

Consult with your Software AG technical support representative to determine the cause of the problem. Perform a full save operation before retrying a delta save operation.

The DSF user exit returned an invalid threshold value (percentage of DLOG area usage at or above which Adabas is to call the exit).

Adabas calls the DSF user exit when the usage of the DLOG area is nn% or more.

The DLOG block currently referenced is not in the coupling facility cache structure and must be read anew from the disk datasets.

The DLOG block currently referenced is already held in the coupling facility cache structure.

An attempt to write the DLOG block currently referenced from a disk dataset to the coupling facility cache structure failed. Probably, the cache structure is full.

Enlarge the size of the cache.

The ADARUN parameter DSF=YES was specified for a PLCOPY execution but no Delta Save images (DSIM) dataset was supplied in the job control.

None. No online save information is extracted from the protection log.

If Delta Save online save and merge operations are to be performed, specify a DSIM dataset for the PLCOPY executions.

A SYN1 checkpoint (online save start) was found on the protection log. The protection log number is "plog-number", the SYN1 block number is "rabn".

The Delta Save Facility starts extracting online save information from the protection log and writing it to the Delta Save images (DSIM) dataset.

A SYN2 checkpoint (online save end) was found on the protection log. The protection log number is "plog-number", the SYN2 block number is "rabn".

The Delta Save Facility stops extracting online save information from the protection log. The Delta Save images (DSIM) dataset is marked ready for merge.

A SYN1 checkpoint (online save start) was found on the protection log. The protection log number is "plog-number", the SYN1 block number is "block-number". These values are different from the PLOGNUM and SYN1 parameters specified for the COPY function.

The Delta Save Facility does not start extracting online save information from the protection log. The SYN1 checkpoint is ignored.

A SYN1 checkpoint (online save start) was found on the protection log but the Delta Save images (DSIM) dataset is by now ready for merge.

The SYN1 checkpoint is ignored.

A SYN1 checkpoint (online save start) was found on the protection log but the Delta Save images (DSIM) dataset is not in a correct status. The current DSIM status "status-code" is shown.

The SYN1 checkpoint is ignored.

Rebuild the DSIM dataset using the ADARES COPY function.

A SYN1 checkpoint (online save start) was found on the protection log but was written before the start of the online save operation associated with the DSIM dataset. Therefore, the checkpoint does not indicate the start of the online save operation for which information is to be extracted from the protection log.

The SYN1 checkpoint is ignored.

None. If there is only one SYN1 checkpoint on the protection log to be copied and the message cannot be otherwise explained, check whether the Adabas nucleus and the ADASAV utility that is executing the online save operation were running on different machines or on different divisions of the same machine. If so, ensure that the local times of these two machines or divisions are accurately synchronized.

A SYN2 checkpoint (online save start) was found on the protection log but the previous SYN1 checkpoint was ignored because of the incorrect status of the Delta Save images (DSIM) data set. The current DSIM status status-code is shown. See the corresponding DSF033 message.

The SYN2 checkpoint is ignored.

Rebuild the DSIM data set using the ADARES COPY function.

(printed on the ADARUN protocol) The Delta Save images (DSIM) dataset has been opened. Its current status is shown.

(printed on the ADARUN protocol) The Delta Save images (DSIM) dataset status has been changed to the new one shown.

(printed on the ADARUN protocol) The Delta Save images (DSIM) dataset has been closed. Its current status is shown.

The Delta Save images (DSIM) dataset has been completed and marked ready for merge. Statistics displayed include

• its percentage of use;

• the number of Asso and Data block images contained in the DSIM dataset (block counts do not differentiate several images of the same block); and

• the number of address converter blocks allocated during the associated online save operation and recorded in the DSIM dataset.

This message, which is printed on the operator console with a "dbid" and on the ADARUN protocol without a "dbid", indicates that the Delta Save images (DSIM) dataset is not yet ready for merge. The DSIMWAIT parameter has been specified to wait for the completion of the DSIM dataset.

The Delta Save Facility waits until the DSIM dataset is ready for merge, or until the maximum wait time (DSIMWAIT) has been exceeded.

This message indicates how much of the Delta Save logging (DLOG) area is already being used at the beginning of a delta save operation.

The specified type of save operation was completed successfully. The ID of the delta save operation (DSID) is displayed: "fsnum" and "dsnum" are the numbers of the full and delta save operation, respectively.

For an offline save operation, this message is also written to the operator console with a "dbid". For an online save, the Adabas nucleus writes equivalent information in the DSF011-DSF013 messages.

For an offline save operation, the Delta Save logging (DLOG) area is reset. For a full save operation, if Delta Save logging was disabled, it will be enabled

• by ADASAV for an offline save operation; or

• by the nucleus for an online save operation.

This message occurs following message DSF042. delta save operations are now possible. Unless this message is displayed, an offline full save operation with the Delta Save Facility is not successful, even though ADASAV may have already closed the output save dataset.

This message is also written to the operator console with a "dbid".

(printed at the beginning of a delta save operation) The number of Associator and Data Storage blocks to be saved.

In a MERGE or RESTORE DELTA operation, an input save dataset with the stated delta save identification was opened. "fsnum" is the full save number; "lowdsnum" the low delta save number, and "hidsnum" the high delta save number of the save dataset.

In a MERGE or RESTORE DELTA operation, an input delta save dataset with the stated delta save identification was opened. The delta save dataset was concatenated to another delta save dataset. "fsnum" is the full save number; "lowdsnum" the low delta save number, and "hidsnum" the high delta save number of the save dataset.

In a MERGE or RESTORE DELTA operation, an input online delta save dataset with the stated delta save identification was opened. The delta save dataset is an unloaded DSIM dataset. "fsnum" is the full save number; "dsnum" the delta save number of the save dataset. If the originating DSIM dataset was (re)built from the PLOG using the ADARES COPY function, the DSID is unknown and shown as zeros.

In a delta restore operation without full save input the database has the stated delta save identification. The associated full and delta save datasets were restored previously. The value "fsnum" denotes the full save number, "hidsnum" is the highest delta save number of the save datasets already restored.

In a MERGE operation, the indicated output save dataset has been completed. Its delta save identification is shown. "fsnum" denotes the full save number. "lowdsnum" is the low delta save number and "hidsnum" is the high delta save number.

This message is also written to the operator console with a "dbid".

In a MERGE operation, an unloaded DSIM delta save dataset with the delta save identification shown has been written. "fsnum" denotes the full save number; "dsnum" is the delta save number. If the originating DSIM dataset was (re)built from the PLOG using the ADARES COPY function, the DSID is unknown and shown as zeros.

This message is also written to the operator console with a "dbid".

A phase of a delta restore operation has been completed. One or more save tapes have been restored. Their combined delta save identification is shown. A subsequent delta restore operation without full save input may begin with the delta save dataset that has the next higher delta save identification. "fsnum" is the full save number. The value "lowdsnum" is the low delta save number, and "hidsnum" is the high delta save number.

This message is also written to the operator console with a "dbid".

This message is printed when the Delta Save images (DSIM) dataset is examined and matches one of the online save input datasets. It is also printed when the DSIM dataset is to be unloaded. The DSIM dataset contains "asso-count" different Associator blocks and "data-count" different Data blocks to take part in the operation.

Without a Delta Save logging (DLOG) area installed and Delta Save logging enabled, it is not possible to perform delta save operations.

The delta save operation is abnormally terminated.

Use Adabas Online System to install a DLOG area and perform a full save operation to enable Delta Save logging.

Delta Save logging must be enabled before delta save operations are possible.

The attempted delta save operation is abnormally terminated.

Perform a full save operation to enable Delta Save logging.

When running with Delta Save (ADARUN parameter DSF=YES is specified), a Delta Save images (DSIM) dataset must be provided for an online full or delta save operation.

The online save operation is abnormally terminated.

Supply a DSIM dataset for the online save operation or perform the save operation offline.

The Delta Save images (DSIM) dataset must be "not in use" to be eligible for a Delta Save Facility online save operation. The current status of the DSIM dataset is different, as shown.

The online save operation is abnormally terminated.

Determine whether the DSIM dataset is required for merging a previously created online save tape. If not, reset the DSIM dataset (using ADAFRM function DSIMRESET) and rerun the save operation.

Execution of ET-synchronization at the end of the online save operation was not successful. The Delta Save logging (DLOG) area was not reset. Delta Save logging remains disabled if it was disabled before, or enabled if it was enabled before. A subsequent ADASAV error message indicates the nucleus response code for the failed ET-synchronization.

Although it has already been closed, the created save dataset must not be used for later merge or restore operations.

The online save operation is abnormally terminated.

Eliminate the cause of the error and rerun the online save operation.

Execution of ET-synchronization at the end of the online save operation was successful. The Delta Save logging (DLOG) area was reset. Afterwards, an error occurred and caused a nucleus response code to be returned to ADASAV. A subsequent ADASAV error message indicates the response code returned by the nucleus. If Delta Save logging was disabled before, it has been enabled.

ADASAV prints an error message but continues operation. When terminating normally, it will set condition code 4.

The created save tape is valid and may not be dropped if delta save operations are to follow later on. Otherwise the succeeding delta save datasets cannot be merged and/or restored.

Only the DSIM dataset has been specified for processing. No full or delta save input dataset has been supplied.

ADASAV unloads the DSIM dataset to the sequential output save dataset and frees the DSIM dataset for the next online save operation.

A full save tape created by the Delta Save Facility was restored. The delta save identification of the restored database is shown. "fsnum" is the full save number; "lowdsnum" is the low deta save number; and "hidsnum" is the high delta save number of the save datasets restored.

This message is also written to the operator console with a "dbid".

Delta Save logging was enabled in the restored database.

The next save operation can be a delta save. Its result can be merged with the full save that was input to the restore operation.

A full save created by the Delta Save Facility is to be restored but the ADARUN parameter DSF=NO has been specified.

The Delta Save logging (DLOG) area will be removed. The restore operation continues normally.

None required. If the restored database is to be run with the Delta Save Facility, install the DLOG area again.

The input dataset requirements for

• functions MERGE and RESTORE DELTA: at least one full or delta save dataset must be supplied.

• unloading the DSIM dataset (function MERGE): only the DSIM datset must be supplied. No full or delta save input is allowed.

The MERGE or RESTORE DELTA operation is abnormally terminated.

Supply suitable input datasets. If the function is RESTORE DELTA, rerun the job with RESTORE instead of RESTORE DELTA.

In a merge or delta restore operation, the database ID of an input save dataset is different from that specified in the ADARUN DBID parameter. Both database IDs are shown.

The merge or delta restore operation is abnormally terminated.

Supply the proper save tape or correct the ADARUN DBID parameter.

In a merge or delta restore operation, the input save datasets are not specified correctly:

• a delta save dataset is supplied instead of a full save dataset;

• a full save dataset is supplied instead of a delta save dataset;

• a gap exists in the DD-names/link-names for the delta save datasets;

• a save dataset was not created by a save operation with the Delta Save Facility;

• a save dataset was not created at Adabas 5.3 level or above;

• the input dataset does not contain a save dataset header record;

• the input dataset was not created by ADASAV.

The merge or delta restore operation is abnormally terminated. The DD-name/link-name of the offending input dataset is displayed.

Supply the proper input save tapes and rerun the job.

The original or unloaded Delta Save images (DSIM) dataset is required for processing an online save dataset in a MERGE or RESTORE DELTA operation, but it either

• has not been specified;

• has an incorrect status; or

• has been specified in the wrong logical sequence.

The MERGE or RESTORE DELTA operation is abnormally terminated.

Provide the correct DSIM dataset; rebuild it if necessary. Rerun the job.

The specified input full and delta save datasets do not cover a continuous sequence of save operations. Their delta save identifications (DSIDs) do not match, because one or more of the following is true:

• the full save numbers are not the same;

• the sequence of delta save numbers is not ascending without duplicates and gaps;

• in the sequence of full and delta save inputs, unloaded DSIM datasets are not specified directly after the associated online save.

• the dates and times are not ascending.

For a RESTORE DELTA operation without full save input, the DSID of the database takes part in this matching of DSIDs. The DSIDs matched have been displayed in previous messages.

The MERGE or RESTORE DELTA operation is abnormally terminated.

Provide the correct input save datasets in the correct sequence. Rerun the job.

A provided original or unloaded Delta Save images (DSIM) dataset is not the one associated with the specified input online save dataset. It does not contain the block images written during the online save operation that created the save dataset.

The DSIM dataset's full save number, delta save number, and database ID are shown. Further, the protection log number and protection log block number of the save operation's SYN1 checkpoint are displayed for both the DSIM dataset and the online save dataset. For associated online save and DSIM datasets, these SYN1-related numbers must be identical.

The MERGE or RESTORE operation is abnormally terminated.

Provide the right DSIM dataset and/or input save datasets. Rerun the job.

The delta merge/restore pattern specified in the PATTERN parameter does not match the input full and delta save datasets supplied.

The delta merge or delta restore operation is abnormally terminated.

Check and correct the PATTERN parameter and the job control statements. Rerun the job.

Another dataset was concatenated to one of the input datasets (the DD-name/link-name of the input dataset is shown). Input save dataset concatenation is allowed only if

• the function is RESTORE DELTA (not MERGE); and

• save datasets are concatenated to the last input save in logical sequence.

The MERGE or RESTORE DELTA operation is abnormally terminated.

Correct the specification of input datasets and rerun the job.

An I/O error occurred when Delta Save Facility tried to read the last block of the Delta Save images (DSIM) dataset. It is probably smaller than specified.

Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Correct the DSIMSIZE parameter or supply a correct DSIM dataset. If the function was PLCOPY, rebuild the DSIM dataset using the COPY function. Otherwise, rerun the COPY function.

The protection log and the Delta Save images (DSIM) dataset belong to different databases. The two database IDs are shown.

No online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Provide the correct protection log or rebuild the DSIM dataset. If the function was PLCOPY, rebuild the DSIM dataset using the COPY function. Otherwise rerun the COPY function.

The specified SYN1 checkpoint on the protection log was not found. The specified SYN1 position and the current position on the protection log are shown.

No online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified, a subsequent ADARES error abnormally terminates the function.

Supply matching protection log and parameter inputs, then rerun the job.

The first block of the protection log to be processed is not continuous with the last block processed before. Extracting block images for building the Delta Save images (DSIM) dataset must proceed in sequence. The current position on the protection log and the last position of the previous PLCOPY execution are shown.

No online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The PLCOPY function will continue processing. When terminating normally, the function will set condition code 4.

Rebuild the DSIM dataset using the COPY function.

The Delta Save images (DSIM) dataset is not large enough to hold all block images written during the accompanying online save operation. This DSIM dataset cannot be used for merging.

The DSIM dataset is set to an error status. The PLCOPY function will continue processing. When terminating normally, the function will set condition code 4.

Enlarge the DSIM dataset and rebuild it using the COPY function before performing the merge operation.

The Delta Save images (DSIM) dataset is not large enough to hold all block images written during the accompanying online save operation. This DSIM dataset cannot be used for merging.

The DSIM dataset is set to an error status. The COPY function will continue processing. When terminating normally, the function will set condition code 4. If no sequential output dataset was specified, a subsequent ADARES error abnormally terminates the function.

Augment the DSIM dataset and run the COPY function again before performing the merge operation.

The Delta Save images (DSIM) dataset was modified by another utility while

• the ADARES PLCOPY or COPY function was writing online save information extracted from the protection log to it; or

• the ADASAV MERGE function was reading online save information from it.

The DSIM dataset is inconsistent.

In ADASAV, the MERGE function is abnormally terminated. In ADARES, the DSIM dataset is set to an error status. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Avoid parallel usage of the DSIM dataset in the future. If the function was PLCOPY, rebuild the DSIM dataset using the COPY function. If the function was COPY, rerun the COPY function. If the function was MERGE, rebuild the DSIM dataset using the COPY function and rerun the MERGE function.

An I/O error occurred when the Delta Save Facility was trying to read a block from the Delta Save logging (DLOG) area. An ADAIOR error text is given. The affected Associator RABN is shown in decimal "dec-rabn" and hexadecimal "hex-rabn" formats.

The save function is abnormally terminated.

Determine the cause of the I/O error and eliminate it. Remove the DLOG area and install it again. Perform a full save operation.

An I/O error occurred when the Delta Save Facility was trying to write a block to the Delta Save logging (DLOG) area. An ADAIOR error text is given. The affected Associator RABN is shown in decimal "dec-rabn" and hexadecimal "hex-rabn" formats.

The save function is abnormally terminated.

Determine the cause of the I/O error and eliminate it. Remove the DLOG area and install it again. Perform a full save operation.

An error occurred when the Delta Save Facility was trying to open the Delta Save images (DSIM) dataset. An ADAIOR error text is given. The job control is probably incorrect, or the DSIMDEV parameter is missing or wrong.

In ADASAV, the function is abnormally terminated. In ADARES, no online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Check and correct the job control and/or the DSIMDEV parameter. If the function was ADARES PLCOPY, rebuild the DSIM dataset using the ADARES COPY function. Otherwise rerun the job.

An I/O error occurred when the Delta Save Facility was trying to read a block from the Delta Save images (DSIM) dataset. An ADAIOR error text is given. The affected DSIM RABN is shown in decimal "dec-rabn" and hexadecimal "hex-rabn" formats.

In ADASAV, the function is abnormally terminated. In ADARES, no more online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Determine the cause of the I/O error and eliminate it. Rebuild the DSIM dataset.

An I/O error occurred when the Delta Save Facility was trying to write a block to the Delta Save images (DSIM) dataset. An ADAIOR error text is given. The affected DSIM RABN is shown in decimal "dec-rabn" and hexadecimal "hex-rabn" formats.

In ADASAV, the function is abnormally terminated. In ADARES, no more online save information will be extracted from the protection log during this ADARES execution. Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Determine the cause of the I/O error and eliminate it. Rebuild the DSIM dataset.

An error occurred when the Delta Save Facility was trying to close the Delta Save images (DSIM) dataset. An ADAIOR error text is given.

In ADASAV, the function is abnormally terminated. In ADARES, the PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Determine the cause of the error and eliminate it.

An error occurred when the Delta Save Facility was trying to open an input save dataset. The DD/link name of the dataset and an ADAIOR error text are given. A job control statement is probably incorrect.

The function is abnormally terminated.

Determine the cause of the error and eliminate it. Rerun the job.

An error occurred when the Delta Save Facility was trying to read from an input save dataset. The DD-name/link name of the dataset and an ADAIOR error text are given.

The function is abnormally terminated.

Determine the cause of the error and eliminate it. If the save dataset turns out to be readable, rerun the job.

An error occurred when the Delta Save Facility was trying to close an input save dataset. The DD/link name of the dataset and an ADAIOR error text are displayed.

The function terminates abnormally.

Determine the cause of the error and eliminate it.

Sufficient virtual memory could not be obtained for Delta Save Facility processing. The number of bytes requested and obtained are shown in decimal and hex format.

In ADASAV, the function is abnormally terminated. In ADARES, building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Increase the partition/region of the job. If the function was ADARES PLCOPY, rebuild the DSIM dataset using the ADARES COPY function. Otherwise rerun the job.

The Delta Save Facility requires a database at Adabas version 5.3.3 or above. The requested function cannot be executed. The internal version indicator found in the GCB is shown in hexadecimal format (the indicator is "05xx" for Adabas version 5.1, "45xx" for version 5.2, and "C502" for version 5.3.2).

The function is abnormally terminated.

To use the Delta Save Facility, convert the database to Adabas version 5.3.3 or above.

The Delta Save logging (DLOG) area was installed by another, incompatible version of the Delta Save Facility. The internal version indicator and the version of the Delta Save Facility software are displayed in hexadecimal format.

The function is abnormally terminated.

Use a compatible version of the Delta Save Facility software, or remove the DLOG area and install it again.

The Delta Save images (DSIM) dataset was created by another, incompatible version of the Delta Save Facility. The internal version indicator and the version of the Delta Save Facility software are displayed in hexadecimal format.

In ADASAV, the function is abnormally terminated. In ADARES, building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Use a compatible version of the Delta Save Facility software, or rebuild the DSIM dataset using the ADARES COPY function.

An error was detected while processing a record from an input save dataset. Probably the save dataset is invalid. The DD/link name of the save dataset, an internal reason code, and the serial block number in decimal and hexadecimal are shown. The requested function cannot be completed.

The function is abnormally terminated.

Check for invalid concatenation of save datasets and correct it, if found. Consult your Software AG technical support representative, if necessary.

Either some important control information is not consistent for all records of an input save dataset, or the serial block numbers within an input save dataset are not in ascending order, increasing by one. Probably the save dataset is invalid. The DD/link name of the save dataset is shown.

The function cannot be completed, and is abnormally terminated.

Check for invalid concatenation of save datasets and correct it, if found. Consult your Software AG technical support representative, if necessary.

An error was detected in a protection log block processed by the Delta Save Facility. The protection log number, the block number and offset within the block, and an internal reason code are displayed in decimal format, the block number and offset also in hex format. A DSIM dataset cannot be built.

Building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Check for and correct any mistake in the specification of protection log datasets. Consult your Software AG technical support representative, if necessary.

An inconsistent block was encountered in the Delta Save logging (DLOG) area. The bad RABN is shown in decimal and hex format, plus an internal reason code. The delta save operation cannot be completed.

The delta save operation is abnormally terminated.

Consult your Software AG technical support representative to determine the cause of the error. Disable Delta Save logging, remove the DLOG area, and install it again. Perform a full save operation.

An inconsistent block was encountered in the Delta Save images (DSIM) dataset. The bad RABN is shown in decimal and hex format, plus an internal reason code. The requested Delta Save Facility function cannot be completed.

In ADASAV, the function is abnormally terminated. In ADARES, building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Consult your Software AG technical support representative to determine the cause of the error. Rebuild the DSIM dataset using the ADARES COPY function.

An inconsistent block was encountered in a file-specific extension of the Delta Save logging (DLOG) area. The file number, the RABN of the inconsistent block, and an internal reason code are shown. A delta save operation is not possible.

The delta save operation is abnormally terminated.

Consult your Software AG technical support representative to determine the cause of the error. Save and restore or reorder the file in question. Then rerun the delta save operation.

An internal error occurred in the indicated module at the specified offset. Some internal trace information as well as the register settings at the time of the error are shown. The requested Delta Save Facility function cannot be completed.

In ADASAV, the function is abnormally terminated. In ADARES, building the DSIM dataset is discontinued. The PLCOPY or COPY function will continue processing. When terminating normally, the function will set condition code 4. If no output dataset was specified for the COPY function, a subsequent ADARES error abnormally terminates the function.

Consult your Software AG technical support representative to determine the cause of the error.