
IDCAMS BACKUP and RESTORE
Chapter 7. Running Jobs With BIM-EPIC 7-43
IDCAMS BACKUP and RESTORE
You can use BIM-EPIC to control the IDCAMS backup dataset produced by the BACKUP
function and used by the RESTORE function. IDCAMS provides for the backup dataset to
reside on either tape or disk.
Only prime dataset definitions are allowed. Therefore, multi-dataset tape groups are
specifically disallowed. For disk only, non-generation single-extent disk datasets
(WRK=YES) residing on CKD devices only may be used and truncation must be bypassed.
Each controlled tape dataset must be defined with a TLBL or DD statement and each
controlled disk dataset must be defined with a DLBL and abbreviated EXTENT statement (//
EXTENT SYS00n) or a DD statement with the OPTION=SYS00n parameter.
LUB allocation must be inhibited since IDCAMS requires SYS005 be used for the output
backup dataset and SYS004 for the input backup dataset.
Due to IDCAMS restrictions, you cannot use GDI to route a tape backup to disk or vise-versa.
When using disk for the backup dataset, a new extent must be allocated and the correct
assignment made before starting the backup function.
Many sample job streams for IDCAMS BACKUP and RESTORE are supplied when BIM-
EPIC is installed. Please see the BIM-EPIC Installation and System Guide, "BIM-EPIC
Sample Jobstreams".
Description
DSN Catalog
JCL Requirements
Restrictions
Examples
Kommentare zu diesen Handbüchern