General Information › General Restrictions

General Restrictions

Consider the following list of restrictions when planning for CA Disk. This list applies to the CA Disk product in general. Any specific function restrictions are documented with each function. This list helps you avoid problems caused when plans to process data do not include exception conditions.

• CA Disk never scratches data sets with the SYS1 first-level identifier unless SCRASYS1 was specified to allow it. This protects system data sets from accidental loss.

  Note: CA Disk does not do any checking before taking catalog update actions for SYS1 data sets.

• CA Disk does not back up all parts of SAS multi-volume data sets unless they were last processed by SAS release 9 or SAS release 8 at the current maintenance level.

  Newer releases of SAS follow IBM standards for multi-volume data sets. BACKUP, BACKUPCC, ARCHIVE and RESTORE can process these data sets.

• Multivolume VSAM, PS, and DA datasets in the MVS environment can span up to 59 volumes for the archive, backup and restore functions.
• The following data set names are reserved for CA Disk internal use and are not be processed by ARCHIVE and RESTORE functions:

  VTOC.xxxxxx
  

  DMSOS.Vxxxxxx
  

• In all functions except Archive, Backup and Restore, data sets controlled by the UCC6 program product are automatically bypassed by CA Disk with an identifying message. Since CA Disk does not support the format unique to the UCC6 PDS, copying one with CA Disk converts it to a conventional PDS (for example, restoring one from a backup copy).
• The sysparm UCC6CPDS allows other CA Disk functions to process them.
• The CA Disk functions of Archive, PDS Compress, Move, and Copy do not process data sets that have been selected implicitly if they are included in the APF list or linklist. These data sets must be selected explicitly for processing.
• User labels on disk or tape volumes are not supported. Do not confuse user labels with standard labels that are present on most tape and DASD volumes. CA Disk issues messages to identify any data set containing user labels, and bypasses processing for the data set.
• Data sets marked as unmovable are normally skipped. CA Disk does not do absolute track allocation or use track-image processing. Both of these are needed to ensure the integrity of data sets marked as unmovable. Sysparms are available that permit CA Disk to copy (and relocate) the data sets.
• CA Disk does not support the PANEXEC program product data set load libraries. These data sets are formatted like a PDS but have no valid directory. CA Disk cannot determine their internal format.
• Exclude DBRC Recon data sets from the Sequential Migrate function.
• Back up CA VIEW databases as a unit and do not update during the backup process. If a database spans multiple volumes, perform full volume backups. If the database needs to be restored, restore all data sets comprising the database from the same backup.