Document revision date: 15 July 2002

Before you can copy files to a disk volume, you must perform the following actions:

1. Prepare the volume, as explained in Section 9.3.
2. Because disks are random-access devices, and because files must be listed in directories, you must create a directory to contain your files on the disk volume after you initialize the volume.

Copying from Disks

The default format for files on disk volumes is Files--11 Structure Level 2. You can also initialize disks in the Files--11 Structure Level 1 format, which is the format used by other Compaq operating systems, including RSX--11M, RSX--11M-PLUS, RSX--11D, and IAS.

When you copy files from disks to standard-labeled disk volumes, the following items are not preserved:

• Directory specifications
• Individual file protections
• User identification codes (UICs)
• Creation times (but the dates are preserved)
• Revision and backup dates and times

You can use the COPY command to copy the highest version of all the files in your default directory to another directory on that volume.

Copying from Tapes

The default format for files on tapes is the standard-labeled volume. The OpenVMS system supports sequential, relative, and indexed files on disks, but you can copy only sequential files to standard-labeled disk volumes. The only valid record formats are variable-length and fixed-length.

When you copy files with tape file names from magnetic tape to disk, specify a standard OpenVMS file name for the output file name specification. If you do not specify an OpenVMS file name on output, your process receives the following error message:

RMS-F-FNM, error in file name

This message indicates that the tape file name is not a valid OpenVMS file name.

If you enter the COPY command with the /LOG qualifier, the system sends a message to the current SYS$OUTPUT device after each file has been copied. To verify that the files were successfully copied, use the DIRECTORY command.

Examples

1. CREATE/DIRECTORY DMA3:[PUBS] $ DEFINE P DMA3:[PUBS] $ COPY *.* P $ COPY [PRIMER]*.* P $ COPY [COMMANDS]*.* P

   
   The CREATE/DIRECTORY command in this example creates a disk directory file named [PUBS] on DMA3:, and the DEFINE command defines the logical name P as DMA3:[PUBS]. The COPY command copies the highest version of each file in the current default directory and in the directories [PRIMER] and [COMMANDS] to the newly created directory.

2. $ COPY *.* DMA5:[PRIVATE]

   
   For this example, assume that the disk device DMA5: has been allocated to your process and that a disk volume has been initialized and mounted on that device. Also assume that you have a directory called PRIVATE already created on that volume.

3. $ COPY/LOG MTA1:"%&*?!SKI! """ SEASON.DAT %COPY-S-COPIED, MTA1:[]"%&*?!SKI! """.;1 copied to WRKD:[MANUAL]SEASON.DAT;1 (120 records)

   
   The COPY/LOG command in this example copies the tape file %&*?!SKI!#" (# means space) to the file SEASON.DAT on the default disk and directory, WRKD:[MANUAL]. To copy the file to disk, you must specify a new file name. (The OpenVMS software provides defaults for segments of the file specification that are not specified.)
   Because this example uses the /LOG qualifier, the system returns a message that confirms the file was copied from the MTA1: tape volume; the message also tells how many records were copied.

4. $ COPY/LOG MTA0:*.* * %COPY-S-COPIED, MTA0:[]TASTETEST.DAT;1 copied to WRKD:[FOOD]TASTETEST.DAT;1 (249 records) %COPY-S-COPIED, MTA0:[]ALLAT;1 copied to WRKD:[FOOD]ALALL;1 (48 records) %COPY-S-NEWFILES, 2 files created

   
   In this example, the COPY/LOG command specifies wildcard characters for the file name and file type. Therefore, the system copies the only two files on the tape volume to the disk volume.

5. $ COPY/LOG MTA1:*.* [EX] %COPY-S-COPIED, MTA1:[].DAT;1 copied to WRKD:[EX]TEST.DAT21 records %COPY-E-OPENOUT, error opening WRKD:[EX]"%&*()!SKI! """.;1 as output -RMS-F-FNM, error in file name %COPY-W-NOTCOPIED, MTA1:[]"%&*()!SKI! """.;1 not copied %COPY-E-OPENOUT, error opening WRKD:[EX]"SANFRAN%%%""".;1 as output -RMS-F-FNM, error in file name %COPY-W-NOTCOPIED, MTA1:[]"SANFRAN%%%""".;1 not copied %COPY-S-COPIED, MTA1:[]OPENVMS_LONG$FILE_NAME.LONG_EXT;1 copied to WRKD$:[EX]OPENVMS_LONG$FILE_NAME.LONG_EXT;1 (80 records) %COPY-S-COPIED, MTA1:[]C6.JOU;1 copied to WRKD:[EX]C6.JOU;1 (4 records) %COPY-S-NEWFILES, 2 files created

   
   The COPY/LOG command string specifies that all files on the volume mounted on tape volume MTA1: are to be copied to the current default disk and directory WRKD:[EX]. However, the system does not copy files with tape file names, but, instead, returns an error message.

