Troubleshooting Terminal, Printer and Serial Device Connections - Edition 4 (32022-90030)

106 Appendix A
TermDSM Messages
MESSAGE: You can’t test your own port. Please run TermDSM from
another port. (TDSM 110)
(TDSM 110) CAUSE: Double check the numbers entered. If you wish to test a port,
you cannot be logged on to that port; the operation will abort your
session and you will be unable to obtain the results of the test.
ACTION: If you want to test the port to which you are logged on, move
to another port or the system console to run TermDSM.
MESSAGE: Please put a loopback hood on the port, before answering
the “How may times?” question. (TDSM 113)
(TDSM 113) CAUSE: A loopback hood must be in place before the diagnostic is run.
ACTION: Place loopback hood on the port and continue.
MESSAGE: Please connect and make ready (power on, remote mode,
etc.) a supported terminal, before answering the 'How many times?'
question. (TDSM 114)
(TDSM 114) CAUSE: The hardware must be present before the diagnostic is run.
ACTION: Make a supported terminal ready and continue.
MESSAGE: Please connect and make ready (power on, remote mode,
etc.) a supported printer (or terminal), before answering the “How
many times?” message. (TDSM 115)
(TDSM 115) CAUSE: The hardware must be present before the diagnostic is run.
ACTION: Make a supported printer (or terminal) ready and continue.
MESSAGE: You can’t reprogram EEPROM on your own DTC. Please
run TermDSM from another DTC or from the console. (TDSM 118)
(TDSM 118) CAUSE: Your own session is on this DTC. If you wish to reprogram
EEPROM, you can’t be logged onto that DTC; the operation will abort
your session and you will be unable to obtain the results.
ACTION: Move to a port on a different DTC or to the system console to
run TermDSM.
MESSAGE: Warning: The LDM dump is suspect. Consecutive dumps
did not match. (TDSM 121)
(TDSM 121) CAUSE: This message is written to dump files and never appears as an
error message to a user. There was activity during the dump process, so
part of the dump relating to the Logical Device Manager might be
inconsistent with the rest of the dump.
ACTION: Submit the dump to your HP support representative.