Chapter 6 Virtual Terminal (VT ERROR) Error Messages

CAUSE: During the termination process a resource was not released with a good disposition.

ACTION: None; this is not a severe problem since MPE forces cleanup upon process termination.

CAUSE: Conflicting states existed in the VT status mask. The transition to a new state could not be made.

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

CAUSE: A VT routine requested an illegal option for altering the current state.

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

CAUSE: The VTS protocol message has no request parameters. This may be an error in the data transmission or a mismatch in versions of the VT software.

ACTION: Verify the VT versions on the different nodes, retry the VT session, and/or see Appendix A “Submitting an SR ” of this manual.

CAUSE: The VTS protocol message contains an invalid request. This may be a transmission error or a result of incompatible versions of VT.

ACTION: Check the VT version numbers using NMMAINT, retry the VT session. If the problem recurs, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The VTS protocol message could not be decoded; the format was not recognized. This results from incompatible versions of the software or an uncorrected transmission error.

ACTION: Verify the VT software version numbers, retry the VT session. If the problem recurs, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The VT "partner" on the remote machine could not handle a request and has generated an unexpected protocol error. This is the result of Virtual Terminal error 4, 5 or 6 above.

ACTION: One of your commands was probably not executed correctly. Terminate the session and re-issue the commands. If the problem persists, verify VT versions and/or submit SR.

CAUSE: The VT process could not initialize the environment properly, probably because of poor timing or a resource shortage.

ACTION: Terminate the session and log on again.

CAUSE: Sequencing problem: VT did not have a read request from the remote system to satisfy your REMOTE command.

ACTION: Reissue your command.

CAUSE: The trace facility could not be enabled or disabled. When you are starting the trace, this indicates that the trace file could not be opened. For trace termination, the file did not close successfully. In either case there may not be sufficient storage for the file, or the user's limit may have been exceeded.

ACTION: Readjust the disc space parameters, and reissue the command.

CAUSE: Information could not be added to a VT environment-related table, usually because timing was off or there was a resource shortage.

ACTION: The VT can continue to function; however, it would be best to terminate the remote session and begin again.

CAUSE: The DSLINE table was not accessible to the VT service probably because of a timing problem in the subsystems. The table entry was not released.

ACTION: Terminate the remote session.

CAUSE: An internal buffer could not be returned to the buffer pool.

ACTION: If the problem reoccurs, dump the system and see Appendix A “Submitting an SR ” of this manual.

CAUSE: The File System did not honor the request to alter the issuing of Line Feed on receipt of a Carriage Return.

ACTION: This may affect the actions of the remote application program: if problems occur, reestablish the remote session.

CAUSE: Setting of a timed read failed.

ACTION: This may affect the actions of the remote application program: if problems occur, reestablish the remote session.

CAUSE: The echo setting was not altered as requested by the application program.

ACTION: This will affect the remote program: terminate and rerun the program.

CAUSE: Space control was not altered.

ACTION: Line feeds will not be issued as requested: rerun the remote program.

CAUSE: A preemptive write could not be issued.

ACTION: None.

CAUSE: Data could not be written to the terminal.

ACTION: Reconfigure the terminal to respond to the attached CPU.

CAUSE: Terminal type could not be retrieved from the file system.

ACTION: Reattempt to establish the remote session. If it fails again, make sure that the terminal is properly configured for MPE.

CAUSE: End-of-Record setting failed.

ACTION: Terminate the remote program, reset the terminal, and run the program again.

CAUSE: The mode required by the remote program was not set by MPE.

ACTION: Terminate the remote program and attempt to rerun it.

CAUSE: The File System did not alter the setting of the driver/terminal handshake mode.

ACTION: Terminate the remote program.

CAUSE: The terminal could not be allocated for access.

ACTION: Check the MPE configuration and retry the remote session.

CAUSE: The terminal type was not reset as requested.

ACTION: Terminate the remote program and rerun it.

CAUSE: The parity setting for reads/writes to the terminal was not altered.

