Considerations for cabinet copies
The following considerations apply to cabinet copies:
- You can move a cabinet copy on disk to another volume without any problem.
Making cabinet copies on disk requires the use of the SPACE option. If you do not specify a value for SPACE, BMC AMI Copy issues a warning message and uses either the lesser of 100 cylinders or the value of MAXPRIM.
If you want to restrict cabinet copies on disk to a single volume data set, you can code the SPACE option on the OUTPUT command to make sure that cabinet copy does not span multiple volumes. For example, if you calculate that you need at least 10,000 cylinders, specify the following SPACE syntax in your job:
SPACE (10000,0) CYLThis specification will only complete allocation if 10,000 primary cylinders or tracks (as per ACP$OPTS) are found on a single volume.
- The STACK CABINET option, which specifies cabinet copies, and the DSSNAP YES option, which specifies Instant Snapshots, are mutually exclusive options, and you cannot use them on the same OUTPUT command. (You cannot make cabinet copies using the Instant Snapshot functionality.)
- If you specify a MAXTASKS value greater than 1 when you are making cabinet copies, you must ensure that the data sets have unique names. You can do this by using the symbolic variables &SEQ or &TASK.
- You should not make cabinet copies of the BMCXCOPY table. Instead, make a standard copy. (BMCXCOPY needs to be available for BMC AMI Recover to run, and you need BMC AMI Recover to recover from a cabinet copy.)
Version cleanup might cause a COPYPEND setting when you use cabinet copies.
If the last copy is registered in BMCXCOPY and OLDEST_VERSION is 255, BMC AMI Copy does not call DSNUTILB, and the clean up for versioning is not done. If additional ALTERs are done, they will fail.
To avoid this situation, insert a copy into SYSCOPY, run the BMC AMI Copy MODIFY command to delete all entries. DSNUTILB is called, and the cleanup is done.