Using CD-ROM Volume Archives on a Cataloging System

• The MCP does not allow a volume with KIND = CD to be added to the volume library.
• COPYWRITE uses KIND=PACK to represent CD-ROM volume archives. Since a DISK or PACK disk family cannot have a SERIALNO with alphabetic characters, a serial number convention which uses an alphabetic character in the serial number can be used to differentiate between a CD-ROM volume and a disk or pack family.
• The COPY&BACKUP command adds backup references to a CDROM volume archive, before the archive has been burned onto CD media. The Cataloging function is associated with the destination volume being created.
• The COPY&CATALOG command adds backup references to a CDROM (or TAPE or DISK) volume archive, after it has been created. The Cataloging function is associated with the source volume which has been created. The destination volume is not relevant to the Cataloging actions, and is often NULL.
• The ADD&CATALOG command is almost identical to the COPY&CATALOG command.

COPY & BACKUP

• The COPY&BACKUP option copies files to a CD-ROM volume archive, and for each file creates a backup reference to the volume archive, using the SERIALNO specified in the COPY statement. See Example 111.
• It is only available for volume archives which have a LIBRARY/MAINTENANCE file system, and is not allowed when doing a COPY and DISCARD.
• With a COPY&BACKUP a <source volume> must be specified, and there must only be a single <source volume>. The <source volume> specifies the volume name of the source files, and is needed to add the backup references.
• The <source volume> may only have a KIND of  DISK or PACK.
• The SERIALNO attribute must be set on the <destination volume>.
• The SERIALNO is used as a key to search the Volume Library. If an entry exists with the same SERIALNO, but a volume name different from the <destination volume>, an error is reported.
• If the SERIALNO does not exist in the volume library, it is created using a VOLUME ADD <destination volume>(KIND=PACK,SERIALNO="<serialno>").
• If the SECURITYTYPE = CONTROLLED the volume is marked as DESTROYED. This could be used by a site to indicate that the backup reference to the CD-ROM volume archive has been added to the file, but the CD-ROM volume has not yet been created, and may be invalid. A backup reference on a file should indicate that a safe backup exists. If the CD-ROM volume archive is never burned, then the backup reference gives false information. METALOGIC FAMILYMANAGER does not use COPY&BACKUP for this reason, instead it uses the COPY&CATALOG function, to add the reference when the volume has been burned and remounted on the A-Series.
• A backup reference can only be added to a file if a system is Cataloging, the volume it exists on has been added to the Volume Library, and the file is Cataloged.

COPY & CATALOG

• The COPY&CATALOG option copies files from a <source volume> and adds backup references into catalogued file entries. See Example 112.
• The <source volume> attribute SERIALNO gives the SERIALNO which will be used as the backup reference.
• If a Volume Library entry exists for this serial number, then the volume name must match the <source volume> name. If an entry with this serial number does not exist in the Volume Library, then it is added if the volume is either TAPE or CDROM. A volume library entry is not added for DISK or PACK families.
• If the <source volume> is a CDROM, and this is the first time the volume has been mounted (indicated by null attributes in the Volume Library entry), then the Volume Library attributes CREATIONDATE, SITEID and SAVEFACTOR are updated. The CREATIONDATE is set from the CD volume attributes while the SITEID is set from Time(23). If a SAVEFACTOR attribute is specified on the <source volume>, it is used to update the SAVEFACTOR of the Volume Library entry, otherwise a default of 30 is used.
• The FAMILYOWNER attribute of the <destination volume> specifies the volume name where the file entries which are to be updated should exist. Note, that the <destination volume> name is not relevant to the Catalog action.
• A backup reference to a volume with the name and SERIALNO of the <source volume> is added to each <filename> ON <FAMILYOWNER family>, where the <filename> is the name of each file copied from the <source volume>.
• The COPY&CATALOG option is typically used with a <destination volume> of NULL. The files are copied from the <source volume> and discarded, however, a backup reference is added.
• METALOGIC FAMILYMANAGER uses this method when backing up to CDs. It generates the CD images, and AUTOUNLOADS them to be burned onto CD media. It then waits for the CD to be mounted on the CD unit. It performs a COPY&CATALOG to NULL, which verifies the volume, since the MCP reads and checksums every record of every file, and a backup reference to the CD volume is then added to each file on the FAMILYOWNER family.
• If the SINGLEUNIT attribute is set on the <destination volume>, then both backup reference entries are updated to reference the <source volume>. These backup references are sometimes referred to as the onsite and offsite backup reference.
• The COPY&CATALOG will always attempt to create a backup entry, whereas an ADD&CATALOG will fail unless there is a matching file entry already in the Catalog. METALOGIC MERGETAPE uses the ADD&CATALOG option because there must always be a file entry for the files with which it is dealing.
• If a COPY&CATALOG finds that no file entry exists on the FAMILYOWNER family for a file being copied from a <source volume>, it will create a file entry. The procedure CreateNonResidentEntry does this by creating an empty file with matching genealogy, updating the backup references, and then removing the file.
• The COPY&CATALOG feature can be used to create backup references to TAPE, DISK and PACK volumes as well as CDROM volumes.
• It can be used to create a database of files on offline volumes. For example, take all the UNISYS release CDs for a particular release, say 42.1. RC a spare disk (or use a small Memory Disk), as RELEASE421, and add it to the Volume Library. For each release CD, COPY&CATALOG *= FROM <release cd name>(CD,SERIALNO="<serialno>") TO NULL(CD,HOSTNAME=LOCAL,FAMILYOWNER=RELEASE421). After all the CDs have been copied, the disk can be RCed. Now an ODT PD - command, or better still FLEX, can be used to search for files for that release on the offline volume called RELEASE421, and the backup entry refers to the CD which contains the file contents.
• While the COPY&CATALOG is typically used with a NULL destination, a CDROM volume archive, with optional data transformation, may be a useful destination. A site may create a LIBRARY/MAINTENANCE CD, and then remount the CD, do a COPY&CATALOG to verify the CD volume and add the backup references, and copy to a destination with SCRATCHPOOL=WINDOWSNT, so that another CD image is generated from the verified LIBRARY/MAINTENANCE CD, suitable for loading onto Windows.

