NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 4 47
NFT/3000 Error Messages
4 NFT/3000 Error Messages
NFT/3000 messages may be distinguished from other NFT messages in
the following way: bit 2 of the DSCOPY result parameter or of the
NFTERR JCW indicates the appropriate error set (on=NFT/3000,
off=NFT). The DSCOPYMSG intrinsic is able to determine the correct
error set.
0 MESSAGE: NO ERRORS WERE DETECTED.
CAUSE: No errors occurred during the file transfer.
ACTION: None. This is an informative message.
1 MESSAGE: UNABLE TO OPEN NFT MESSAGE CATALOG.
CAUSE: If NFT is unable to open its message catalog it will print an
error message to the system console, log the error to the NM logging
facility and terminate. This error code will not actually be returned to
the user.
ACTION: Make sure that NFTCAT2.NET.SYS is present and not being
accessed exclusively by some other user. If so, then try running MAKECAT
to ensure that the file is in message catalog format. If the console
message says that the version number in the message catalog is not
current then obtain the proper version. Examine the NM log file to see
which file system error occurred when the FOPEN was attempted.
2 MESSAGE: ATTEMPTED READ FROM INPUT FILE FAILED.
CAUSE: Read from the command input file (formal designator DSCOPYI)
failed.
ACTION: Look for a file equation for DSCOPYI. Make sure it is what was
intended.
3 MESSAGE: UNABLE TO OPEN SECONDARY OUTPUT FILE.
CAUSE: FOPEN of the secondary output file (formal designator DSCOPYL)
failed.
ACTION: Look for a file equation for DSCOPYL. Make sure it is correct. If
primary output is not enabled, check the NM log file for the file system
error which occurred.
4 MESSAGE: UNABLE TO OPEN INPUT FILE.
CAUSE: FOPEN of the command input file (formal designator DSCOPYI)
failed.
ACTION: Look for a file equation for DSCOPYI. Ensure that it refers to a
valid file (or $STDIN).