DataManager Batch Processing and Reporting › The Archive/Restore Program (CAKSARCH) › The RESTORE Option

The RESTORE Option

The restore job is not intended to replace full database restores. Instead, it is provided as a means to restore specific tables used with DataManager.

Caution: If you run backups using a where_clause, be extremely careful when restoring tables. The contents of the designated table will be deleted before restore processing, and only archived records will be restored.

The RESTORE control statement identifies which backup table contains the definitions you want restored and the ddname of the file you want replaced. One run can process multiple RESTORE statements.

►►─ RESTORE ─┬───────────────────────────┬─ DD=ddname ─┬───────┬──────────────►◄
             └─ TBL=qualifier.tablename ─┘             └─ INS ─┘

where:

TBL= (optional)

Specifies the fully qualified data set name of the table to be restored. This program can restore to a new or existing table. If TBL= specifies a new table, the table is allocated before the archived table is restored. If TBL= is omitted, the table stored in the backup file will be used. Since DataManager stores definitions in four tables (IRDDESC, IRDTAB, ORDDESC and ORDTAB), submit four RESTORE statements to restore all these tables in one run.

DD=

Gives the ddname of the associated JCL DD statement that describes the backup data set. The information from this data set is copied into the TBL file specified in the RESTORE control statement. When restoring multiple tables, be sure each table has a unique ddname.

INS (optional)

If specified, RESTORE output will list the insert statements processed during this run. Omit INS to suppress this printed output.