ACTION: Terminate the remote program, check the terminal's configuration, and rerun the program.

CAUSE: The terminal could not be opened for VT access.

ACTION: Use SYSDUMP to verify that your terminal is correctly configured as a valid MPE terminal.

CAUSE: A hardware EOF was set on the terminal.

ACTION: Reestablish your local session.

CAUSE: The VT could not continue because of a VTS protocol error or a corrupt data structure.

ACTION: Verify the NS version numbers, and if they are compatible, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The remote logon was started; however, it did not succeed because the logon timed out, a break was issued during logon, the remote CI aborted, or communication to the remote system was lost.

ACTION: Reattempt the remote logon.

CAUSE: Some action on the remote system, probably an operator command, forced the session to be aborted.

ACTION: Reestablish remote session.

CAUSE: The session device is either incorrectly configured, is not a terminal, or is not accessible through the file system.

ACTION: Check the above and reattempt logon.

CAUSE: VT could not initialize itself because of an internal error or a resource shortage.

ACTION: Reattempt the logon; if it fails, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The remote system could not support a VT option or the two systems have incompatible software versions.

ACTION: Verify the VT version numbers and submit an SR.

CAUSE: The local and remote VT code are different versions, or a data transmission error occurred.

ACTION: Reattempt session establishment. If the error reoccurs, verify the version numbers using NMMAINT and see Appendix A “Submitting an SR ” of this manual.

CAUSE: The node name specified is not valid.

ACTION: Check the validity of the node name and make sure that it is installed in the Node Management Tables. If valid and installed, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The remote machine has no VT servers available.

ACTION: Enable/increase the number of VT servers on the remote machine.

CAUSE: The connection to the remote machine has failed. The session is terminated.

ACTION: Attempt to re-logon to the remote machine.

CAUSE: The connection to the remote machine has failed. The session is terminated.

ACTION: Attempt to re-logon to the remote machine.

CAUSE: The remote VT closed the connection. The session has been terminated.

ACTION: Attempt to re-logon to the remote machine.

CAUSE: There is insufficient buffer space because of a shortage of table space or system tables. The VT could not be started.

ACTION: Reattempt the command. If problem persists, see Appendix A “Submitting an SR ” of this manual

CAUSE: There is an error in the interaction between the CI and VT.

ACTION: Verify the version numbers of the NS subsystem for the CI and VT. See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal data structure allocation error.

ACTION: When possible, dump the system and forward it to your SE.

CAUSE: A condition on the remote system forced the VT to terminate.

ACTION: None; this is a valid action.

CAUSE: An error occurred while trying to restart the VT because of old data or a non-responding remote node.

ACTION: Close the DSLINE, reopen it, and initiate a new remote session.

CAUSE: No error.

ACTION: This is an informative message.

CAUSE: The device specified for access is not available.

ACTION: Verify that the node name and device are valid.

CAUSE: All available pseudo terminals are currently active.

ACTION: Try the remote request later.

CAUSE: A File System error has occurred; the terminal was not accessible by the VT program.

ACTION: Save the Node Management logfile, and if the problem recurs, see Appendix A “Submitting an SR ” of this manual.

CAUSE: Your session device is not an acceptable MPE session device.

ACTION: Verify the configuration in SYSGEN.

CAUSE: The device string was omitted in the FOPEN or file equation.

ACTION: Insert a device string.

CAUSE: The terminal did not respond since the speed in the configuration file and the hardware-configured speed do not match.

ACTION: Set the hardware to the speed in the configuration file.

CAUSE: The connection to the remote machine failed because the local network services are going down.

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

CAUSE: An error occurred while VT trying to set or steal break for the remote session.

ACTION: Bring up the network services on the local node, and re-establish the connection.

CAUSE: The ATTACHIO failed with an abnormal completion code.

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

CAUSE: Could not set the $BACK information to environment table.

ACTION: Close the DSLINE, re-open the line, and then initiate a new remote session.