6. $ COPY/FTP sys$login:login.com - $_ system.bldg.corp.com"username password"::sys$login:login.tmp
   This example transfers the OpenVMS RMS file SYS$LOGIN:LOGIN.COM to the remote file SYS$LOGIN:LOGIN.TMP over a TCP/IP connection while specifying the user name and password on the remote system.

You can use the COPY command to copy files from a disk volume to a tape volume. The procedures are similar to those for copying files from one disk volume to another. One difference, however, is that magnetic tapes are sequential-access devices and do not have directories. You must set up (initialize and mount) a tape device before copying disk files to a tape volume. (The characteristics of tape files are described in Section 10.9.)

The entire set of Files--11 file names is supported for magnetic tapes. You can copy a disk file with the following file name to a magnetic tape volume without having to modify the file name:

THIS_IS$AN_OPENVMSLONG_FILE.LONG_TYPE

Although the OpenVMS system supports stream and variable with fixed-length control (VFC) records, it encodes these records in a variable-length format on standard-labeled volumes. Systems that are not OpenVMS do not distinguish stream records or VFC records from variable-length records; instead, they interpret both as variable-length records. Therefore, do not create either stream or VFC records on volumes that will be used for information interchange to a system that is not OpenVMS.

The following steps show how to use DCL commands to copy files from a default directory on a disk volume to a standard-labeled magnetic tape volume. Included in the steps are examples showing how to allocate, initialize, and use a magnetic tape to copy a set of your disk files.

How to Perform This Task

To copy files from a default directory on a disk volume to a standard-labeled tape volume, follow these steps:

1. First, allocate a drive as follows:

   $ ALLOCATE MT: TAPE_DEVICE %DCL-I-ALLOC _MARS$MTA2: allocated

   
   This ALLOCATE command requests the allocation of a tape drive whose name begins with MT. The logical name TAPE_DEVICE in this case refers to the MARS$MTA2: drive.
   The system response indicates that unit 2 on controller A was available and is now allocated to you. You can now physically load the tape on the drive. Be sure the write ring on the tape is in place; if it is not, you cannot write to the tape.

2. Initialize the tape by entering a command similar to the following:

   $ INITIALIZE TAPE_DEVICE: GMB001/PROTECTION=(GROUP:R,WORLD)

   
   The INITIALIZE command specifies the logical name for the volume (TAPE_DEVICE, which in this case refers to MTA2:) and the volume label for the tape volume (GMB001). The label can be no longer than six characters. The /PROTECTION qualifier defines a protection code restricting group access to read and allowing no world access.

3. Enter the MOUNT command to mount the volume and write files to it, as in the following example:

   $ MOUNT TAPE_DEVICE: GMB001 %MOUNT-I-MOUNTED, GMB001 mounted on _MTA2: $ COPY *.* TAPE_DEVICE:

   
   The MOUNT command specifies the device name and volume label of the volume on the device. The COPY command copies the highest version of each file in your default directory onto the tape. The file names, file types, and version numbers of the output files default to the same file names, file types, and version numbers as the input files.
   If you enter the COPY command with the /LOG qualifier, the system sends a message to the current SYS$OUTPUT device after it copies each file.

4. You can also use the DIRECTORY command to verify that the files were copied successfully.

   $ DIRECTORY TAPE_DEVICE:

   
   This DIRECTORY command lists the file names and file types of all files on the tape.

5. When you finish using the magnetic tape, dismount and deallocate it as follows:

   $ DISMOUNT TAPE_DEVICE: $ DEALLOCATE TAPE_DEVICE:

   
   If you do not dismount and deallocate the magnetic tape, the system does so automatically when you log out.

The following examples illustrate ways of copying files to tape volumes.

