Troubleshooting Terminal, Printer and Serial Device Connections - Edition 4 (32022-90030)
114 Appendix A
TermDSM Messages
MESSAGE: You have entered an incorrect ROM code version.)
(TDSM 268) CAUSE: Incorrect ROM code version was entered for EEPROM
reprogramming.
ACTION: Re-enter the correct ROM code version.
MESSAGE: You have entered an incorrect ROM code version.)
(TDSM 270) CAUSE: The DTC has reported that the port in question is bad or does
not exist.
ACTION: Note the range of ports in the error message. If you are
specified a port that does not exist, verify the information to determine
the correct port. For reset and dump, you can specify an ldev number
instead of the port to do the operation.
If the port does exist, a hardware failure has probably occurred.
Contact you HP support representative. You can obtain additional
information by running the card selftest (through the SIC subcommand
of the TermDSM RESET command), the DTC selftest, and the DTC
offline diagnostics.
MESSAGE: That SIC is malfunctioning, or not installed. TermDSM can
not always tell the difference between 'not installed' and a serious
malfunction. (TDSM 271)
(TDSM 271) CAUSE: Possible hardware problem or no card is installed in that slot.
ACTION: Double check that the SIC number you specified is correct. If
it is, it is likely that the SIC is defective. Contact you HP support
representative. You can obtain additional information by running the
card selftest (through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline diagnostics.
MESSAGE: The loopback is too long. (TDSM 275)
(TDSM 275) CAUSE: Internal error.
ACTION: Contact you HP support representative.
MESSAGE: Dump failed. Open of DTCM failed, or DTC owned and not
overridden (TDSM 280)
(TDSM 280) CAUSE: This message is written to dump files, and never appears as an
error message to a user terminal.
If the user was informed the DTC was in use by another TermDSM (see
message 35), and the second user chose NOT to override, then this
message is normal and is not cause for alarm. Otherwise, it is indicative
of an internal error
ACTION: If the problem persists, take another dump. If you are sure
another user was not involved, contact your HP support representative.