This section describes how an ADASAV SAVE database or SAVE DELTA execution can be restarted after failure. The specific actions to be performed depend on the type of failure.
This document covers the following topics:
If the ADASAV utility terminates with an error message and user abend
34 or 35:
Determine and correct the cause of the error.
If the save operation was performed online, reset the DSIM dataset (see below).
Resubmit the save job.
If the ADASAV utility terminates abnormally with a system ABEND or a user ABEND other than 34 or 35:
For Offline Save Operation
Determine and correct the cause of the error.
Remove the DIB entry of the ADASAV job, using ADADBS functions OPERCOM DDIB and RESETDIB.
Resubmit the save job.
For Online Save Operation
Determine and correct the cause of the error.
Reset the nucleus online dump status, using the ADADBS OPERCOM RDUMPST command or the corresponding Adabas Online System function.
Delete the user queue element (UQE) of ADASAV in the nucleus, using the ADADBS functions OPERCOM DUQ and OPERCOM STOPU or the corresponding Adabas Online System functions.
Remove the DIB entry of the ADASAV job, using the ADADBS OPERCOM DDIB and RESETDIB commands, or the corresponding Adabas Online System functions.
Reset the DSIM dataset (see below).
Resubmit the save job.
After an interrupted online save operation, the DSIM dataset must be reset to prepare it for another save/copy/merge cycle.
This can be done using the ADAFRM function DSIMRESET FROMRABN=1,SIZE=1B. See DSIMRESET: Reset the DSIM Dataset .
Software AG recommends that you specify the DSIM dataset for exclusive use by the ADAFRM utility to avoid accidentally destroying information in a DSIM dataset currently in use by another utility. For the other utilities (ADASAV and ADARES), the DSIM dataset must be specified for shared-update use.