Examples

1. $ COPY *.* MTA2:

   
   For this example, assume that MTA2: has been allocated to your process and that a tape volume has been initialized and mounted on that device. The COPY command writes files to the MTA2: tape volume.
   The highest versions of all files in your default disk directory are copied to the tape volume. The file names, file types, and version numbers of the output files default to the same file names, file types, and version numbers as the input files.

2. $ COPY/LOG FORTAP.DAT MTA1:"%&*?!SKI! "" " %COPY-S-COPIED, WRKD:[MANUAL]FORTAP.DAT;1 copied to MTA1:[]"%&*?!SKI! """.;0 (120 records)

   
   In this command for copying from disk to tape, a tape file name is specified as the output file specification. Note that the trailing space in the file name %&*?!SKI!#"# (where # means space) is not present because trailing spaces are not significant in tape names.

3. $ COPY/LOG OPENVMS_LONG$FILE_NAME.LONG_EXT MTA1: %COPY-S-COPIED, WRKD:[MANUAL]OPENVMS_LONG$FILE_NAME_EXT;1 copied to MTA1:OPENVMS_LONG$FILE_NAME.LONG_EXT;1 (80 records)

   
   In this example, a long file name with a long file type is copied to the tape volume MTA1: with the same file name and type as on the disk volume.

4. $ COPY/LOG %%.JOU;* MTA1:*.* %COPY-S-COPIED, WRKD:[MANUAL]C6.JOU;1 copied to MTA1:[]C6.JOU;1 (4 records)

   
   In this example, all files with a two-character file name and a file type of .JOU are copied to the tape volume MTA1: with the same file name and type as on the disk volume. Version numbers are preserved.

When you are copying to or from a tape and that tape reaches the end, the system suspends processing and sends a request to mount the next tape in the volume set. An operator communication manager (OPCOM) message similar to the following one is displayed at the terminal:

%%%%%%%%%%% OPCOM, 14-MAY-2000 15:23:31.78 %%%%%%%%%%% request 3, from user PLAW MOUNT new relative volume 2 (DW0QT2) on MTA1:

If automatic volume switching is disabled or if the tape file system cannot mount a given volume, you might need to mount a continuation volume in a volume set. See Section 9.8.2 for information about mounting continuation volumes.

10.10.4 Using the Exchange Utility (EXCHANGE)

The Exchange utility (EXCHANGE) converts the format of files, as appropriate, when copying files between volumes of different structures. EXCHANGE recognizes all Files-11 and RT-11 disk volumes on OpenVMS devices, as well as all DOS-11 and RT-11 formatted volumes on 9-track tape devices.

For more information about how to use EXCHANGE and for a description of all EXCHANGE commands, qualifiers, and parameters, refer to online help or the archived manual OpenVMS Exchange Utility Manual.

10.10.5 Using the EXCHANGE/NETWORK Command

Use the DCL command EXCHANGE/NETWORK to transfer files to and from operating systems that do not support OpenVMS file organizations. This transfer occurs over a DECnet communications link that connects nodes that are both OpenVMS and not OpenVMS operating systems.

Use the EXCHANGE/NETWORK command to perform the following operations:

• Transfer files between an OpenVMS node and a node that is not OpenVMS.
• Transfer a group of input files to a group of output files.
• Transfer files between two nodes that are not OpenVMS, provided those nodes share DECnet connections with the OpenVMS node that issues the EXCHANGE/NETWORK command.

For details on using the EXCHANGE/NETWORK command, refer to online help or the OpenVMS DCL Dictionary.

How to Perform This Task

To issue the EXCHANGE/NETWORK command, use the following format:

EXCHANGE/NETWORK input-filespec[,...] output-filespec

where:

input-filespec	Specifies the name of an existing file to be transferred. (Wildcard characters are allowed.)
output-filespec	Specifies the name of the output file into which the input is to be transferred.

Example

$ EXCHANGE/NETWORK MYSYS_FILE.DAT FOO::FOREIGN_SYS.DAT

The command in this example transfers the file MYSYS_FILE.DAT, which is located in the current default device and directory, to the file FOREIGN_SYS.DAT on node FOO, which is not an OpenVMS node. By default, the command automatically determines whether the transfer method should be block or record I/O.

10.11 Creating a CD-ROM

