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.
MESSAGE: NO ERRORS WERE DETECTED.
Level: 0
CAUSE: No errors occurred during the file transfer.
ACTION: None. This is an informative message.
MESSAGE: UNABLE TO OPEN NFT MESSAGE
CATALOG.
Level: 1
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.
MESSAGE: ATTEMPTED READ FROM INPUT FILE FAILED.
Level: 2
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.
MESSAGE: UNABLE TO OPEN SECONDARY OUTPUT FILE.
Level: 3
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.
MESSAGE: UNABLE TO OPEN INPUT FILE.
Level: 4
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).
MESSAGE: COMMAND LINE IS TOO LONG.
Level: 5
CAUSE: Input command length exceeded the allowed maximum
(200 bytes).
ACTION: Ensure that the command input file is correct. If the
command is truly too long, global specifications may be used to
shorten it.
MESSAGE: CALL TO GENMESSAGE FAILED.
Level: 6
CAUSE:DSCOPYMSG intrinsic could not retrieve the
specified error string from the NFT message catalog.
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.
MESSAGE: COMMAND LINE CONTAINS TOO MANY PARAMETERS.
Level: 9
CAUSE: Too many delimiters were in the command line (each
delimiter corresponds to one parameter).
ACTION: If the command line was entered properly, try using global
specifications to reduce the number of parameters.
MESSAGE: NO SOURCE FILE WAS SPECIFIED.
Level: 10
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: NO CLOSING QUOTE WAS SPECIFIED.
Level: 11
CAUSE: A matching apostrophe (') or set of quotation
marks (" "), was not found.
ACTION: The punctuation surrounding the parameter is not of the
same type. They must both be either (' ') or (" ").
MESSAGE: ! IS AN INVALID DELIMITER BETWEEN SOURCE AND TARGET.
Level: 12
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: ! IS INVALID DELIMITER BETWEEN TARGET AND KEYWORDS.
Level: 13
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: UNKNOWN KEYWORD: !
Level: 14
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: REMOTE ENVIRONMENT SPECIFIED BY USER DOES NOT EXIST.
Level: 15
CAUSE: The session associated with the specified node or
environment cannot be found. Either the session was aborted externally or
an internal error occurred.
ACTION: Ask your system manager if your session was aborted. If
not, check the NM log file for additional error
information.
MESSAGE: RESTART ID FILE NAME IS TOO LONG.
Level: 16
CAUSE: Restart ID file name exceeds the length of a legal
MPE file name.
ACTION: Correct the file name and re-enter the
command.
MESSAGE: INVALID FILE SIZE.
Level: 19
CAUSE:FSIZE specified contains non-numeric characters or
is too large.
ACTION: Retype and reissue the command with the correct
FSIZE.
MESSAGE: INVALID CHECKPOINT INTERVAL.
Level: 20
CAUSE: Checkpoint interval specified contains non-numeric
characters or is too large.
ACTION: Retype and reissue the command with the correct
checkpoint interval.
MESSAGE: FILE IS TOO LONG.
Level: 22
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: MISSING RIGHT BRACKET IN LOG-ON SPECIFICATION.
Level: 23
CAUSE: Typographical error.
ACTION: Retype and reissue the command.
MESSAGE: INVALID RECORD NUMBER FOR RESTART ID FILE.
Level: 24
CAUSE: Record number specified for restart ID file contains
non-numeric characters or is too large.
ACTION: Retype and reissue the command with the correct
record number for the restart ID.
MESSAGE: SCHAR AND ICHAR NOT ALLOWED AS GLOBAL SPECS.
Level: 25
CAUSE:SCHAR and ICHAR may not follow "+" on the
command line.
ACTION: Specify these options for every transfer.
MESSAGE: INVALID RESTART SPEC.
Level: 26
CAUSE:RESTART option syntax is incorrect.
ACTION: See Using NS 3000/iX Network Services for
correct syntax.
MESSAGE: FILE ID NOT ALLOWED AS GLOBAL SPECIFICATION.
Level: 27
CAUSE: File ID cannot follow "+" on
command line. All other specifications may be made global.
ACTION: Retype and reissue the command.
MESSAGE: REP(LACE) OVERRIDES APP(END) AND OVER(WRITE).
Level: 28
CAUSE: Reminds user of the consequences of issuing REP
option.
ACTION: None.
MESSAGE: APP(END) OVERRIDES REP(LACE) AND OVER(WRITE).
Level: 29
CAUSE: APP (append) was specified after REP (replace)
or OVER (overwrite), therefore it takes effect during the transfer.
ACTION: None.
MESSAGE: OVER(WRITE) OVERRIDES APP(END)
AND REP(LACE).
Level: 31
CAUSE: Reminds user of OVER option's consequences.
ACTION: None.
MESSAGE: INVALID RSIZE.
Level: 34
CAUSE:RSIZE specified contains non-numeric characters or
is too large.
ACTION: Retype and reissue the command with the correct
RSIZE.
MESSAGE: EQUALS SIGN MUST FOLLOW !
Level: 35
CAUSE: Equals sign does not follow the SDEV, DEV,
or CODE option.
ACTION: Retype and reissue the command.
MESSAGE: ! OVERRIDES PREVIOUS RECORD TYPE.
Level: 36
CAUSE: Either FIX or VAR was specified when the
other was already specified in the command line or globally.
ACTION: None.
MESSAGE: ! OVERRIDES PREVIOUS FILE TYPE.
Level: 37
CAUSE: Either SEQ or DIR was specified when the
other was already specified in the command line or globally.
ACTION: None.
MESSAGE: ! OVERRIDES PREVIOUS DATA TYPE.
Level: 38
CAUSE: Either BIN or ASC was specified when the
other was already specified in the command line or globally.
ACTION: None.
MESSAGE: INVALID FILE ID: !
Level: 40
CAUSE: Usually caused by blank characters in the file
ID, or by omitting a delimiter or parameter.
ACTION: Retype and reissue the command.
MESSAGE: INVALID NODE SPEC: !
Level: 41
CAUSE: Usually caused by blank characters in the node
(or environment) specification.
ACTION: Retype and reissue the command.
MESSAGE: INVALID DEVICE SPEC: !
Level: 42
CAUSE: Usually caused by blank characters in the device
specification.
ACTION: Retype and reissue the command.
Level: 44
CAUSE: A node or environment was specified without a
logon specification and without a pre-existing remote session.
ACTION: Specify a logon string in the DSCOPY command line
or perform a DSLINE/REMOTE HELLO before issuing the DSCOPY
command.
Level: 49
CAUSE: When an NFT process is initiated it attempts to
place itself into the appropriate user session (or job). The error
results when this attempt fails.
ACTION: Make sure that the sessions involving file transfer
have not been aborted. If the sessions are present, see
Appendix A "Submitting a CR" of this
manual.
MESSAGE: SOURCE AND TARGET FILE ATTRIBUTES MUST MATCH.
Level: 51
CAUSE: For certain operations (such as overwrite) the
attributes (data type, file type) of both files involved must match.
When they do not this error results.
ACTION: If overwrite was attempted but the source and
target files aren't compatible, try using the replace option (REP);
or use FCOPY to copy the files.
MESSAGE: FSIZE SPEC IS IGNORED IF TARGET EXISTS.
Level: 52
CAUSE: The FSIZE option cannot be used with the OVER
(overwrite) or APP (append) option.
ACTION: None.
Level: 60
CAUSE: An internal error or external request (ABORTJOB)
may have aborted the NFT server.
ACTION: Check NM log file. See
Appendix A "Submitting a CR" of this
manual.
MESSAGE: NEW SIZE SPECIFICATION OVERRIDES PREVIOUS SETTING.
Level: 62
CAUSE: The size specified in the transfer overrides the
global specification.
ACTION: None.
MESSAGE: UNSUPPORTED KEYWORD: !
Level: 63
CAUSE: Keyword specified is not currently supported by NFT/3000.
ACTION: Retry.
MESSAGE: NO FILES IN GENERIC REQUEST.
Level: 64
CAUSE: There are no files in the requested generic file set.
ACTION: Check file names and try the transfer
again.
MESSAGE: UNABLE TO CREATE GENERIC TEMP FILE.
Level: 65
CAUSE: NFT needs a temporary file to hold file names in a generic
set. This error results when NFT is unable to create this file. The cause
may be a lack of disk space, duplicate file name.
ACTION: Check file space available, increase it if necessary
(and possible). Check for temporary files named GENSET@. Purge
these and try the transfer again.
MESSAGE: SOURCE DEVICE SPEC OVERRIDES GLOBAL SPEC.
Level: 66
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
MESSAGE: TARGET NODE SPEC OVERRIDES GLOBAL SPEC.
Level: 67
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
MESSAGE: SOURCE NODE SPEC OVERRIDES GLOBAL SPEC.
Level: 68
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
MESSAGE: TARGET NODE SPEC OVERRIDES GLOBAL SPEC.
Level: 69
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
MESSAGE: SOURCE LOGON SPEC OVERRIDES GLOBAL SPEC.
Level: 70
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
MESSAGE: TARGET LOGON SPEC OVERRIDES GLOBAL SPEC.
Level: 71
CAUSE: An existing global specification conflicts with a
specification in the current transfer. The specification in the current
transfer will override the global specification for the current transfer
only.
ACTION: None.
Level: 75
CAUSE: The number of active NFT servers (set via
NSCONTROL) has reached its limit.
ACTION: Adjust the maximum number of NFT servers allowed via
NSCONTROL. If this is not possible, try to invoke NFT again as a
server may have terminated.
MESSAGE: MESSAGE FILES MAY NOT BE TRANSFERRED IN INTERCHANGE MODE.
Level: 76
CAUSE: MPE message files cannot be transferred using any of the
options which invoke interchange mode.
ACTION: Try the transfer again without any options which
invoke interchange mode.
MESSAGE: UNABLE TO OBTAIN PSEUDO-TERMINAL FOR LOGON.
Level: 77
CAUSE: All available pseudo-terminals are in use.
ACTION: If this happens often, ask the system manager
to configure more pseudo-terminals.
Level: 85
CAUSE: To enter debug in NFT, Privileged Mode (PM) capability
is required.
ACTION: Contact your system operator.
MESSAGE: CI COMMAND EXECUTION FAILED.
Level: 86
CAUSE: Usually accompanied by an MPE error.
ACTION: Fix the MPE error.
MESSAGE: NEW SOURCE FILE CODE OVERRIDES PREVIOUS SETTING.
Level: 87
ACTION: None.
CAUSE: Reminder to user.
MESSAGE: INVALID FCODE.
Level: 88
CAUSE: File code contains non-numeric characters or is too large.
ACTION: The file code must be specified as a
number.
MESSAGE: SM or PM CAPABILITY REQUIRED TO COPY PRIVILEGED FILES.
Level: 89
CAUSE: The user specified a negative file code but did
not have system manager or privileged mode capability.
ACTION: Make sure that the source file is accessed from a session
(or job) whose user has system manager or privileged mode
capability.
Level: 92
CAUSE: One or more invalid characters follow the right
bracket in the logon part of the DSCOPY command.
ACTION: Re-enter the command using the correct
delimiters.
MESSAGE: INVALID STRING FOLLOWING CLOSING QUOTE.
Level: 93
CAUSE: One or more invalid characters follow a closing
quote. A file name, node name, or logon name enclosed in quotes
must be followed by an appropriate delimiter.
ACTION: Re-enter the DSCOPY command using correct
delimiters.
MESSAGE: BOUNDS VIOLATION.
Level: 94
CAUSE: Internal error parameter out of bounds.
ACTION: Check parameters passed to DSCOPY or
DSCOPY MSG.
MESSAGE: SPLITSTACK MODE CALLS NOT ALLOWED.
Level: 95
CAUSE:DSCOPY will not run in splitstack mode.
ACTION: Do not attempt to run DSCOPY in splitstack
mode.
MESSAGE: FIRST PARAMETER IS OUT OF RANGE (0:14).
Level: 96
CAUSE:OPT has value other than 0 opt 14.
ACTION: Check content of OPT parameter.
MESSAGE: ILLEGAL BASIC CALLING SEQUENCE.
Level: 100
CAUSE: There is in an error in the calling sequence of
a BDSCOPY intrinsic call.
ACTION: Refer to Using NS 3000/iX Network Services for
the correct calling sequence.
MESSAGE: AUTOLOGON DISABLED; USE :REMOTE HELLO FOR REMOTE SESSION.
Level: 103
CAUSE: Automatic logon facility has been turned off by
the network manager.
ACTION: Logon to the remote environment using the
REMOTE HELLO command. Specify this remote environment in the
DSCOPY command.
MESSAGE: RESTART KEYWORD NOT ALLOWED IN DSCOPYI FILE.
Level: 104
CAUSE: User is attempting a restart from the DSCOPYI
command file.
ACTION: Only use the RESTART keyword when
DSCOPYI has not been redirected to a file.
MESSAGE: ERROR IN RETRIEVING RESTART ID NUMBER FROM RESTART ID FILE.
Level: 105
CAUSE: An error occurred while attempting to obtain the
restart ID from the specified file.
ACTION: Verify that the restart ID file name and record
number are correct.
MESSAGE: ! IS AN INVALID DELIMITER AS USED IN RESTART SPEC.
Level: 106
CAUSE: Typographical errors.
ACTION: See Using NS3000/iX Network Services for
the correct delimiters.
Level: 109
CAUSE: Usually a typographical error. Either a right
parenthesis is missing, or the formal file designator is too long.
ACTION: Check the command syntax and try again.
MESSAGE: FILE COMMAND WITH 'DEL' OPT. NOT ALLOWED.
MESSAGE: BLOCK SIZE EXCEEDS MAXIMUM ALLOWABLE LIMIT.
Level: 112
CAUSE: Maximum block size is 65510 bytes.
ACTION: Change the file block size to be less or equal
to 65510 bytes.
MESSAGE: SOURCE FILE CANNOT RESIDE IN A HIERARCHICAL DIRECTORY.
Level: 113
CAUSE: Source file resides in HFS (hierarchical file
system) namespace.
ACTION: NFT is POSIX aware, not POSIX compliant, and does
not support HFS files.
MESSAGE: TARGET FILE CANNOT RESIDE IN A HIERARCHICAL DIRECTORY.
Level: 114
CAUSE: Target file resides in HFS (hierarchical file
system) namespace.
ACTION: NFT is POSIX aware, not POSIX compliant, and does
not support HFS files.
MESSAGE: SOURCE FILE CANNOT BE BYTE STREAM RECORD TYPE.
Level: 115
CAUSE: Source file is a byte stream file.
ACTION: NFT is POSIX aware, not POSIX compliant, and does
not support byte stream files.
MESSAGE: TARGET FILE CANNOT BE BYTE STREAM RECORD TYPE.
Level: 116
CAUSE: Target file is a byte stream file.
ACTION: NFT is POSIX aware, not POSIX compliant, and does
not support byte stream files.
Complete PDF