The ADASAV utility saves and restores the contents of the database, specific files, or a file to or from a sequential dataset.
ADASAV should be run as often as required for the number and size of the files contained in the database, and the amount and type of updating.
For large databases, ADASAV functions may be run in parallel for the various disk packs on which the database is contained.
Special ADASAV functions are available for use with the Adabas Delta Save Facility. For more information, see the Adabas Delta Save Facility documentation.
For either RESTORE or RESTONL function operations, the Associator and Data Storage datasets must first be formatted. If either operation is interrupted, no database update activity should be attempted until the function has been successfully reexecuted.
RESTONL functions restore from a SAVE dataset created while the Adabas nucleus was active (that is, online); RESTORE functions restore from a SAVE dataset created while the Adabas nucleus was inactive (that is, offline).
RESTONL and RESTORE have the subfunctions GCB, FILES, and FMOVE:
Without a subfunction, RESTONL and RESTORE restore entire databases.
With the GCB subfunction, they restore the general control block, Associator RABNs 2-30 of the database, and specified files.
With the FILES subfunction, they restore one or more files into an existing database to their original RABNs.
With the FMOVE subfunction, they restore one or more files into an existing database to any free space, allowing changes to extent sizes.
If changes occurred during the online SAVE, the RESTONL function is followed automatically by the RESTPLOG function. RESTPLOG applies the updates that occurred during, and therefore were not included in, the online SAVE.
RESTPLOG is also executed following a RESTONL or RESTONL FILES function that ended before completing restoration of protection log (PLOG) updates. RESTPLOG applies the database updates not applied by the unsuccessful RESTONL function.
The SAVE function to save a database, or one or more files may be executed while the Adabas nucleus is active (online) or inactive (offline). If the Recovery Aid option is active, a SAVE database operation begins a new RLOG generation.
