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