Using NS3000/iX Network Services (36920-90008)

92 Chapter 5
Network File Transfer
Using Checkpoint and Restart with DSCOPY
Troubleshooting After Using CHECKPT and RESTART
If a restart returns an error, some possible explanations might be:
1. One or more of the necessary files for restarting has been lost or
corrupted, that is, NFTRxx, GENSETx, or NFTSCRxx, or the source or
target files.
2. The transfer did not progress past the negotiation stage before it was
aborted.
3. The error was not one from which a restart can be done; examples
include a file lockword violation or an unknown node name. A restart
can only be done if the transfer has progressed past the negotiation
stage to the data transfer stage.
4. The circumstances that caused the failure have not cleared; that is,
the remote system is still down, or the link has not yet been
reestablished.
5. You are not using the same local logon as was used when
checkpointing was specified.
6. The file equation for DSCOPYI is not the same as it was when
checkpointing was specified, or the command file has been purged or
corrupted.
HP 3000 to HP 3000 Copying Examples
Following are examples of how to use the DSCOPY command for copying
files between HP 3000s.
Local to Local
DSCOPY can be used (from the MPE/iX prompt) to make a local copy of a
local file. If no global location specifications are in effect, the following
names will be interpreted as local files:
DSCOPY SFILE TO TFILE
The node name delimiter (colon or comma) used alone will override any
global specification and indicate that the file is local. In this example a
semicolon replaces TO, since TO would be misinterpreted as the source
environment ID following the colon.
DSCOPY SFILE:;TFILE
The following (still local) example copies a file named INFO in the PUB
group of the MKTG account into a (new) file of the same name in the
user’s logon group and account:
DSCOPY INFO.PUB.MKTG TO INFO