CX Logging Location Codes

CAUSE: The NS keyword table was not allocated during system startup prior to an NS command execution.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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.

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.

CAUSE: The NS keyword table is not large enough to contain all keywords from the ASCAT.NET.SYS catalog.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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.

CAUSE: The port used for communication between CI and the VT server could not be added to the MPE port dictionary.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The VT service request could not be sent to the DSDAD process port.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The start VT port message could not be sent to the VT server process.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A port for communication between the CI and CT server process could not be created.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A port DST entry could not be allocated for the port between the CI and VT server.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The VT service could not be initiated.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A port message with an unexpected function code was received from the VT server process.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

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.)

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.)

CAUSE: A port message with the remote command could not be sent from the CI to the VT server process.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A port message send to DSDAD failed.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The DSLINE JCW, set to the DSLINE number by the NS software, could not be found.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Not enough stack space to execute the NS command.

ACTION: Prepare or link the program with more stack space.

CAUSE: Internal resource problem. Could not get DST for NSCONTROL status command.

ACTION: If this happens all the time then see Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal resource error. Server terminated during VT_START_UP.

ACTION: Reissue the command. If it happens again see Appendix A “Submitting an SR ” of this manual.