Using NS3000/iX Network Services (36920-90008)

Chapter 5 89
Network File Transfer
Using DSCOPY
primary file is $STDLIST (the terminal in the case of sessions, the
system line printer in the case of streamed jobs). The secondary file is a
file or device with the formal designator DSCOPYL.
The QUIET option suppresses all information regarding the success of
file transfers except error messages. Primary output to $STDLIST is
disabled if the opt parameter of the DSCOPY intrinsic is set to 0,1, or 2;
otherwise, primary output is enabled. Secondary output is normally
disabled since the secondary file DSCOPYL defaults to $NULL. It will be
enabled if a file equation names DSCOPYL as the formal designator of an
actual file or device. For example, assume the file is named OUTFILE.
Type the following at the MPE/iX prompt:
FILE DSCOPYL=OUTFILE
If the file does not already exist, you can indicate TEMP or SAVE as the
disposition of the file. Otherwise the file will be purged.
FILE DSCOPYL=OUTFILE,new;TEMP
In the second case NFT will create the file for you, but you must SAVE it
to make it permanent.
The NFT facility also sets a number of Job Control Words (JCWs).
JCWs are 16-bit values, identified by a name, which are maintained by
MPE on a per-job or per-session basis. The JCW named DSCOPY
indicates how many files were successfully transferred in the DSCOPY
subsystem.
The JCW named NFTERR gives the NFT error code returned after an
unsuccessful transfer in an NS 3000/iX network. If a warning has been
issued, the “warn” bit of this JCW is set. Bit 2 of this JCW indicates
which NS 3000 NFT error message set the error code belongs to: if on, it
is the HP 3000-specific error message set; if off, it is the generic NFT
error message set.
If a transfer error occurs in a job stream, DSCOPY continues with the
next transfer request. However, the abort bit of the system JCW, named
JCW, is set. As a result, the job will fail after the DSCOPY subsystem is
exited unless a CONTINUE command has been specified.