Chapter 3 NS/NFTERR and NS/NFTWARN Messages

CAUSE: Transfer succeeded.

ACTION: None.

CAUSE: An internal NFT error has occurred.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Error in logging on to the source computer, or no logon string supplied where required.

ACTION: Check the logon string or provide a logon string and try again.

CAUSE: Error in logging on to the target computer, or no logon string where required.

ACTION: Check the logon string or provide a logon string and try again.

CAUSE: An unexpected file system error occurred in opening or accessing the source file.

ACTION: Verify that the source file is accessible. Also, refer to the qualifying file system error string.

CAUSE: A connection could not be established to the computer where the source file resides. Either the source-computer name is incorrect, the source computer is not connected to the network, or there are insufficient resources.

ACTION: Verify that the source-computer name is correct, that the source computer is connected to the network, and that there are sufficient resources to establish a connection. Also, refer to the qualifying error string. Check the log file for PM errors.

CAUSE: A connection could not be established to the computer where the target file resides. Either the target-computer name is incorrect, or the target computer is not connected to the network, or there are insufficient resources.

ACTION: Verify that the target-computer name is correct, that the target computer is connected to the network, and that there are sufficient resources to establish a connection. Also, refer to the qualifying error string. Check the log file for PM errors.

CAUSE: Insufficient resources at the source computer to carry out the file transfer.

ACTION: Verify that there are sufficient resources on the source computer and try again. Verify that DST tables are available. Check that the configured maximum number of DST table entries is large enough.

CAUSE: Insufficient resources at the target computer to carry out the file transfer.

ACTION: Verify that there are sufficient resources on the target computer and try again. Verify that DST tables are available. Check that the configured maximum number of DST table entries is large enough.

CAUSE: Source file specified does not exist.

ACTION: Verify that the source file name is correct.

CAUSE: The target file does not exist and APPend was specified.

ACTION: Verify that the target file name is correct.

CAUSE: Acknowledges the user's Abort or Cancel request.

ACTION: None. This is an informational message only.

CAUSE: An internal error has occurred during negotiations between the source and target computers.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Consumer mainframe refused the data type offered by the producer mainframe.

ACTION: Consult Using NS 3000/iX Network Services for the use of the ASC (ASCII) and BIN (binary) option.

CAUSE: Consumer mainframe refused the record type offered by the producer mainframe.

ACTION: Consult Using NS 3000/iX Network Services for the use of the FIX (fixed) and VAR (variable) options.

CAUSE: Consumer mainframe refused the file type offered by the producer mainframe.

ACTION: Consult Using NS 3000/iX Network Services for the use of the DIR (direct) and SEQ (sequential) options.

CAUSE: Consumer mainframe refused the file size offered by the producer mainframe.

ACTION: Consult Using NS 3000/iX Network Services for the RSIZE option.

CAUSE: Consumer mainframe refused the file size offered by the producer mainframe.

ACTION: Consult Using NS 3000/iX Network Services for the FSIZE option.

CAUSE: If an overwrite operation is attempted and the files involved do not have compatible attributes, this error will result. Also, if a file equation has been issued to change the characteristics of the target file to be incompatible with those of the source file, this error is returned.

ACTION: Try the REP (replace) option or remove the offending file equation.

CAUSE: Requested RSIZE is too large.

ACTION: Specify a smaller record size.

CAUSE: Requested FSIZE is too large.

ACTION: Specify a smaller record size.

CAUSE: The target file exists and neither REPLACE nor OVERWRITE was specified.

ACTION: Verify that the target file name is correct, and specify REPLACE or OVERWRITE.

CAUSE: Source file could not be accessed without proper password.

ACTION: Specify the password and the source-file name and try again.

CAUSE: Target file could not be accessed without proper password.

ACTION: Specify the password and the target-file name and try again.

CAUSE: The target computer has run out of disk space. The target file will not fit.

ACTION: Purge unused files on the target computer and try again.

CAUSE: An error was detected on the connection to the computer where the source files reside. If the file-producer program is still active on the source computer, it will attempt to carry out the remainder of the user-file copy command (perhaps causing several file transfers to occur if wildcards were given). If the file producer is no longer active, the remaining files were not transferred.

ACTION: Determine which, if any, of the files were not transferred. Transfer these files by specifying the proper command and trying again.

CAUSE: An error was detected on the connection to the computer where the target files are to be created. If this error occurs while the file producer is in the middle of copying several files, the current file may not have been copied successfully and an attempt will not be made to copy the remainder of the files.

ACTION: Specify a command to copy the remainder of the files, and try again.

CAUSE: The existing target file could not be purged.

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: Check the target file name syntax and try again.

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: The source file could not be purged after successfully copying the file (the MOVE option was given).

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: An unexpected file system error occurred while reading from the source file.

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: An unexpected file system error occurred while writing data to the target file.

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: An unexpected file system error occurred in creating or opening the target file.

