 |
» |
|
|
|
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. | CAUSE: No errors
occurred during the file transfer. ACTION: None. This is an
informative message. |
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. |
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. |
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. |
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). |
MESSAGE: COMMAND
LINE IS TOO LONG. | 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. | 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: KEYWORD
DICTIONARY IS TOO LONG. | |
MESSAGE: COMMAND
LINE CONTAINS TOO MANY PARAMETERS. | 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. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: NO CLOSING
QUOTE WAS SPECIFIED. | 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. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: ! IS INVALID
DELIMITER BETWEEN TARGET AND KEYWORDS. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: UNKNOWN
KEYWORD: ! | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: REMOTE ENVIRONMENT
SPECIFIED BY USER DOES NOT EXIST. | 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. | 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. | 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. | 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. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: MISSING
RIGHT BRACKET IN LOG-ON SPECIFICATION. | CAUSE: Typographical
error. ACTION: Retype and reissue
the command. |
MESSAGE: INVALID
RECORD NUMBER FOR RESTART ID FILE. | 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 | CAUSE: SCHAR
and ICHAR may not follow "+"
on the command line. ACTION: Specify these options
for every transfer. |
MESSAGE: INVALID
RESTART SPEC. | 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. | 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). | CAUSE: Reminds
user of the consequences of issuing REP
option. ACTION: None. |
MESSAGE: APP(END)
OVERRIDES REP(LACE) AND OVER(WRITE). | CAUSE: APP(end)
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). | CAUSE: Reminds
user of OVER option's
consequences. ACTION: None. |
MESSAGE: INVALID
RSIZE | 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 ! | CAUSE: Equals
sign does not follow the SDEV,
DEV, or CODE
option. ACTION: Retype and reissue
the command. |
MESSAGE: ! OVERRIDES
PREVIOUS RECORD TYPE. | 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. | 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. | 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: ! | 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: ! | CAUSE: Usually
caused by blank characters in the node (or environment) specification. ACTION: Retype and reissue
the command. |
MESSAGE: INVALID
DEVICE SPEC: ! | CAUSE: Usually
caused by blank characters in the device specification. ACTION: Retype and reissue
the command. |
MESSAGE: CREATION
OF IPC SOCKET FAILED. | |
MESSAGE: NO LOGON
FOR REMOTE ENVIRONMENT. | 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. |
MESSAGE: ATTEMPT
TO GET SOCKET ENDPOINT FAILED. | |
MESSAGE: VARIABLE
LENGTH RECORDS CANNOT BE DIRECTLY ACCESSED. | CAUSE: The DIR
option cannot be used on variable record files or with the VAR
option. ACTION: Retry. |
MESSAGE: BUFFER MANAGER
ERROR. | |
MESSAGE: ATTEMPT
TO PLACE NFT SERVER BACK IN SYSTEM ENVIRONMENT FAILED. | |
MESSAGE: BUFFER MANAGER
ERROR. | 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 an SR ”
of this manual. |
MESSAGE: INTERNAL
ERROR — SEND QUEUE OVERFLOW. | |
MESSAGE: SOURCE AND
TARGET FILE ATTRIBUTES MUST MATCH. | 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. | CAUSE: The FSIZE
option cannot be used with the OVER (overwrite) or APP (append)
option. ACTION: None. |
MESSAGE: INTERNAL
ERROR — COMPLETION QUEUE OVERFLOW. | |
MESSAGE: UNABLE TO
OBTAIN DATA SEGMENT FOR INTERNAL IPC. | |
MESSAGE: UNABLE TO
FIND AFT ENTRY FOR INTERNAL IPC. | |
MESSAGE: CREATION
OF INTERNAL IPC PORT FAILED. | |
MESSAGE: ATTEMPT
TO RECEIVE NFT SERVICE REQUEST FAILED. | |
MESSAGE: UNKNOWN
INTERNAL MESSAGE WAS RECEIVED. | |
MESSAGE: NFT SERVER
WAS ABORTED. | CAUSE: An internal
error or external request (ABORTJOB)
may have aborted the NFT server. ACTION: Check NM log file.
See Appendix A “Submitting an SR ” of this
manual. |
MESSAGE: INTERNAL
ERROR — WARNING QUEUE OVERFLOW. | |
MESSAGE: NEW SIZE
SPECIFICATION OVERRIDES PREVIOUS SETTING. | CAUSE: The size
specified in the transfer overrides the global specification. ACTION: None. |
MESSAGE: UNSUPPORTED
KEYWORD: ! | CAUSE: Keyword
specified is not currently supported by NFT/3000. ACTION: Retry. |
MESSAGE: NO FILES
IN GENERIC REQUEST. | 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. | 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. | 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. | 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. | 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. | 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. | 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. | 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: UNABLE TO
CONTACT NFT SERVER | |
MESSAGE: UNABLE TO
STORE NFT PORT ID IN PORT DICTIONARY. | |
MESSAGE: ERROR OCCURRED
WHEN SETTING UP NFT SERVER. | |
MESSAGE: NO NFT SERVERS
ARE CURRENTLY AVAILABLE. | 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. | 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. | CAUSE: All available
pseudo-terminals are in use. ACTION: If this happens often,
ask the system manager to configure more pseudo-terminals. |
MESSAGE: NFT TERMINATION
FAILED. | |
MESSAGE: LOGON ID
IS TOO LONG. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: NODE NAME
IS TOO LONG. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: FILE PASSWORD
IS TOO LONG. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: DEVICE NAME
IS TOO LONG. | CAUSE: Usually
a typographical error. ACTION: Retype and reissue
the command. |
MESSAGE: INSUFFICIENT
BUFFER SPACE FOR USER REQUEST. | |
MESSAGE: PM CAPABILITY
IS REQUIRED FOR DEBUG. | CAUSE: To enter
debug in NFT, Privileged Mode (PM) capability is required. ACTION: Contact your system
operator. |
MESSAGE: CI COMMAND
EXECUTION FAILED. | CAUSE: Usually
accompanied by an MPE error. ACTION: Fix the MPE error. |
MESSAGE: NEW SOURCE
FILE CODE OVERRIDES PREVIOUS SETTING. | ACTION: None. CAUSE: Reminder to user. |
MESSAGE: INVALID
FCODE. | 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. | 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. |
MESSAGE: INVALID
DATA MESSAGE WAS RECEIVED. | |
MESSAGE: UNABLE TO
OBTAIN INFO ON NEWLY CREATED SESSION. | |
MESSAGE: INVALID
STRING FOLLOWING RIGHT BRACKET. | 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. | 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 | CAUSE: Internal
error parameter out of bounds. ACTION: Check parameters
passed to DSCOPY
or DSCOPY MSG. |
MESSAGE: SPLITSTACK
MODE CALLS NOT ALLOWED. | 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). | CAUSE: OPT
has value other than 0 opt 14. ACTION: Check content of
OPT parameter. |
MESSAGE: ILLEGAL
BASIC CALLING SEQUENCE. | 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. | 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. | 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. | 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. | CAUSE: Typographical
errors. ACTION: See Using
NS3000/iX Network Services for the correct delimiters. |
MESSAGE: INVALID
COMMAND INPUT FORMAL FILE DESIGNATOR. | 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. | CAUSE: File equation
contains ';DEL' parameter. ACTION: Remove file parameter
';DEL' from file equation. |
MESSAGE: FILE CMD.
WITH 'NEW', 'OLD', or 'OLDTEMP'
OPT. NOT ALLOWED. | CAUSE: Domain
parameter in file equation. ACTION: Remove file equation
domain parameter. |
MESSAGE: BLOCK SIZE
EXCEEDS MAXIMUM ALLOWABLE LIMIT. | 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. | 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. | 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. | 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. | CAUSE: Target
file is a byte stream file. ACTION: NFT is POSIX aware,
not POSIX compliant, and does not support byte stream files. |
|
