Using NS3000/iX Network Services (36920-90008)

88 Chapter 5
Network File Transfer
Using DSCOPY
4. The DSCOPY subsystem is terminated.
All specifications except file names may be made global in this manner.
A new SDEV or TDEV specification, or “SDEV=” or “TDEV=” without a
device name, clears a previous global source or target device. The only
way to clear MOVE, COMP, or QUIET is to use CLEAR.
If all source and target parameters are omitted, or if the command
begins with + (global), you will receive a subsystem prompt consisting
of the string DSCOPY. (You can also issue global specifications within
the subsystem.)
Interrupting a File Transfer
[BREAK] is disabled during a DSCOPY operation. To interrupt a file
transfer in progress, type
[CTRL]-Y instead.
The DSCOPY subsystem issues a prompt consisting of the word DSCOPY.
If you press [CTRL]-Y (or //[Return]) in response to this prompt, the
subsystem is terminated. If you enter
[CTRL]-Y in response to a
continuation prompt (issued when an ampersand on the previous line
allows a command to be continued on the next line), the current
command is not executed and the DSCOPY prompt is reissued. If
[CTRL]-Y interrupts a file transfer, you are prompted for further
instructions. The following commands are allowed:
1. A[BORT] — stops transfer and saves as permanent files new files
created during the transfer. Files in the process of transferring that
have been partially copied are saved as new target files.
2. C[ANCEL] — stops transfer. Target files that have already been
completely copied during the transfer are saved on the target
system. Files whose transfer was incomplete are not saved on the
target system.
3. P[ROGRESS] — causes progress of transfer to be reported.
4. ? — gives a description of the commands listed above.
If an error or a CANCEL request interrupts a transfer, a newly created
file will be purged unless the transfer is complete. If a generic file set is
being transferred, those files that have been successfully copied are not
purged. In the case of a KSAM file (actually two files, a data file and a
key file), the new data file is purged unless its transfer is complete; the
new key file is not purged even if its transfer is not complete. If an
incomplete key file is created in this way, you should purge it or
overwrite it in a subsequent transfer.
Event Recording
DSCOPY produces a listing of user requests and file transfer results
(including error messages). This information is sent to a primary file
and a secondary file, either of which (or both) may be disabled. The