Memorex LOCK - VERSION 2-24 Información técnica Pagina 313

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 568
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 312
Controlling IDCAMS Backup Datasets
User Reference
Connectivity Systems, Inc.—Copyright © 2006
Use Pursuant to Company Instructions
7-45
Additional Functionality
Controlling IDCAMS Backup Datasets
Description You can use BIM-EPIC to control the IDCAMS backup dataset. This
backup dataset is produced by the BACKUP command and is used by the
RESTORE command. IDCAMS allows the backup dataset to reside on
either tape or disk.
DSN Catalog 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. Truncation must be bypassed.
JCL
Requirements
There are several JCL requirements you must consider.
Each controlled tape dataset must be defined with a TLBL
statement or DD statement.
Each controlled disk dataset must be defined with a DLBL
statement and abbreviated EXTENT statement (// EXTENT
SYS00n) or a DD statement with OPTION=SYS00n.
LUB allocation must be inhibited since IDCAMS requires
SYS005 for the output backup dataset and SYS004 for the input
backup dataset.
Restrictions 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 must be made before
starting the BACKUP command.
Examples Many sample job streams for IDCAMS BACKUP and RESTORE are
supplied when BIM-EPIC is installed. See the BIM-EPIC Installation and
System Guide for additional information.
Vista de pagina 312
1 2 ... 308 309 310 311 312 313 314 315 316 317 318 ... 567 568

Comentarios a estos manuales

Sin comentarios