ACTION: Refer to the qualifying file system error string to determine what to do.

CAUSE: A request was made to send a file to a non-disk device. Such transfers are not supported.

ACTION: Copy the non-disk device file to a disk file using a system utility program, and then use DSCOPY to copy that file to the target computer.

CAUSE: A request was made to send a file to a non-disk device. Such transfers are not supported.

ACTION: Copy the file to disk on the target computer using DSCOPY and then to the non-disk device using a system utility program.

CAUSE: An unexpected file system error occurred in closing the target file.

ACTION: Refer to the qualifying file system error string to determine what to do

CAUSE: The given source file password was incorrect.

ACTION: Specify the correct source file password and try again.

CAUSE: The given target file password was incorrect.

ACTION: Specify the correct target file password and try again.

CAUSE: Some non-MPE systems allow characters in file names that are not allowed on MPE systems. These characters are removed from a file name when that file is transferred to an MPE system.

ACTION: None.

CAUSE: Some non-MPE systems allow file names to be longer than 8 characters. These names are truncated to 8 characters when transferred to an MPE system.

ACTION: None.

CAUSE: If interchange mode is used, source file attributes may differ from target file attributes.

ACTION: None.

CAUSE: When the target file's record size is smaller than the source file's record size, the source file's records are truncated to fit the target file's record size.

ACTION: None.

CAUSE: The source and/or the target computer does not support data compression (the COMPRESS option); or the transfer is local. File transfer will continue without data compression.

ACTION: None.

CAUSE: Indicates that an internal error has occurred. File transfer will continue without tracing.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The STRIP option cannot be used with files that have variable-length records.

ACTION: Do not use the STRIP option with files having variable-length records.

CAUSE: An unexpected file system error occurred in accessing the target file. This may mean that a file equation specified access options which conflict with those desired by NFT.

ACTION: Verify that the target file is accessible, reset previously given file equations, and specify attributes which do not conflict with those desired by NFT. Also, refer to the qualifying file system error string.

CAUSE: The source file name is invalid on the source computer.

ACTION: Check the source file name syntax and try again.

CAUSE: Target mainframe does not support the APP (append) option.

ACTION: None.

CAUSE: Target mainframe does not support the OVER (overwrite) option.

ACTION: None.

CAUSE: An error occurred while a generic source file specification was being processed.

ACTION: Verify that the generic source file specification does match up with existing files.

CAUSE: An incoming connection to an NFT server program has gone down for an unknown reason.

ACTION: This error will appear only in a log file. See "Submitting an SR" in appendix A of this manual.

CAUSE: Source mainframe does not support the MOVE option. The transfer will take place, but the source file will not be purged.

ACTION: None.

CAUSE: NFT cannot open the file containing the information needed to restart a checkpointed transfer. This may be caused by the following factors:

ACTION: Be sure there are fewer than 99 restart files in any of the necessary groups and accounts. Determine whether the file exists, and if so, make sure that the file is not being accessed. Also check to make sure that you are logged on as the same user, group, and account number as when checkpointing.

CAUSE: NFT fails to obtain valid information from the checkpointing/restart file and cannot restart the transfer. An FREAD error may have been received from the restart file, or the restart file may be in an inconsistent state and contains incomplete or invalid data.

ACTION: None.

CAUSE: NFT failed to store valid information to the checkpoint/restart file. This error is returned only if the data transfer portion of the NFT transaction has begun and an FWRITE error to the checkpoint/restart file has occurred.

ACTION: Attempt to restart the transfer. If this fails consistently, there may be a problem with the file system. See Appendix A “Submitting an SR ” of this manual.

CAUSE: NFT attempted to restart a generic transfer and was unable to open the generic listf file, i.e., the file which contains the list of files to be transferred. This would occur if the file is opened exclusively or has been purged.

ACTION: Make sure that the generic listf file (GENSETn) exists in the producer's group and account and is not accessed exclusively.

CAUSE: A restart has been attempted and the producer and consumer checkpoints do not match. The checkpoint restart file has been corrupted, or a serious internal NFT error has occurred.

ACTION: Restart the transfer from scratch. If the problem persists, see Appendix A “Submitting an SR ” of this manual.

CAUSE: This warning is issued for any one of the following reasons:

ACTION: After the warning is issued, the file transfer will continue with no checkpointing taking place. You may wish to abort the transfer.

CAUSE: Checkpointing has been specified for a transfer for which the producer and consumer environments are equivalent, i.e., their group, account, and node name are the same.

ACTION: Transfer will continue with no checkpointing. You may wish to abort the transfer.

CAUSE: Use of the FSIZE option has resulted in a target file too small to hold the source file. After the target file is full, the transfer is stopped.

ACTION: None.

CAUSE: The block size for the Native Mode KSAM file has changed because of the file system differences.

ACTION: None.