Is the CTLFILE ignored when using the UNSTACK control statement?

Products

• CA 1 Flexible Storage
• CA 1 Tape Management - Copycat Utility

Issue/Introduction

When using COPYCAT's FILECOPY the CTLFILE is ignored when also using the UNSTACK control statement.

 

Environment

 

 

Resolution

When running Copycat's FILECOPY for a multi-file or multi-file/multi-volume dataset and using the CTLFILE and UNSTACK control statements, the CTLFILE is ignored.  The first file will not be a dummy file coded on the CTLFILE control statement.  The CTLFILE is only used when you are consolidating multiple files.   CTLFILE can not be used with UNSTACK, but can be used with MERGE.

 

CTLFILE

Specifies the 1 to 44 character data set name which identifies a dummy file that is created as the first file on the tape. Files that match this data set name will not be copied if ALL is specified by the FILES parameter.

If DUPLEX=YES is specified, the duplex copy will also have a control file with this same name, unless CTLFILE2 is specified.

 

  

UNSTACK

Represents a special control directive designed for use with virtual tape systems. The output files are each written to a separate volume. This allows the virtual system to physically stack the files within the virtual tape system while giving the external appearance of each file being on a separate volume. UNSTACK and MERGE processing of any kind are mutually exclusive.