 |
» |
|
|
|
CIERR errors are reported by the Command Interpreter when
an error is detected in the DSLINE,
REMOTE, or NSCONTROL
commands. (NETCONTROL
is not included here; NETCONTROL
has its own set of errors.) | | | |  | NOTE: A CI error is displayed on $STDLIST
during the execution of the command. Some CI errors display a pointer
(^) to the error in the command. For the Network Service commands,
more than one CI error may be displayed (although only in a session;
a job aborts when the first CI error is detected). These CI errors
are held in CATALOG.PUB.SYS,
message set 2 (CI errors). When a CI error is detected, the CIERR
job control word is set to the error number. | | | | |
The CI errors fit into four categories: Syntax errors or invalid
options: These errors result from user errors when issuing
the command, and can be readily corrected. Warnings: Warnings are issued
when a command is still executable, but the results may not be what
you intended. These result from cases where conflicting options
are specified. The warning informs you which option was actually
used (or not used). Resource errors: These errors
occur when a system resource needed for the execution of the command
is not available. They should be rare. If they occur, you can wait
and reissue the command later, when the resource may be available.
If resource errors happen frequently, the configuration or resource
allocation of the system may be inadequate. The system manager and
SE should then look into the problem. Resource errors are also logged
using Network Management logging, to log class 6, subclass 2. Internal errors: These errors
indicate that the Network Service software is malfunctioning. If
they ever occur, an HP representative should be notified. Internal
errors are also logged using Network Management logging, to log
class 6, subclass 3.
MESSAGE: INTERNAL
DS ERROR — NO KEYWORD TABLE. | CAUSE: The NS
Keyword Table was not allocated during system startup or prior to
an NS command execution. ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: INTERNAL
DS ERROR — NO ASGLOBAL DST. | CAUSE: The NS
global data segment was not allocated during system startup, or
has been lost. ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: INVALID
ASCAT.NET.SYS MESSAGE CATALOG. | CAUSE: The ASCAT.NET.SYS
message catalog exists, but is not in the proper format. It may
have been overwritten by a file that is not a properly prepared
message catalog. ACTION: Check that the message
sets of the ASCAT.NET.SYS
catalog are correct. Run the MAKECAT
utility to prepare the message catalog properly. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT ALLOCATE KEYWORD BUFFER. | CAUSE: The NS
Keyword Table is not large enough to contain all the keywords from
the ASCAT.NET.SYS
catalog. ACTION: See Appendix A “Submitting an SR ”of this manual. |
MESSAGE: ASCAT.NET.SYS
MESSAGE CATALOG DOES NOT EXIST. | CAUSE: The ASCAT.NET.SYS
catalog file is missing; the NS command keywords cannot be loaded. ACTION: Inform your system
manager; install ASCAT.NET.SYS
from the NS product tape. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT CREATE KEYWORD TABLE. | CAUSE: The NS
Keyword Table extra data segment could not be allocated, because
of insufficient memory or free DSTs. ACTION: Inform your system
manager; increase the number of configured DSTs or obtain more memory. |
MESSAGE: NON-NUMERIC
CHARACTER IN ENVIRONMENT NUMBER. | CAUSE: Syntax
error in an environment number #Lxxx (in DSLINE)
or xxx (in REMOTE),
where one or more of the values for x is not numeric. ACTION: Correct the syntax
error and reissue the command. |
MESSAGE: NON-ALPHANUMERIC
CHARACTER IN ENVIRONMENT ID OR NODE NAME. | CAUSE: Syntax
error in an environment identifier in a DSLINE
or REMOTE, where
one or more characters are not alphanumeric. ACTION: Correct the syntax
error and reissue the command. |
MESSAGE: FILE NAME
PART LONGER THAN 8 CHARACTERS. | CAUSE: The file,
group, or account portion of a file name is longer than the allowed
maximum length. ACTION: Correct the file
name and reissue the command. |
MESSAGE: NON-ALPHANUMERIC
CHARACTER IN FILE NAME. | CAUSE: There is
a character in a file name that is not an alphabetic or a numeric
character (or special character .
or /). ACTION: Correct the file
name and reissue the command. |
MESSAGE: EXPECTED
, ; OR RETURN. | CAUSE: An invalid
delimiter was found after a parameter for a command option. ACTION: Correct the syntax
error and reissue the command. |
MESSAGE: EXPECTED
, ; OR RETURN. | CAUSE: An invalid
delimiter was found after a parameter for a command option. ACTION: Correct the syntax
error and reissue the command. |
MESSAGE: EXPECTED
TRACE SERVICE:ALL, VT, NFT, RFA. | CAUSE: In a DSLINE TRACE
option, the second parameter was not the name of the service to
be traced. ACTION: Correct the option
parameter and reissue the command. |
MESSAGE: EXPECTED
MAXIMUM NUMBER OF TRACE RECORDS. | CAUSE: In a DSLINE TRACE
option, the third parameter was not the number of trace records
in the trace file, an integer between 0 and 32767. ACTION: Correct the option
parameter and reissue the command. |
MESSAGE: EXPECTED
MAXIMUM LENGTH OF TRACE DATA. | CAUSE: In a DSLINE TRACE
option, the fourth parameter was not the length of the trace record,
an integer between 0 and 32767. ACTION: Correct the option
parameter and reissue the command. |
MESSAGE: EXPECTED
TRANS OPTION. | CAUSE: In the
DSLINE TRACE
option, the fifth parameter was not TRANS, which selects transport
tracing. ACTION: Correct the option
parameter and reissue the command. |
MESSAGE: EXPECTED
=. | CAUSE: An equals
sign (=) was not found between the option keyword and a list of
positional parameters. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: TOO MANY
PARAMTERS IN TRACE OPTION. | CAUSE: More than
the five defined parameters were specified in a DSLINE TRACE
option. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: EXPECTED
OR '. | CAUSE: A string
that begins with a quotation mark as a delimiter () or (')
does not end with a closing quotation mark () or ('). You
must use the same delimiter for starting and ending the string. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: EXPECTED
; OR RETURN. | CAUSE: An unexpected
character was found after a command option. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: QUIET OVERRIDES
PREVIOUS QUIET OPTION. | CAUSE: Two or
more QUIET options were specified. ACTION: None. |
MESSAGE: PROMPT OVERRIDES
PREVIOUS PROMPT OPTION. | CAUSE: Two or
more PROMPT options were specified. The prompt string from the last
PROMPT is used. ACTION: None (unless you
do not want the last prompt; then correct and reissue the command). |
MESSAGE: LOGON OVERRIDES
PREVIOUS LOGON OPTION. | CAUSE: Two or
more LOGON options were specified. The logon from the last LOGON
will be used. ACTION: None (unless you
do not want the last logon; then correct and reissue the command). |
MESSAGE: COMP OVERRIDES
PREVIOUS COMP OR NOCOMP OPTION. | CAUSE: Two or
more COMP and/or NOCOMP options were specified. The COMP option
will take effect. ACTION: None (unless you
do not want the COMP option; then correct and reissue the command). |
MESSAGE: NOCOMP OVERRIDES
PREVIOUS COMP OR NOCOMP OPTION. | CAUSE: Two or
more COMP and/or NOCOMP options were specified. The NOCOMP option
will take effect. ACTION: None (unless you
do not want the NOCOMP option; then correct and reissue the command). |
MESSAGE: TOO MANY
TRACE OPTIONS (MAXIMUM OF 10). | CAUSE: There were
more than 10 TRACE options specified in a DSLINE
command. ACTION: Consolidate the TRACE
options into less than 10, or break the DSLINE
command into two or more DSLINE
commands, each with less than 10 TRACE options. |
MESSAGE: DS/3000
DSLINE OPTION IS IGNORED FOR NS NODE. | CAUSE: A DSLINE
command for an NS node environment specified a DS/3000 option that
is not supported for the NS node. The unsupported DS options are
LOCID, REMID, PHNUM, LINEBUF, EXCLUSIVE, SELECT, FROMADR, FROMADDR, TOADR, TOADDR, QUEUE,
and NOQUEUE. ACTION: None. |
MESSAGE: INVALID
DSLINE OPTION; EXPECTED QUIET, PROMPT, LOGON, COMP, NOCOMP, CLOSE,
RESET, SHOW, OR TRACE. | CAUSE: An unknown
option keyword was found in a DSLINE. ACTION: Correct or delete
the option and reissue the command. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT ADD VTREQ PORT. | CAUSE: The port
used for communication between the CI and the Virtual Terminal server
could not be added to the MPE port dictionary. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT SEND SERVICE REQUEST. | CAUSE: The VT
service request could not be sent to the DSDAD process port. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT SEND START VT MSG. | CAUSE: The Start
VT port message could not be sent to the Virtual Terminal server
process. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT CREATE VT REQ PORT. | CAUSE: A port
to be used for communication between the CI and the Virtual Terminal
server process could not be created. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT GET PORT DST. | CAUSE: A port
data segment entry could not be allocated for the port between the
CI and the Virtual Terminal server. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT START VT. | CAUSE: The Virtual
Terminal service could not be initiated. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INTERNAL
DS ERROR — RECEIVED BAD PORT MESSAGE. | CAUSE: A port
message with an unexpected function code was received from the Virtual
Terminal server process. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: VT SERVER
NOT AVAILABLE NOW. | CAUSE: The Virtual
Terminal server process could not be created. There may be several
reasons: The DSSERVER.NET.SYS
program is missing. The number of created DSSERVER
processes is at the allowed maximum. The NSCONTROL SHOW=SERVERS
command will tell you the current and maximum number of DSSERVERs. The DSSERVER process
aborted during its initialization.
ACTION: Depending on the
cause: Restore the DSSERVER.NET.SYS
program from the NS/3000 product tape. Wait for the number of DSSERVERs to decrease, or
increase the maximum number of DSSERVERs by NSCONTROL SERVER=DSSERVER,,new max> (Only
users with NM capability can use the NSCONTROL
command.) See "Submitting an SR" in appendix
A of this manual.
|
MESSAGE: LOCAL VT
SERVICE HAS NOT BEEN STARTED. | CAUSE: The local
Virtual Terminal service (VTL) has not been started using the NSCONTROL
command. ACTION: Issue either an NSCONTROL START
or an NSCONTROL START=VTL
command to start the local VT service, or wait until the service
is started. (Only users with NM capability can use the NSCONTROL
command.) |
MESSAGE: LOCAL VT
SERVICE HAS BEEN ABORTED. | CAUSE: An NSCONTROL ABORT
has been issued. This immediately terminates all network services,
including the local Virtual Terminal service. ACTION: Issue either an NSCONTROL START
or an NSCONTROL START=VTL
to start the local VT service, or wait until the service is started.
(Only users with NM capability can use the NSCONTROL
command.) |
MESSAGE: VIRTUAL
TERMINAL SERVICE DETECTED AN ERROR. | CAUSE: An error
was detected by the Virtual Terminal server process. The error message
for the VT error will precede the CI error message. ACTION: Some of the VT errors
are normal responses (e.g., REMOTE NOT ACCEPTING SERVICE REQUESTS)
and some are internal errors (e.g., UNEXPECTED/BAD RESPONSE FROM VT).
Look up the VT error message for the appropriate action to take. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT SEND REMOTE COMMAND. | CAUSE: A port
message with the remote command could not be sent from the CI to
the Virtual Terminal server process. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: INVALID
TRACE INFORMATION. | CAUSE: Information
in a DSLINE TRACE
option was incorrect. A DS error will also be displayed. ACTION: Correct the TRACE
option and reissue the command. |
MESSAGE: COULD NOT
USE ENVIRONMENT. | CAUSE: This CI
error is returned for a number of errors detected when the environment
in a DSLINE or REMOTE
command cannot be used. One or more DS errors will accompany this
CI error to more fully describe the error or errors. ACTION: Correct the command,
based on the DS errors, and reissue. |
MESSAGE: COULD NOT
USE GENERIC ENVIRONMENT. | CAUSE: This CI
error is returned for a number of errors detected when a generic
environment in a DSLINE command
cannot be used. One or more DS errors will accompany this CI error
to more fully describe the error or errors. ACTION: Correct the command,
based on the DS errors, and reissue. |
MESSAGE: ALL DSLINE
OPTIONS BUT CLOSE ARE IGNORED. | CAUSE: Other options
besides CLOSE
were specified in a DSLINE
command. ACTION: None (the selected
environment is closed). |
MESSAGE: ALL DSLINE
OPTIONS BUT RESET ARE IGNORED. | CAUSE: Other options
besides RESET
were specified in a DSLINE
command. ACTION: None (the selected
environment is closed). |
MESSAGE: DSLINE OPTION
OVERRIDES PREVIOUS DSLINE OPTION. | CAUSE: More than
one DSLINE option
was included in a REMOTE HELLO
command. The last DSLINE
option is used. ACTION: None (the REMOTE HELLO
will be executed). |
MESSAGE: DSLINE OPTION
IGNORED. | CAUSE: Both the
envid and DSLINE=envid
options were specified in a REMOTE HELLO
command. The envid is used to select the environment. ACTION: None (the REMOTE HELLO
will be executed). |
MESSAGE: GENERIC
ENVIRONMENT ID NOT ALLOWED HERE. | CAUSE: A generic
environment ID (with the wild card characters @,
#, and/or ?)
was used in the envid or DSLINE=envid
option of a REMOTE command. ACTION: Correct the syntax
and reissue the command. If you want to execute a REMOTE
command for a set of environments, you must issue a separate REMOTE
for each environment. |
MESSAGE: NO DEFAULT
ENVIRONMENT FROM PREVIOUS :DSLINE OR :REMOTE. | CAUSE: A REMOTE
or DSLINE command was issued
without an environment ID or environment number, and there is no
default environment set by a previous command. ACTION: Insert an environment
ID or number into the syntax and reissue the command. |
MESSAGE: INVALID
NSCONTROL OPTION: EXPECTED START, STOP, ABORT, SERVER, LOG, DEBUG,
STATUS, AUTOLOGON, OR VERSION. | CAUSE: An unknown
option keyword was found in an NSCONTROL
command. ACTION: Correct or delete
the keyword and reissue the command. |
MESSAGE: TOO MANY
NSCONTROL OPTIONS. | CAUSE: The information
in the NSCONTROL command is
too large to be sent to the DSDAD
process for processing. ACTION: Consolidate options
in the command, or break the command into two or more NSCONTROL
commands. |
MESSAGE: EXPECTED
SERVER PROGRM FILE NAME. | CAUSE: The first
parameter of a SERVER option in
an NSCONTROL command was not
a program name. ACTION: Correct the SERVER
option and reissue the command. |
MESSAGE: EXPECTED
MINIMUM NUMBER OF SERVERS (>=0 AND =32767). | CAUSE: The second
parameter of a SERVER option in
an NSCONTROL command was not
the minimum number of servers, a positive integer. ACTION: Correct the SERVER
option and reissue the command. |
MESSAGE: EXPECTED
DEBUG OPTION. | CAUSE: The fourth
parameter of a SERVER option in
an NSCONTROL command was not
DEBUG or NODEBUG. ACTION: Correct the SERVER
option and reissue the command. |
MESSAGE: TOO MANY
SERVER PARAMETERS; EXPECTED AT MOST FOUR. | CAUSE: There were
more than four defined parameters for a SERVER
option in an NSCONTROL command ACTION: Correct the SERVER
option and reissue the command. |
MESSAGE: TOO MANY
SERVER PARAMETERS; EXPECTED AT MOST THREE. | CAUSE: There were
more than three defined parameters for a LOG
option in an NSCONTROL command. ACTION: Correct the LOG option
and reissue the command. |
MESSAGE: EXPECTED
ON OR OFF. | CAUSE: The first
parameter of a log option in an NSCONTROL
command was not ON (enable logging)
or OFF (disable logging). ACTION: Correct the LOG option
and reissue the command. |
MESSAGE: EXPECTED
MODULE TO BE LOGGED; EXPECTED DSDAD, DSSERVER, ENV, OR VT. | CAUSE: The second
parameter of a LOG option in an
NSCONTROL command was not the
name of a module to be logged. ACTION: Correct the LOG option
and reissue the command. |
MESSAGE: EXPECTED
HIGH OR LOW. | CAUSE: The parameter
of a log option in an NSCONTROL
command was not HIGH (log all events)
or LOW (log a subset of events). ACTION: Correct the LOG option
and reissue the command. |
MESSAGE: INTERNAL
DS ERROR — COULD NOT SEND CONTROL MESSAGE. | CAUSE: The port
message with the NSCONTROL
information could not be sent from the CI to the DSDAD process. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: DSDAD.NET.SYS
DOES NOT EXIST. | CAUSE: The DSDAD.NET.SYS
program file is missing. ACTION: Restore the DSDAD.NET.SYS
file from the NS product tape. |
MESSAGE: INVALID
CONTROL OPTION. | CAUSE: This CI
error is returned for errors detected during the processing of an
NSCONTROL command. One or more
DS errors will accompany this CI error to more fully describe the
error or errors. ACTION: Correct the error,
based on the DS error(s), and reissue the command. |
MESSAGE: INVALID
SERVER PIN. | CAUSE: The server
process ID number (PIN) in a DEBUG
option in an NSCONTROL command
is not numeric. ACTION: Correct the PIN
and reissue the command. |
MESSAGE: PROMPT MUST
BE 8 CHARACTERS OR LESS. | CAUSE: The prompt
string in a DSLINE
PROMPT option is longer than the maximum of 8 characters. ACTION: Shorten the prompt
string and reissue the command. |
MESSAGE: LOGON MUST
BE 54 CHARACTERS OR LESS. | CAUSE: The logon
string in a DSLINE LOGON
option is longer than the maximum of 54 characters. ACTION: Shorten the logon
string and reissue the command. |
MESSAGE: INTERNAL
ERROR — DSLINE JCW NOT FOUND. | CAUSE: The DSLINE
Job Control Word, set to the DSLINE
number by the DS software, could not be found. ACTION: See "Submitting
an SR" in appendix A of this manual. |
MESSAGE: ABORT DOES
NOT ACCEPT ANY PARAMETERS. | CAUSE: Parameters
were specified for an NSCONTROL ABORT
option. ACTION: Delete the parameters
and reissue the command. |
MESSAGE: ABORT DOES
NOT ACCEPT ANY PARAMETERS. | CAUSE: Parameters
were specified for an :NSCONTROL ABORT
option. ACTION: Delete the parameters
and reissue the command. |
MESSAGE: EXPECTED
ONE OF USERS, SERVICES, SERVERS, OR ALL. | CAUSE: The parameter
for a SHOW option
in an NSCONTROL command was
not one of the defined choices. ACTION: Correct the SHOW
command and reissue the parameters. |
MESSAGE: EXPECTED
MAXIMUM NUMBER OF SERVERS (=> 0 and >32767). | CAUSE: The third
parameter of a SERVER
option in an NSCONTROL
command was not a maximum number of servers, a positive integer. ACTION: Correct the SERVER
option and reissue the command. |
MESSAGE: WILD CARD
CHARACTERS NOT ALLOWED IN NODE NAME. | CAUSE:A wild card
character (@, #, or ?) was used in a node name. Node names cannot
be generic. ACTION: Correct the node
name and reissue the command. |
MESSAGE: NETWORK
SERVICE SOFTWARE VERSIONS DO NOT MATCH. | CAUSE: The version
or update, or fix levels of the Network Service software modules
are not compatible. NS cannot be initiated if its software is incompatible. ACTION: List the versions
for the NS software modules, using NSCONTROL VERSION=MOD
or RUN NMAINT.PUB.SYS.
Identify the incompatible software modules, and replace with the
assistance of your SE. |
MESSAGE: PM CAPABILITY
NEEDED TO USE DEBUG OPTION. | CAUSE: An NSCONTROL DEBUG
or NSCONTROL SERVER=,,,DEBUG
command was executed, but the user does not have PRIVILEGED MODE
(PM) capability. These commands cause a privileged breakpoint to
be activated. ACTION: Execute the command
from a user with PM capability. |
MESSAGE: SYSTEM CONSOLE
NEEDED TO USE DEBUG OPTION. | CAUSE: An NSCONTROL DEBUG
or NSCONTROL SERVER=,,,DEBUG
command was executed from a terminal other than the system console.
These commands cause a breakpoint to appear at the system console. ACTION: Execute the command
from the system console. |
MESSAGE: EXPECTED
GENERIC ENVIRONMENT ID. | CAUSE: In a DSLINE RESET,
the environment ID was not generic. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: INVALID
VERSION OPTION: EXPECTED MOD. | CAUSE: In a NSCONTROL VERSION
command, an invalid option for VERSION
was specified. VERSION=MOD
is the only allowed option. ACTION: Correct the syntax
and reissue the command. |
MESSAGE: REMOTE HELLO
FAILED. | CAUSE: In a REMOTE HELLO
command, the Virtual Terminal service was set up, but the logon
failed on the remote node. The Virtual Terminal service is then
terminated. ACTION: Check that the logon
is valid, and check the jobfence and session limits on the remote
node before reissuing the REMOTE HELLO. |
MESSAGE: NS/3000
HAS NOT BEEN STARTED BY AN :NSCONTROL START. | CAUSE: An NSCONTROL STOP
or ABORT command was issued
when the NS subsystem had not been started with NSCONTROL START. ACTION: None. |
MESSAGE: INVALID
ENVIRONMENT NUMBER. | CAUSE: Environment
number specified in DSLINE
command is greater than 32767 or the number was specified as #L. ACTION: Specify environment
number as a decimal integer between 1 and 32767, inclusive, using
the syntax #Ln. |
MESSAGE: LOGON STRING
EXPECTED. | CAUSE: The DSLINE LOGON=option
was specified without a logon sequence following the equal sign
(=). ACTION: Reissue command with
logon sequence included. |
MESSAGE: EXPECTED
SERVICE NAME: VT, VTR, VTL, VTRL, NFT, NFTL, RFA, RFAL, NSSTATL,
NSSTAT, LOOPBACK. | CAUSE: The NSCONTROL START=
or NSCONTROL STOP=
command was issued with no service names specified. ACTION: Reissue command,
specifying one or more services (as listed in the error message). |
MESSAGE: EXPECTED
ENVIRONMENT ID OR NODE NAME | CAUSE: The command
REMOTE HELLO;DSLINE=
was issued without an envid=nodename or node name. ACTION: Reissue the command,
and include the envid=nodename or nodename following the equal sign
(=). |
MESSAGE: REMOTE SESSION
CANNOT LOGOFF WHILE FRA/RDBA IS ACTIVE. | CAUSE: You cannot
logoff until RFA/RDBA terminates. ACTION: Logoff when RFA/RDBA
terminates. |
MESSAGE: ANOTHER
PROCESS IS EXECUTING A REMOTE COMMAND IN THIS ENVIRONMENT. | CAUSE: Your process
is attempting to use an environment that is already in use. Only
one process can access an environment at a time. ACTION: Try again later. |
MESSAGE: NOT ENOUGH
STACK SPACE TO EXECUTE NS COMMAND. | CAUSE: Internal
resource error. ACTION: If this happens while
running a program, prep or link the program with more stack space.
If this happens after typing a command, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: UNABLE TO
STORE NFT PORT ID IN PORT DICTIONARY. | |
MESSAGE: ERROR OCCURRED
WHEN SETTING UP NFT SERVER. | |
MESSAGE: NFT SERVER
WAS ABORTED. | CAUSE: NFT server
process terminated abnormally. ACTION: Examine the logging
information returned at the system console. If you cannot correct
the problem, see Appendix A “Submitting an SR ”
of this manual. |
MESSAGE: CRITICAL
INTERNAL NFT ERROR. | |
MESSAGE: ATTEMPT
TO PLACE NFT SERVER INTO REQUESTORS ENVIRONMENT FAILED. | |
MESSAGE: UNABLE TO
CONTRACT NFT SERVER. | |
MESSAGE: NO NFT SERVERS
ARE CURRENTLY AVAILABLE. | CAUSE: Maximum
allowable limit of NFT Servers reached on system. ACTION: Wait until fewer
DSCOPY applications are running
on the system, or ask the system manager to raise the maximum allowable
limit of NFT Servers (via the NSCONTROL
command). Try again. |
MESSAGE: NSCONTROL
COMMAND ERROR. | CAUSE: NSCONTROL
error found. A previously printed error message should be more specific. ACTION: Refer to the ACTION
for the previously displayed error message. |
MESSAGE: DSLINE COMMAND
ERROR. | CAUSE: DSLINE
error found. A previously printed error message should be more specific. ACTION: Refer to the ACTION
for the previously displayed error message. |
MESSAGE: REMOTE COMMAND
ERROR. | CAUSE: REMOTE
error found. A previously printed error message should be more specific. ACTION: Refer to the ACTION
for the previously displayed error message. |
MESSAGE: RESOURCE
ERROR — COULD NOT GET DST. | |
MESSAGE: LIST IS
INCOMPLETE — RESOURCE ERROR. | |
MESSAGE: INTERNAL
DS ERROR — SERVER TERMINATED | |
MESSAGE: INTERNAL
ERROR — COULD NOT STORE VTTM ID IN DSTABLE. | CAUSE: Internal
resource error. ACTION: If this happens while
running a program, prep or link the program with more stack space.
If this happens after typing a command, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: INTERNAL
ERROR — COULD NOT STORE REQ. ID IN DSTABLE. | CAUSE: Internal
resource error. ACTION: If this happens while
running a program, prep or link the program with more stack space.
If this happens after typing a command, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: NO $BACK
ENVIRONMENT IN THIS SESSION | CAUSE: The session
executing the DSLINE command does not have $BACK
environment. This session was not created using the REMOTE
command. ACTION: None. |
MESSAGE: ONLY TRACE
OPTION IS ALLOWED FOR $BACK ENVIRONMENT | CAUSE: $BACK
environment supports only TRACE
option. ACTION: Remove all the option
except TRACE and reissue the command. |
MESSAGE: NS TRANSPORT
MISSING; MUST BE INSTALLED | CAUSE: NS Transport
product not installed. ACTION: Execute NETCONTROL VERSION=MOD.
If an error is returned, install or reinstall NS Transport properly. |
|
