Level: 1
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.
MESSAGE: INVALID STATUS FOUND.
Level: 2
CAUSE: Conflicting states existed in the VT status mask.
The transition to a new state could not be made.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: ILLEGAL STATUS STATE.
Level: 3
CAUSE: A VT routine requested an illegal option for altering
the current state.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: VTS MESSAGE DOES NOT INCLUDE PARAMETERS.
Level: 4
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 a CR"
of this manual.
MESSAGE: VTS MESSAGE CONTAINS AN INVALID PARAMETER.
Level: 5
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 a CR" of this manual.
MESSAGE: VTS MESSAGE HAS INVALID FORMAT.
Level: 6
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 a CR" of this manual.
MESSAGE: UNEXPECTED/BAD RESPONSE FROM VT.
Level: 7
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 CR.
MESSAGE: VT SERVER NOT ADOPTED.
Level: 8
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.
MESSAGE: SAVED READ DATA NOT VALID.
Level: 9
CAUSE: Sequencing problem: VT did not have a read request
from the remote system to satisfy your REMOTE command.
ACTION: Reissue your command.
MESSAGE: VT TRACE STATE NOT ALTERED.
Level: 11
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 disk space parameters, and reissue
the command.
MESSAGE: VT DATA AREA NOT UPDATED.
Level: 12
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.
MESSAGE: RETRIEVE OF DSLINE DATA FAILED.
Level: 13
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.
MESSAGE: BUFFER/STORAGE NOT RELEASED.
Level: 14
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 a CR" of this
manual.
MESSAGE: CR/LF SWITCH FAILED.
Level: 16
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.
MESSAGE: SET READ TIMEOUT FAILED.
Level: 17
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.
MESSAGE: SET ECHO FAILED.
Level: 18
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.
MESSAGE: SET PRE/POST SPACE FAILED.
Level: 19
CAUSE: Space control was not altered.
ACTION: Line feeds will not be issued as requested: rerun
the remote program.
MESSAGE: PREEMPTIVE WRITE.
Level: 20
CAUSE: A preemptive write could not be issued.
ACTION: None.
MESSAGE: FWRITE TO TERMINAL FAILED.
Level: 21
CAUSE: Data could not be written to the terminal.
ACTION: Reconfigure the terminal to respond to the attached
CPU.
MESSAGE: GET TERM-TYPE FAILED.
Level: 22
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.
MESSAGE: SET EOR FAILED.
Level: 23
CAUSE: End-of-Record setting failed.
ACTION: Terminate the remote program, reset the terminal, and run
the program again.
MESSAGE: SET EDIT MODE FAILED.
Level: 24
CAUSE: The mode required by the remote program was not set by MPE.
ACTION: Terminate the remote program and attempt to rerun
it.
MESSAGE: SET DRIVER MODE FAILED.
Level: 25
CAUSE: The File System did not alter the setting of the
driver/terminal handshake mode.
ACTION: Terminate the remote program.
MESSAGE: TERMINAL NOT ALLOCATED.
Level: 26
CAUSE: The terminal could not be allocated for access.
ACTION: Check the MPE configuration and retry the remote
session.
MESSAGE: SET TERMINAL TYPE FAILED.
Level: 27
CAUSE: The terminal type was not reset as requested.
ACTION: Terminate the remote program and
rerun it.
MESSAGE: TERMINAL PARITY NOT ALTERED.
Level: 28
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.
MESSAGE: TERMINAL OPEN FAILED.
Level: 29
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.
MESSAGE: END OF FILE ENCOUNTERED.
Level: 30
CAUSE: A hardware EOF was set on the terminal.
ACTION: Reestablish your local session.
MESSAGE: FATAL INTERNAL ERROR OCCURRED.
Level: 31
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 a CR" of this
manual.
MESSAGE: REMOTE SESSION LOGON FAILED.
Level: 32
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.
MESSAGE: REMOTE SESSION ABORTED.
Level: 33
CAUSE: Some action on the remote system, probably an
operator command, forced the session to be aborted.
ACTION: Reestablish remote session.
MESSAGE: CANNOT ACCESS SESSION DEVICE.
Level: 34
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.
MESSAGE: VT INITIALIZATION FAILED.
Level: 35
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 a CR" of this
manual.
MESSAGE: VT NEGOTIATIONS FAILED.
Level: 36
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
CR.
MESSAGE: VTS MESSAGE PROTOCOL ERROR.
Level: 37
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 a CR" of this
manual.
MESSAGE: INVALID REMOTE NODE REQUESTED.
Level: 38
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 a CR" of this
manual.
MESSAGE: REMOTE NOT ACCEPTING CHANGE REQUESTS.
Level: 39
CAUSE: The remote machine has no VT servers available.
ACTION: Enable/increase the number of VT servers on the
remote machine.
MESSAGE: REMOTE NOT RESPONDING, DATA SEND FAILED.
Level: 40
CAUSE: The connection to the remote machine has failed.
The session is terminated.
ACTION: Attempt to re-logon to the remote
machine.
MESSAGE: REMOTE NOT RESPONDING, RECEIVED FAILED.
Level: 41
CAUSE: The connection to the remote machine has failed.
The session is terminated.
ACTION: Attempt to re-logon to the remote
machine.
MESSAGE: REMOTE NOT RESPONDING, CONNECTION CLOSED.
Level: 42
CAUSE: The remote VT closed the connection. The session
has been terminated.
ACTION: Attempt to re-logon to the remote
machine.
MESSAGE: VT COULD NOT SECURE BUFFER SPACE.
Level: 43
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 a CR" of this
manual
MESSAGE: VT-CI ERROR, MISSING DATA
STRUCTURE.
Level: 44
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 a CR" of this
manual.
MESSAGE: DUPLICATE VT DATA STRUCTURE.
Level: 45
CAUSE: Internal data structure allocation error.
ACTION: When possible, dump the system and forward it
to your SE.
MESSAGE: REMOTE VT REQUESTED STOP.
Level: 46
CAUSE: A condition on the remote system forced the VT to terminate.
ACTION: None; this is a valid action.
MESSAGE: VT RESTART ATTEMPT FAILED.
Level: 47
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.
MESSAGE: VT TERMINATED NORMALLY (VT INFORMATIONAL MESSAGE 48).
Level: 48
CAUSE: No error.
ACTION: This is an informative message.
MESSAGE: CANNOT ACCESS TERMINAL FOR
REVERSE-VT.
Level: 49
CAUSE: The device specified for access is not available.
ACTION: Verify that the node name and device are
valid.
Level: 50
CAUSE: All available pseudo terminals are currently active.
ACTION: Try the remote request later.
MESSAGE: VT TERMINATED, COULD NOT FOPEN TERMINAL.
Level: 51
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 a CR" of this
manual.
MESSAGE: VT TERMINATED, INVALID DEVICE FOR SESSION.
Level: 52
CAUSE: Your session device is not an acceptable MPE session
device.
ACTION: Verify the configuration in
SYSGEN.
MESSAGE: NO DEVICE STRING SPECIFIED FOR REVERSE-VT.
Level: 53
CAUSE: The device string was omitted in the FOPEN or
file equation.
ACTION: Insert a device string.
MESSAGE: INVALID TERMINALL SPEED FOR
REVERSE-VT.
Level: 54
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.
MESSAGE: LOCAL NS GOING DOWN, CONNECTION FAILED.
Level: 55
CAUSE: The connection to the remote machine failed because
the local network services are going down.
ACTION: See Appendix A "Submitting a CR" to
this manual.
MESSAGE: ATTEMPT TO SET OR STEAL BREAK FAILED.
Level: 57
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.
MESSAGE: SET QUIESE IOQ FAILED.
Level: 58
CAUSE: The ATTACHIO failed with an abnormal completion
code.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: SET $BACK ENVIRONMENT INFO FAILED.
Level: 59
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.
Complete PDF