 |
» |
|
|
|
NSCONTROL messages are DSERR messages returned to $STDLIST
by the :NSCONTROL command.
(:NSCONTROL initiates,
terminates, and controls the operation of the Network Services subsystem
of NS 3000/iX.) These errors are reported during the execution
of an NSCONTROL command. There may be several
errors reported for one NSCONTROL. NSCONTROL error messages are
held in CATALOG.PUB.SYS,
message set 16 (DS errors). When an NSCONTROL error is detected,
the DSERR job control word is set to the error number. MESSAGE: SERVICE
servicename NOT STARTED. | CAUSE: An NSCONTROL
command with a START
option was issued, but the indicated service was not started. ACTION: Check that the transport
has been started. If the transport is started, then this may be
a resource or internal error. Check the Node Management log file
for the internal errors associated with this problem. See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: SERVICE
servicename ALREADY STARTED. | CAUSE: An NSCONTROL
command with a START
option was issued; the indicated service, however, was already active. ACTION: None. The other specified
services have been started. |
MESSAGE: SERVICE
servicename NOT STOPPED. | CAUSE: An NSCONTROL
command with a STOP
option was issued, but the indicated service was not stopped. ACTION: This may be an internal
error. Check the Network Management log file for the internal errors
associated with this problem. See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: SERVICE
servicename ALREADY STOPPED. | CAUSE: An NSCONTROL
command with a STOP
option was issued; the indicated service, however, was not active. ACTION: None. The other specified
services have been stopped. |
MESSAGE: UNKNOWN
SERVICE servicename. | CAUSE: An NSCONTROL
command with a START
or STOP option
was issued; the indicated service name is not a defined service. ACTION: Delete or correct
the name and reissue the command. The NSCONTROL STATUS=SERVICES
command will display the valid service names. |
MESSAGE: UNKNOWN
SERVER servername. | CAUSE: An NSCONTROL
command with a SERVER
option was issued; the indicated server name is not a defined service. ACTION: Delete or correct
the name and reissue the command. The NSCONTROL STATUS=SERVERS
command will display the valid server names. |
MESSAGE: SERVER pin
DOES NOT SUPPORT DEBUG. | CAUSE: An NSCONTROL
command with a DEBUG=pinin
option was issued, but the server selected by pin does not support
the DEBUG option. ACTION: Correct the pin and
reissue the command, or ignore. |
MESSAGE: PROCESS
pin NOT A SERVER. | CAUSE: An :NSCONTROL
command with a DEBUG=pin option
was issued, but the pin is not a server process. ACTION: Correct the pin and
reissue the command, or ignore. |
MESSAGE: MINIMUM
SERVER NUMBER MAXIMUM SERVER NUMBER FOR servername. | CAUSE: An NSCONTROL
command was issued with a SERVER
option that changes the minimum and/or maximum number of servers,
so that the minimum number of servers is greater than the maximum. ACTION: Correct the SERVER
option and reissue the command. The NSCONTROL STATUS=SERVERS
command will show the current minimum and maximum server limits
for the server type. |
MESSAGE: TOTAL MINIMUM
SERVER NUMBERS MINIMUM PROCESS LIMIT. | CAUSE: An :NSCONTROL
command was issued with a SERVER
option that changes the minimum number of servers for one or more
server types, so that the total number of previously created servers
exceeds the minimum process limit. The minimum process limit prevents
previously created servers from taking up too many processes and
hindering other applications on the system. ACTION: Adjust the minimum
number of servers to fit within the minimum process limit. |
MESSAGE: MISSING
DADCONF.NET.SYS CONFIGURATION FILE. | CAUSE: To be determined. ACTION: Check that the JCONFJOB job
has been streamed. If not, issue the command STREAM JCONFJOB. |
MESSAGE: INVALID
DADCONF.NET.SYS CONFIGURATION FILE. | CAUSE: To be determined. ACTION: Check that the JCONFJOB
job has been streamed. If not, issue the command STREAM JCONFJOB. |
MESSAGE: SERVICE
NSservice DOES NOT SUPPORT AUTOLOGON. | CAUSE: You cannot
automatically log on with the Network Service you are using. ACTION: Do not use the AUTOLOGON
function with this service. |
MESSAGE: INSUFFICIENT
STACK SPACE. | |
MESSAGE: INSUFFICIENT
SYSTEM RESOURCES. | |
|
