 |
HP OpenVMS DCL Dictionary
HP OpenVMS DCL Dictionary
When you use the /LOG qualifier, the COPY command displays the
following for each copy operation:
- The file specifications of the input and output files
- The number of blocks or the number of records copied (depending on
whether the file is copied on a block-by-block or record-by-record
basis)
- The total number of new files created
/MODIFIED
Modifies the time value specified with the /BEFORE or the /SINCE
qualifier. The /MODIFIED qualifier selects files according to the dates
on which they were last modified. This qualifier is incompatible with
the /BACKUP, /CREATED, and /EXPIRED qualifiers, which also allow you to
select files according to time attributes. If you specify none of these
four time modifiers, the default is the /CREATED qualifier.
/OVERLAY
/NOOVERLAY (default)
Requests that data in the input file be copied into the existing
specified file, overlaying the existing data, rather than allocating
new space for the file. The physical location of the file on disk does
not change; however, for RMS indexed and relative files, if the output
file has fewer blocks allocated than the input file, the copy fails
giving an RMS-E-EOF error.
The /OVERLAY qualifier is ignored if the output file is written to a
non-file-structured device.
/PROTECTION=(ownership[:access][,...])
Specifies protection for the output file.
- Specify the ownership parameter as system (S), owner (O),
group (G), or world (W).
- Specify the access parameter as read (R), write (W),
execute (E), or delete (D).
The default protection, including any protection attributes not
specified, is that of the existing output file. If no output file
exists, the current default protection applies.
For more information on specifying protection codes, refer to the
HP OpenVMS Guide to System Security.
/READ_CHECK
/NOREAD_CHECK (default)
Reads each record in the input files twice to verify that it has been
read correctly.
/REPLACE
/NOREPLACE (default)
Requests that, if a file exists with the same file specification as
that entered for the output file, the existing file is to be deleted.
The COPY command allocates new space for the output file. In general,
when you use the /REPLACE qualifier, include version numbers with the
file specifications. By default, the COPY command creates a new version
of a file if a file with that specification exists, incrementing the
version number. The /NOREPLACE qualifier signals an error when a
conflict in version numbers occurs.
/SINCE[=time]
Selects only those files dated on or after the specified time. You can
specify time as absolute time, as combination of absolute and delta
times, or as one of the following keywords: BOOT, LOGIN, TODAY
(default), TOMORROW, or YESTERDAY. Specify one of the following
qualifiers with the /SINCE qualifier to indicate the time attribute to
be used as the basis for selection: /BACKUP, /CREATED (default),
/EXPIRED, or /MODIFIED.
For complete information about specifying time values, refer to the
OpenVMS User's Manual or the online help topic DCL_Tips (subtopic Date_Time).
/STYLE=keyword
Specifies the file name format for display purposes.
The valid keywords for this qualifier are CONDENSED and EXPANDED.
Descriptions are as follows:
Keyword |
Explanation |
CONDENSED (default)
|
Displays the file name representation of what is generated to fit into
a 255-length character string. This file name may contain a DID or FID
abbreviation in the file specification.
|
EXPANDED
|
Displays the file name representation of what is stored on disk. This
file name does not contain any DID or FID abbreviations.
|
The keywords CONDENSED and EXPANDED are mutually exclusive. This
qualifier specifies which file name format is displayed in the output
message, along with the confirmation if requested.
File errors are displayed with the CONDENSED file specification unless
the EXPANDED keyword is specified.
Refer to the OpenVMS User's Manual for more information.
/TRUNCATE (default)
/NOTRUNCATE
Controls whether the COPY command truncates an output file at the
end-of-file (EOF) when copying it. This operation can only be used with
sequential files.
By default, the actual size of the input file determines the size of
the output file. If you select /NOTRUNCATE, the allocation of the input
file determines the size of the output file.
/VOLUME=n
Places the output file on the specified relative volume number of a
multivolume set. By default, the COPY command places the output file
arbitrarily in a multivolume set.
/WRITE_CHECK
/NOWRITE_CHECK (default)
Reads each record in the output file after it is written to verify that
the record copied successfully and that the file can be read
subsequently without error.
Note
Some hardware devices, such as TK50 tape drives, verify data integrity
as part of their hardware function. For devices such as these, you do
not need to use /WRITE_CHECK. For information about which devices
provide automatic write checking, consult your hardware documentation.
|
Examples
#1 |
$ COPY TEST.DAT NEWTEST.DAT
|
In this example, the COPY command copies the contents of the file
TEST.DAT from the default disk and directory to a file named
NEWTEST.DAT on the same disk and directory. If a file named NEWTEST.DAT
exists, the COPY command creates a new version of the file.
#2 |
$ COPY ALPHA.TXT TMP
$ COPY ALPHA.TXT .TMP
|
In this example, the first COPY command copies the file ALPHA.TXT into
a file named TMP.TXT. The COPY command uses the file type of the input
file to complete the file specification for the output file. The second
COPY command creates a file named ALPHA.TMP. The COPY command uses the
file name of the input file to name the output file.
#3 |
$ COPY/LOG TEST.DAT NEW.DAT;1/REPLACE
%COPY-I-REPLACED, DKA0:[MAL]NEW.DAT;1 being replaced
%COPY-S-COPIED, DKA0:[MAL]TEST.DAT;1 copied to DKA0:[MAL]NEW.DAT;1 (1 block)
|
In this example, the /REPLACE qualifier requests that the COPY command
replace an existing version of the output file with the new file. The
first message from the COPY command indicates that it is replacing an
existing file. The version number in the output file must be explicit;
otherwise, the COPY command creates a new version of the file NEW.DAT.
#4 |
$ COPY *.COM [MALCOLM.TESTFILES]
|
In this example, the COPY command copies the highest versions of files
in the current default directory with the file type .COM to the
subdirectory MALCOLM.TESTFILES.
#5 |
$ COPY/LOG *.TXT *.OLD
%COPY-S-COPIED, DKA0:[MAL]A.TXT;2 copied to DKA0:[MAL]A.OLD;2 (1 block)
%COPY-S-COPIED, DKA0:[MAL]B.TXT;2 copied to DKA0:[MAL]B.OLD;2 (1 block)
%COPY-S-COPIED, DKA0:[MAL]G.TXT;2 copied to DKA0:[MAL]G.OLD;2 (4 blocks)
%COPY-S-NEWFILES, 3 files created
|
In this example, the COPY command copies the highest versions of files
with file types .TXT into new files. Each new file has the same file
name as an existing file, but a file type .OLD. The last message from
the COPY command indicates the number of new files that have been
created.
#6 |
$ COPY/LOG A.DAT,B.MEM C.*
%COPY-S-COPIED, DKA0:[MAL]A.DAT;5 copied to DKA0:[MAL]C.DAT;11 (1 block)
%COPY-S-COPIED, DKA0:[MAL]B.MEM;2 copied to DKA0:[MAL]C.MEM;24 (58 records)
%COPY-S-NEWFILES, 2 files created
|
In this example, the two input file specifications are separated with a
comma. The asterisk (*) wildcard character in the output file
specification indicates that two output files are to be created. For
each copy operation, the COPY command uses the file type of the input
file to name the output file.
#7 |
$ COPY/LOG *.TXT TXT.SAV
%COPY-S-COPIED, DKA0:[MAL]A.TXT;2 copied to DKA0:[MAL]TXT.SAV;1 (1 block)
%COPY-S-APPENDED, DKA0:[MAL]B.TXT;2 appended to DKA0:[MAL]TXT.SAV;1 (3 records)
%COPY-S-APPENDED, DKA0:[MAL]G.TXT;2 appended to DKA0:[MAL]TXT.SAV;1 (51 records)
%COPY-S-NEWFILES, 1 file created
|
In this example, the COPY command copies the highest versions of all
files with the file type TXT to a single output file named TXT.SAV.
After the first input file is copied, the messages from the COPY
command indicate that subsequent files are being appended to the output
file.
Note that, if you use the /NOCONCATENATE qualifier in this example, the
COPY command creates one TXT.SAV file for each input file. Each TXT.SAV
file has a different version number.
#8 |
$ COPY MASTER.DOC DKA1:[BACKUP]
|
In this example, the COPY command copies the highest version of the
file MASTER.DOC to the device DKA1. If no file named MASTER.DOC exists
in the directory [BACKUP], the COPY command assigns the version number
of the input file to the output file. You must have write (W) access to
the directory [BACKUP] on device DKA1 for the command to work.
#9 |
$ COPY SAMPLE.EXE DALLAS::DISK2:[000,000]SAMPLE.EXE/CONTIGUOUS
|
In this example, the COPY command copies the file SAMPLE.EXE on the
local node to a file with the same name at remote node DALLAS. The
/CONTIGUOUS qualifier indicates that the output file is to occupy
consecutive physical disk blocks. You must have write (W) access to the
device DISK2 on remote node DALLAS for the command to work.
#10 |
$ COPY *.* PRTLND::*.*
|
In this example, the COPY command copies all files within the user
directory at the local node to the remote node PRTLND. The new files
have the same names as the input file. You must have write (W) access
to the default directory on remote node PRTLND for the command to work.
#11 |
$ COPY BOSTON::DISK2:TEST.DAT;5
_To: DALLAS"SAM SECReturn"::DISK0:[MODEL.TEST]TEST.DAT/ALLOCATION=50
|
In this example, the COPY command copies the file TEST.DAT;5 on the
device DISK2 at node BOSTON to a new file named TEST.DAT at remote node
DALLAS. The /ALLOCATION qualifier initially allocates 50 blocks for the
new file TEST.DAT at node DALLAS. The access control string SAM
SECReturn is used to access the remote directory.
#12 |
$ MOUNT TAPED1: VOL025 TAPE:
$ COPY TAPE:*.* *
|
In this example, the MOUNT command requests that the volume labeled
VOL025 be mounted on the magnetic tape device TAPED1 and assigns the
logical name TAPE to the device.
The COPY command uses the logical name TAPE as the input file
specification, requesting that all files on the magnetic tape be copied
to the current default disk and directory. All the files copied retain
their file names and file types.
#13 |
$ ALLOCATE CR:
_CR1: ALLOCATED
$ COPY CR1: CARDS.DAT
$ DEALLOCATE CR1:
|
In this example, the ALLOCATE command allocates a card reader for
exclusive use by the process. The response from the ALLOCATE command
indicates the device name of the card reader, CR1.
After the card reader is allocated, you can place a deck of cards in
the reader and enter the COPY command, specifying the card reader as
the input file. The COPY command reads the cards into the file
CARDS.DAT. The end-of-file (EOF) in the card deck must be indicated
with an EOF card (12-11-0-1-6-7-8-9 overpunch).
The DEALLOCATE command relinquishes use of the card reader.
#14 |
$ COPY [SMITH]MONKEY.DIR [JONES]
$ COPY [SMITH.MONKEY]*.* [JONES.MONKEY]*.*
|
In this example, the COPY command creates the new empty directory
[JONES.MONKEY] that is registered in the [JONES]MONKEY.DIR directory
file. After the COPY command creates the new [JONES]MONKEY.DIR
directory file, you can copy or create files in the [JONES.MONKEY]
directory.
The second COPY command in this example copies files from the
[SMITH.MONKEY] directory to the [JONES.MONKEY] directory.
#15 |
$ COPY [SMITH]CATS.DIR [SMITH]DOGS.DIR
|
In this example, the COPY command creates the new empty directory file,
called [SMITH]DOGS.DIR. Use this copy command to create a directory
file that has the same attributes as the [SMITH]CATS.DIR file. This
command example has the same effect as entering the command:
$ CREATE/DIRECTORY [SMITH.DOGS]
|
#16 |
$ COPY [SMITH]TIGER.DIR [SMITH.ANIMALS]
$ COPY [SMITH.TIGER]*.* [SMITH.ANIMALS.TIGER]*.*
$ DELETE [SMITH.TIGER]*.*;*
$ SET PROTECTION=W=D TIGER.DIR
$ DELETE TIGER.DIR;
|
In this example, the COPY command creates the new empty directory file
called [SMITH.ANIMALS]TIGER.DIR. The subsequent commands in this
example then copy the files from the [SMITH.TIGER] directory to the
[SMITH.ANIMALS.TIGER] directory, then delete the original TIGER.DIR
directory file. Because the TIGER.DIR is a directory file, you must
specify a protection code of delete (D) before you can delete the
directory file.
COPY/FTP
Transfers files between hosts with possibly dissimilar file systems
over a TCP/IP connection by invoking the FTP utility.
Format
COPY/FTP input-filespec output-filespec
Parameters
input-filespec
Specifies the name of an existing file (the source file) to be copied.
output-filespec
Specifies the name of the output file (the destination file) into which
the input file is copied.
Description
The COPY/FTP command copies files to and from remote nodes using the
File Transfer Protocol (FTP). The services provided by this command are
a subset of the architected features of FTP (see vendor documentation
for usage of their supplied FTP program).
For OpenVMS to OpenVMS
Transfers
If both machines support OpenVMS structured transfers, the /BINARY,
/ASCII, and /FDL qualifiers will be ignored. The cooperating OpenVMS
FTP client and server will automatically transfer the file with proper
OpenVMS attributes.
|
COPY/FTP commonly supports the asterisk wildcard character (*) in
remote file specifications.
Qualifiers
/ANONYMOUS
Causes an anonymous access to the remote node or nodes. /ANONYMOUS is
the default remote access. The password passed to the remote node
should be in the form of "user@fullyqualifiednodename".
/ASCII
Used to identify an ASCII file (text file). /ASCII is the default.
/BINARY
Required to identify binary files.
/FDL
This qualifier is optional. Causes interaction with an FDL (file
definition language) file. If the file is being copied to the local
OpenVMS system, a remote FDL file is sought and interpreted for the
operation. If the file is being copied outside the local OpenVMS
system, an FDL file is generated and copied in addition to the
requested file. If the /FDL qualifier is specified and the vendor
application does not support it, a warning message may be issued.
/LOG
Displays a message at SYS$OUTPUT when a file is transferred.
/NOSTRUVMS
Used to explicitly disable the negotiation of STRU OpenVMS transfers.
Otherwise, some servers will immediately abort when negotiating the
feature.
/PASSIVE=option
Controls whether the FTP client or server initiates the data
connection. If you do not specify this qualifier, the Internet Protocol
appropriate value is used. The values are: OFF for IPv4, ON for IPv6.
The following table describes the /PASSIVE options:
Option |
Description |
OFF
|
The FTP server initiates the data connection.
|
ON (default)
|
The FTP client initiates the data connection.
This is often used where a firewall between the FTP client and
server prevents the server from making an outbound connection.
ON is the default value only if /PASSIVE is specified.
|
The underlying TCP/IP Networking product must recognize this qualifier
and must support FTP passive in order for this qualifier to have an
effect.
Note that the /PASSIVE qualifier is equivalent to the FTP PASV command.
/VERBOSE
/NOVERBOSE
Specifies whether all messages (including banner messages) are to be
displayed on the terminal. By default, disables the display of the
messages.
Examples
#1 |
$ COPY/FTP/FDL/ANON rms_indexed_file.idx -
remotehst5::"/public/rms.idx.file"
|
This example transfers the OpenVMS RMS file
rms_indexed_file.idx to the remote file
public/rms.idx.file on remotehst5 over a TCP/IP
connection. Access to the remote host is anonymous and an FDL file is
generated and copied along with rms_indexed_file.idx.
#2 |
$ COPY/FTP/VERBOSE sys$login:login.com -
xdelta.zko.dec.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.
#3 |
$ COPY/FTP/LOG RESULTS.LOG -
_To: grad.uq.edu.au"JONES BYRONBAY"::DKA200$:[JONES.DATA]
|
In this example, the COPY/FTP command copies the file RESULTS.LOG to
the file DKA200$:[JONES.DATA]RESULTS.LOG using the user account JONES,
with password BYRONBAY on node grad, that is located in the
uq.edu.au internet domain.
COPY/RCP
Copies files from host to host over a TCP/IP connection by invoking the
RCP utility.
Format
COPY/RCP input-filespec output-filespec
Parameters
input-filespec
Specifies the name of an existing file (the source file) to be copied.
output-filespec
Specifies the name of the output file (the destination file) into which
the input file is copied.
Description
The COPY/RCP command copies one or more files (or directory trees) to
or from a remote host using the RCP utility.
The OpenVMS DCL commands for TCP/IP support the same remote file
specification format as the DCL commands for DECnet network
connections. Some implementations of the file transaction applications
support file transfers in which both the source file and the
destination file are remote file specifications.
The full format for a remote file specification is as follows:
node"username password account"::filename.ext
|
If a file resides on a system other than OpenVMS, enclose the name of
the file in quotation marks. For example, to access a file named
/usr/users/user/Orders on a Tru64 UNIX node named U32, you
would use the following format for the file specification:
U32"user password"::"/usr/users/user/Orders"
|
Note that UNIX® systems support case sensitive file specifications.
Qualifiers
/AUTHENTICATE
Specifies that Kerberos authentication should be used for acquiring
access to the remote node.
/LOG
Displays a message in SYS$OUTPUT when a file is transferred.
/PRESERVE
Preserves the file protection codes.
/RECURSIVE
Requests a subdirectory copy operation.
/TRUNCATE=USERNAME
Truncates the user name to 8 characters.
/USERNAME=username
Optional qualifier that specifies the remote user name. The standard
operation is to log in to a remote system using the same user name as
at the local terminal. The command supports quoted parameters in the
/USERNAME value.
Example
|
$ COPY/RCP local_file.c remotehst4"Smith smpw"::rem_file.c
|
This example copies local_file.c to rem_file.c on the
remote host remotehst4 over a TCP/IP connection.
|