ADD & CATALOG

• The ADD&CATALOG option is the same as the COPY&CATALOG option, except that ADD&CATALOG will fail if a matching Catalog file entry does not already exist on the FAMILYOWNER family. See Example 113.

Creating a Hard Link to a CD Volume

This feature is provided to allow FamilyManager and Flex to to access CD Volumes on different families.

When FamilyManager is used to backup files to CD Images, the CD Images are stored on the Family specified by the FLEX_CWIMAGE configuration variable established when FamilyManager was installed.

When Flex Inquiry is used to load a Non-Resident file which is backed up on a CD Image, it assumes that the CD Image is located on the FLEX_CWIMAGE Family.

CopyWrite allows the creation of a Hard Link to a CD Image.

A Hard Link is a Non Resident File Entry on a Family, which contains a Backup Reference to another Family on which the actual file is Resident.

This feature allows FamilyManager and Flex to assume that CD Images are on theFLEX_CWIMAGE Family, but have them actually resident somewhere else.

In CopyWrite, a Hard Link is created by Label Equating the Internal File Name, CDIMAGEHARDLINK and specifying theFAMILYNAME on which the Hard Link should be created.

WFL Task T;T(File CDImageHardLink(FamilyName=CDImage));
Copy A to Fred(CD,HostName=Local)[T]
#RUNNING 4614
#BOT 4615  (NFT)WFLCODE
#BOT 4616  (NFT)FILE/TRANSFER
#BOT 4617  (NFT)FILE/TRANSFER/SERVICES
#4617 Metalogic CopyWrite Version 50.500.01 was compiled at 16:00:6 
      on the 30th April 2004 (MCP 48.189.9445)
#4617 FRED will be an A Series LIBRARY MAINTENANCE Volume
#4617 <1> (NFT)A copied to FRED
#4617 Formatting CDROM Volume FRED
#4617 PK504 (NFT)FRED REMOVED ON CDIMAGE
#4617 Hard Link (NFT)FRED created on CDIMAGE to DEV PK [000506]
#4617 FRED in (NFT)FRED ON DEV prepared by NFT and published by NFT using
     Metalogic COPYWRITE
#4617 ----- Summary for LIBRARY MAINTENANCE-----
#4617 Created 1 files and 1 directory.
#4617 Transferred 6120 bytes to the CDROM volume image.
#EOT 4617  (NFT) (NFT)FILE/TRANSFER/SERVICES
#EOT 4616  (NFT) (NFT)FILE/TRANSFER
#EOT 4615  (NFT) (NFT)WFLCODE

The CD Image is created on the FamilyName of the Task, and the Hard Link is created on the FamilyName specified by the CDIMAGEHARDLINK Label Equation.

LFiles Fred on CDImage : Cat
#RUNNING 4619
#?
ON CDIMAGE
(NFT) : DIRECTORY
. FRED : PROMBURNERDATA NON-RESIDENT

CATALOG ENTRY 1 (NON-RESIDENT) PROMBURNERDATA
TIMESTAMP=05/03/2004 09:46:02 CYCLE=1 VERSION=0
LASTACCESSDATE =05/03/2004 09:46:01
BACKUP #1 IS PACK, SERIALNO 000506
BACKUP #2 IS PACK, SERIALNO 000506

FamilyManager provides syntax which allows files to be backed up to a CD Image on a specific family, and internally it uses this label Equation to create the hard Link back to theFLEX_CWIMAGE family.

When CopyWrite is called to copy a File from a CD Image, and the CD Image it finds first is actually a Hard Link, CopyWrite chases the link to the Resident CD Volume, and copies the file from there.