• A CD-ROM volume archive file contains a bit image of an ISO9660 volume (or a modified ISO9660 for LIBRARY/MAINTENANCE). It may be created by COPYWRITE on the A-Series, or copied from a CD mounted on a CD unit. It may be created by products which run on Windows or other operating systems.
• COPYWRITE searches for a volume archive file when the LOCKEDFILE attribute is set to TRUE on the <source volume>.
• The title of the volume archive file is by default the name of the <source volume>, and the <primary family> of the WFL is used as it's location. If the volume archive is on another family, it may be specified using the FAMILYOWNER attribute.
• COPYWRITE searches for the volume archive first on KIND = CD, and if not found, KIND = DISK.
• If the <source volume> name is used as the INTNAME for a label equation, the TITLE attribute may be used to specify the title of volume archive file, and must give the complete path.
• COPYWRITE can access the LIBRARY/MAINTENANCE, LMCD, ISO9660 and JOLIET file systems within the volume. (LMCD is the name given to the underlying ISO9660 structures used for a LIBRARY/MAINTENANCE volume).
• The SCRATCHPOOL attribute is used to select the file system. If the SCRATCHPOOL attribute is not set, then the file system is the LIBRARY/MAINTENANCE file system. See Example 20.
• Set SCRATCHPOOL to ISO9660 to copy files from the ISO9660 file system. If A-Series Extended Attribute Records have been stored with the files, then the A-Series original file structure can be recreated. See Example 21 through Example 25.
• Set SCRATCHPOOL to JOLIET to copy files from the JOLIET file system.
• A SCRATCHPOOL of LMCD selects the underlying modified ISO9660 file system used to store the LIBRARY/MAINTENANCE logical file system. For example, the first file is called *FILE000 and contains the Tape Directory.
• The files to be copied are specified as A-Series titles in the COPY statement.
• The files in the root directory of an ISO9660 or JOLIET volume are non usercoded, and so are selected using '*'.
• If a directory *USERCODE/<username>/... exists on the JOLIET or ISO9660 partition, then it specifies the same file as (<username>)....
• The semantics of the <source file list> are the same as WFL, with some exceptions.
• Where there is no usercode on the <source file list>, and the COPY is running without a usercode, then only non-usercoded files are selected.
• Where there is no usercode on the <source file list>, and the COPY is running with a usercode, then only matching usercoded files are selected.
• A file may be copied from a volume archive with a different title, using the COPY <filename> AS <filename> syntax of WFL.
• The <destination volume> for the copy may be TAPE, DISK, CD or NULL. If the destination is TAPE, there may only be a single <source volume>.
• Only a PU may copy hazardous files, such as codefiles, from a CD-ROM volume archive.

Burning a CD Image on the MCP

• If there is a CD-R or CD-RW attached to the MCP system, then CopyWrite can burn the CD Images directly. It does this by calling the MCP Entrypoint BURN_CDR.
• Set the CDCOPIES attribute on the destination volume to a value greater than 0.

Using MULTIVOLUME CD Images

• If the total size of the files which are to be copied exceed the size of a CD Image, then it will fail, unless MULTIVOLUME is specified. A MULTIVOLUME copy is only available with Library/Maintenance CD Images. It is not available for hybrid CD images. When MULTIVOLUME is specified, a Volume Set consisting of multiple volumes is created.
• A Volume Set allows MCP files to be split across volume boundaries. This allows a file which is larger than the size of a physical CD to be copied and it allows more files than will fit on a physical CD to be copied together. When the MCP reads a file from the CD, and it reaches the end of volume, it requests the next volume in the Volume Set.
• When MULTIVOLUME is set, the title of the CD Image files generated are in the form <volume name>/nnn, where nnn is a number starting at 001, and represents the FAMILYINDEX. For example, the first volume of a Volume Set might be called FRED/001. As each volume is created, the FAMILYINDEX is incremented by 1.
• Each volume of a MULTIVOLUME volume set has a complete directory of all the files on the volume set. For example, a SUPERVISOR PDT command such as PDT IN *FRED/004 would show the same files as PDT IN *FRED/001. The PDT command shows the FAMILYINDEX on which each file begins.
• When copying files from a Volume Set which consists of a set of CD Images on Disk, the MULTIVOLUME attribute must be set along with LOCKEDFILE. The LOCKEDFILE attribute tells CopyWrite the files are CD Images on Disk, while the MULTIVOLUME attribute tells it that the title of the CD Images are in the form <destination volume name>/nnn.
• If the title of the volume is specified by label equation and MULTIVOLUME is set, then /nnn is appended to the title to find the volumes in the Volume Set.
• If the FAMILYINDEX attribute is specified when copying files from a Volume Set, then the volume with that FAMILYINDEX is opened to retrieve the Directory. If FAMILYINDEX is not specified and MULTIVOLUME is specified, then FAMILYINDEX=1 is assumed by default.
• If FAMILYINDEX is specified, then MULTIVOLUME is assumed by default.
• On MCPs before 4.7, the MULTIVOLUME attribute is not recognized. To create a MULTIVOLUME CD Image, set the FAMILYINDEX of the <destination volume> to a value greater than 1. To copy files from a MULTIVOLUME CD Image, set the FAMILYINDEX to select the volume which will be used to load the directory.
• If a Volume Set contains many files, and the file to be copied exists only on the final volume, then only the final volume needs to be online. This means that it is only necessary to have those volumes online which contain all or a part of the file being copied.

Specifying the Size of a CD Image

• The maximum size of a CD Image is set by default to 650 Megabytes. When this limit is reached, CopyWrite either reports an error, or if MULTIVOLUME is specified, it switches to the next volume in the Volume Set.
• The BLOCKSIZE attribute may be used to specify a different maximum CD Image size. It should be set as a <destination volume> attribute, and it's units are Megabytes. For example, setting the BLOCKSIZE=1, creates a CD Image with a maximum size of 1 Megabytes. If the BLOCKSIZE were set to 2000, then a CD Image with a maximum size of 2 Gigabytes would be created. This is larger than a physical CD, so it could not be burned on a CD. However, it is smaller than a physical DVD.
• If BLOCKSIZE is used in conjunction with MULTIVOLUME, then a set of files can be distributed across a set of volumes in which each volume has a specified maximum size. For example, if a set of MCP files had to be copied to a set of Floppy Disks, or sent by e-mail, then each volume of the Volume Set could be limited to 1 Megabyte.