CX Logging Location Codes [ NS3000/iX Error Messages Reference Manual ] MPE/iX 5.0 Documentation
NS3000/iX Error Messages Reference Manual
CX Logging Location Codes
1 CLAS0003 Cause: The NS keyword table was not allocated during
system startup prior to an NS command execution.
Action: See "Submitting an SR" in appendix A of this
manual.
2 CLAS0003 Cause: The NS global data segment was not allocated
during system startup, or has been lost.
Action: See "Submitting an SR" in appendix A of this
manual.
3 CLAS0003 Cause: Bad format in the ASCAT.NET.SYS 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.
4 CLAS0003 Cause: The NS keyword table is not large enough to
contain all keywords from the ASCAT.NET.SYS catalog.
Action: See "Submitting an SR" in appendix A of this
manual.
6 CLAS0002 Cause: The NS keyword table extra data segment could
not be allocated.because of insufficient memory or
free DSTs.
Action: Contact your system manager to increase the
number of configured DSTs or obtain more memory.
7 CLAS0003 Cause: The port used for communication between CI and
the VT server could not be added to the MPE port
dictionary.
Action: See "Submitting an SR" in appendix A of this
manual.
8 CLAS0003 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.
9 CLAS0003 Cause: The start VT port message could not be sent to
the VT server process.
Action: See "Submitting an SR" in appendix A of this
manual.
10 CLAS0002 Cause: A port for communication between the CI and CT
server process could not be created.
Action: See "Submitting an SR" in appendix A of this
manual.
11 CLAS0002 Cause: A port DST entry could not be allocated for
the port between the CI and VT server.
Action: See "Submitting an SR" in appendix A of this
manual.
12 CLAS0003 Cause: The VT service could not be initiated.
Action: See "Submitting an SR" in appendix A of this
manual.
13 CLAS0003 Cause: A port message with an unexpected function
code was received from the VT server process.
Action: See "Submitting an SR" in appendix A of this
manual.
14 CLAS0002 Cause: The VT server process could not be created.
Action: If the DSSERVER.NET.SYS program is missing,
restore it from the NS product tape. If there are no
DSSERVERs running, then try to run DSSERVER.NET.SYS to
see if there are any loader errors. Wait for the
number of DSSERVERs to decrease, or increase the
maximum number of DSSERVERs by NSCONTROL SERVER =
DSSERVER,,wmax. (Only users with NM capability can
use the NSCONTROL command.) See "Submitting an SR" in
appendix A of this manual.
15 CLAS0002 Cause: The local VT sever (VTL) has not been started
via an NSCONTROL command.
Action: Issue NSCONTROL START or NSCONTROL START=VTL
to start the local service, or wait until the service
is started. (Only users with NM capability, who also
have ALLOW capability, can use the NSCONTROL command.)
16 CLAS0003 Cause: An NSCONTROL ABORT has been issued.
Action: Issue NSCONTROL START, or wait until the
service is started. (Only users with NM capability,
who also have ALLOW capability, can use the NSCONTROL
command.)
18 CLAS0002 Cause: A port message with the remote command could
not be sent from the CI to the VT server process.
Action: See "Submitting an SR" in appendix A of this
manual.
19 CLAS0003 Cause: A port message send to DSDAD failed.
Action: See "Submitting an SR" in appendix A of this
manual.
21 CLAS0003 Cause: The DSLINE JCW, set to the DSLINE number by
the NS software, could not be found.
Action: See "Submitting an SR" in appendix A of this
manual.
22 CLAS0003 Cause: Not enough stack space to execute the NS
command.
Action: Prepare or link the program with more stack
space.
23 CLAS0003 Cause: Internal resource problem. Could not get DST
for NSCONTROL status command.
Action: If this happens all the time then see
"Submitting an SR" in appendix A of this manual.
24 CLAS0003 Cause: Internal resource error. Server terminated
during VT_START_UP.
Action: Reissue the command. If it happens again see
"Submitting an SR" in appendix A of this manual.
MPE/iX 5.0 Documentation