Advertisement
COPY COMMAND
7.5 -- Examples
formatting.
Thu15,
the Copy command should be used
to
print
..
~
source listings from diskette:
)
COpy TESTPROG.ALJ#LP
The
console
printerl #CN, could be used instead of #LP Just
as well.
The liN" option is not used in this example
because
the
printer
(eithsT'
#LP
01'
#CN)
is not a "file"
device.
COPlJing to a "non-file" device
will
automaticalllJ
set
the
non-file
fOTmat
mode.
If the
UN" option were
specified in
such a case, no
erro~ ~ould
result.
It
would
only
be
a
redundant
re~uest.
The
last example illustrates
ho~
the command line
~ould
appear
iT
a
user-~efined
device
driver is
used:
COpy TEST?ROG.LXJ#UDiND=TAPE
The user device is indicated via the
#UD.
The
liD"
option
must
be
present.
Otherwise;
an error Ulould result.
The
file
TAPE.LO on drive zero will be used as the device driver
file
.po,.. the user device.
7.5.3
Device-to-diskette example
Once a file has been copied to the console punch with an
FDR,
it can be
ve~iTied
or
cQpie~
back
to
diskette
without
having to speciftj its name.
The following command line:·
COpy
#CR
~ill
cause
COPY
to search .pOl' the .pirst FDR on the console
reader device.
Once it
is
~ound,
the file name' contained
in
tne FDR will be used
~or
<name 2/.
IT
the
rile
name does not
exist in the directory,
it
will be created
before
receiving
the
data
records from
the
console reader.
If the file name
already exists in the directory,
a
message will be
displayed
by the COpy command asking the operator ir the file should be
overwri tten.
The command line
COpy #CRJ TESTPROG.
LXiVL
on the other hand, will search the console reader device
for
an
FDR
that
contains
the
file
name
TESTPROG. LX.
The
same
file name must also exist in the directory of the diskette in
drive
zero
so
that
the
verification can take place.
Any
mis-comparisons between the two Piles will be printed on
the
line printer.
If
the
user
has files in a rormat that can be read by
the
console reader devicel
but
wh
ich
have
no
FDRI
the
liN"
.~
Page
07-12
/
Advertisement