CD-ROM is an alternative vehicle for distributing or backing up files. To create a CD-ROM you need a CD-Recordable (CD-R or CD-RW) drive and a blank CD-R disk. CD-R and CD-RW drives use a laser beam to write (or burn) data to a blank CD-R disk. This differs from the audio compact discs you buy, which are pressed in a factory from a glass master. A CD-R disk is "write once." This means you can write data on it one time only. It is not rewritable.

Read and write-once support for CD-R and CD-RW drives is introduced in OpenVMS Alpha Version 7.3-1 on the AlphaServer DS25 system. OpenVMS supports only qualified CD-R and CD-RW drives. For more information on Alpha systems and the drives they support, refer to the appropriate page at the following Web site:

http://www.compaq.com/alphaserver/configure.html

The write process creates a CD-ROM in Files-11 format. Any supported CD-ROM reader on a computer running OpenVMS will be able to read the CD-ROMs you create.

You cannot use COPY commands to transfer files from a hard drive to a CD-R disk. There is a two step process you must follow and a special program called CDRECORD.COM¹ that you must use.

The first step is to create a logical disk and container file on your hard drive. Organize the directory structure, volume information, and files on the logical disk as you want them to appear on the CD-ROM.

The second step is to run CDRECORD.COM to transfer the contents of the container file to a blank CD-R disk. CDRECORD.COM provides a set of commands you can use to:

• Display information about the CD-R drive
• Set up the logical disk and container file
• Write to a CD-R disk
• Reuse an existing container file
• View online help

To view online help about CDRECORD.COM, enter the HELP command at the DCL prompt ($), as follows:

$ @SYS$MANAGER:CDRECORD HELP

10.11.1 Preparation

When you are ready to create a CD-ROM, make sure you have:

• A CD-R or CD-RW drive connected to a system running OpenVMS Alpha Version 7.3-1 or later.
• A blank CD-R disk.
• The device name of the CD-R drive (DQnn). If you do not know the device name, use the SHOW DEVICE DQ command. The device name for a CD-R drive is typically DQA0, DQA1, DQB0, or DQB1.
• The DIAG, PHY_IO, and SYSPRV privileges. If you want to run at a higher priority level, you need the ALTPRI privilege as well.

To verify that you have the device name for the drive, enter the INQUIRE command followed by the device name. For example:

$ @SYS$MANAGER:CDRECORD INQUIRE DQA1:

The system verifies that DQA1 (or whatever device name you entered) is a CD-R or CD-RW drive. It also displays the read and write speed of the drive.

10.11.2 Setting Up a Logical Disk and Container File

You set up the structure and data you want on the hard drive, then use CDRECORD.COM to transfer everything to a blank CD-R disk. You do this by first creating a logical disk on the hard drive that you can mount, dismount, and generally treat as an actual disk. You also create a container file because CDRECORD.COM needs to work with the files on the logical disk as a single entity.

For best performance, clean up and defragment the hard drive on which you will create the logical disk and container file. For more information, see BACKUP/IMAGE in the OpenVMS System Management Utilities Reference Manual: A--L.

Use the SETUP command in the following format to create a logical disk and a container file:

$ @SYS$MANAGER:CDRECORD SETUP filename LDAn: label nnnn

where:

filename is the name of the container file. Follow the usual rules for naming files and include a file extension.

LDAn: is the name of the logical disk and can have a value of LDA1 to LDA9999.

label is the volume label you want to give the logical disk and the CD-ROM you will write. Follow the usual rules for assigning volume labels.

nnnn is the number of 512-byte blocks you want to allocate for the container file. The number must be a multiple of 4. The default value is 1250000 (640 MB).

The container file must not be larger than the available space on the CD-R disk you are going to write to. Also, check the available space on your hard drive to make sure you have enough room for the container file.

In the following example:

$ @SYS$MANAGER:CDRECORD SETUP TESTFILE.DSK LDA1: FRED 1250000

TESTFILE.DSK is the container file name and extension.

LDA1: is the device name of the logical disk.

FRED is the volume label of the logical disk and the CD-ROM you will write.

1250000 is the space (in 512-byte units) that will be allocated on the hard drive for the container file.

Once you have created a logical disk and container file on your hard drive, you can populate the logical disk with directories and files.

	privacy and legal statement
6017PRO_044.HTML