(TDSM) (contd) [ MPE/iX Error Messages Manual Volume III ] MPE/iX 5.0 Documentation
MPE/iX Error Messages Manual Volume III
(TDSM) (contd)
---------------------------------------------------------------
213 MESSAGE The DTC reported an error or failure. (TDSM 213)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
218 MESSAGE End of Record received. Time = xx msec. (TDSM
218)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
219 MESSAGE Too many characters came back. Time = xx msec.
(TDSM 219)
CAUSE More characters were returned than were sent.
Someone might have pressed a key on the terminal
under test, if this was a terminal loopback.
Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
220 MESSAGE Parity error. Time = xx msec. (TDSM 220)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
221 MESSAGE Hardware receive overrun. Time = xx msec. (TDSM
221)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
222 MESSAGE Framing error. Time = xx msec. (TDSM 222)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
223 MESSAGE SIC Buffer overflow. Time = xx msec. (TDSM 223)
CAUSE Internal error.
ACTION Contact you HP support representative.
---------------------------------------------------------------
226 MESSAGE No record separator in Vplus. Time = xx msec.
(TDSM 226)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
229 MESSAGE Read timeout (no data came back). Time = xx msec.
If external loopback, check loopback hood. If
terminal loopback, check connections, terminal
configuration, etc. (TDSM 229)
CAUSE No or too few characters came back from the
loopback.
ACTION If this is an internal loopback, this indicates a
hardware problem. Contact your 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.
If this is an external loopback, check the loopback
hood to verify that it is securely connected and on
the correct port. f this is a terminal loopback,
verify that a supported, powered on terminal is
securely connected to the proper port. Check baud
rate, parity, etc. Note that the terminal
configuration must match the configuration file,
not the state the terminal was in when it was last
used. If this does not help, run internal, then
external loopback to discriminate between a DTC
problem and a terminal/cabling problem.
---------------------------------------------------------------
230 MESSAGE Alternate end-of-record received. Time = xx msec.
(TDSM 230)
CAUSE Probable hardware failure.
ACTION Contact your 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.
---------------------------------------------------------------
231 MESSAGE Subsystem break. Time = xx msec. (TDSM 231)
CAUSE Probable hardware failure.
ACTION 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.
---------------------------------------------------------------
232 MESSAGE No modem was connected during the operation. Time
= xx msec. (TDSM 232)
CAUSE During the test, the modem on that port was
disconnected.
ACTION Reconnect the modem and try the test again. If the
failure continues, or if there was no modem in use
on that port, there is a probable hardware failure.
Contact your 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.
---------------------------------------------------------------
234 MESSAGE Console attention. Time = xx msec. (TDSM 234)
CAUSE Probable hardware failure.
ACTION Contact your 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.
---------------------------------------------------------------
235 MESSAGE Operation aborted. (TDSM 235)
CAUSE The operation was aborted by the DTC. Possibly, the
download file is invalid.
ACTION Verify the version and integrity of the download
file. Contact your HP support representative. You
can obtain additional information by running the
DTC selftest DTC selftest or the DTC offline
diagnostic.
---------------------------------------------------------------
236 MESSAGE End of dump file encountered. (TDSM 236)
CAUSE The end of the DTC upload (dump) file was
encountered when there was still more information
to write.
ACTION Verify that there is sufficient disc space (approx.
2200 sectors are required). Otherwise, contact
your HP support representative.
---------------------------------------------------------------
238 MESSAGE Security invalid. (TDSM 238)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
239 MESSAGE Bad packet. (TDSM 239)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
240 MESSAGE During a DTC reset/dump request from the
mainframe. (TDSM 240)
CAUSE Informational message which can be printed after an
error message. It describes in which phase of an
operation the error occurred.
ACTION Refer to the cause and action descriptions for the
actual error message preceding message 240.
---------------------------------------------------------------
241 MESSAGE During the DTC download operation. (TDSM 241)
CAUSE Informational message which may be printed after an
error message. It describes in which phase of an
operation the error occurred.
ACTION Refer to the cause and action descriptions for the
actual error message preceding message 241.
---------------------------------------------------------------
242 MESSAGE During a DTC upload (dump) operation. (TDSM 242)
CAUSE Informational message which may be printed after an
error message. It describes in which phase of an
operation the error occurred.
ACTION Refer to the cause and action descriptions for the
actual error message preceding message 242.
---------------------------------------------------------------
243 MESSAGE Bad parameter from TermDSM. (TDSM 243)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
244 MESSAGE Timeout waiting for the DTC to respond. The DTC
may be powered off, malfunctioning, or
misconfigured. (TDSM 244)
CAUSE The TermDSM command resulted in an instruction
being sent to a DTC, and the DTC did not respond.
ACTION Note that the DTC list printed by TermDSM is only a
list of the DTCs configured, not a list of
installed, powered on, and working DTCs. If the
DTC in question was working, and no changes were
made to the configuration file, ensure that the DTC
is powered on. If so, this error indicates a
probable hardware error. Contact your HP support
representative. If this is a new installation or
DTC, which has never been run before, the above
comments can still apply. However, if the
configuration is incorrect, a functional DTC might
still not respond. Check the configuration file,
power to the DTC, connections, etc. If problems
persist, contact your HP support representative.
This error can also be the result of a LAN problem.
If other DTC(s) are working on the same LAN, the
problem is probably related to the DTC or its
configuration. If there is only one DTC, or other
DTCs on the same LAN are unresponsive, then the LAN
hardware or software might be at fault. The LAN
diagnostic LANDAD can be run to investigate LAN
problems.
---------------------------------------------------------------
245 MESSAGE Write to IEEE 802.3 DAM failed. (TDSM 245)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
247 MESSAGE Bad Network Management packet received from DTC.
(TDSM 247)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
248 MESSAGE The DTC requested to be downloaded during the
operation. (TDSM 248)
CAUSE The DTC was trying to power up at the same time you
were trying to access it.
ACTION Wait for the download, or upload/download, to
complete (as shown by the console messages).
Verify then that the DTC is operational. If not,
contact your HP support representative.
---------------------------------------------------------------
249 MESSAGE The DTC requested that it be dumped during the
operation. (TDSM 249)
CAUSE The DTC detected an internal error at the same time
you were trying to access it through TermDSM.
ACTION Wait for the download, or upload/download, to
complete (as shown by the console messages). Then
verify if the DTC is operational. If not, contact
your HP support representative.
---------------------------------------------------------------
250 MESSAGE DTC and mainframe software versions are
incompatible. (TDSM 250)
CAUSE Incompatibilities were found between subsystem
software on the HP 3000 and subsystem software on
the DTC.
ACTION Contact your HP support representative.
---------------------------------------------------------------
251 MESSAGE Bad RMP packet received from DTC. (TDSM 251)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
252 MESSAGE Could not open the download or dump file. (TDSM
252)
CAUSE Files pertaining to this operation cannot be
accessed.
ACTION If this is a dump, verify that sufficient
disc space exists to create the dump file.
Approximately 2200 sectors of disc space is
required. If enough disc space is available (or if
you were not trying to perform a dump operation),
contact your HP support representative.
---------------------------------------------------------------
253 MESSAGE Unable to get a system timer. (TDSM 253)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
254 MESSAGE Software bug encountered. (TDSM 254)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
255 MESSAGE Dump overflow: DTC sent more data than expected.
(TDSM 255)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
256 MESSAGE MPE/XL create object failed. (TDSM 256)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
257 MESSAGE Unknown internal error. (TDSM 257)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
258 MESSAGE Application request timeout occurred. (TDSM 258)
CAUSE Internal error. This means two users of TermDSM
were directing TermDSM commands to the same DTC at
the same time, and the other TermDSM user answered
"yes" to the override question (see TermDSM message
35). Other error messages are likely to be printed
also, because your operations were interrupted.
These error messages should be ignored. There is
nothing wrong with multiple users of TermDSM
running at the same time, as long as they do not
try to direct commands to the same DTC at the same
time. The message and interlock system of TermDSM
message 35 was designed to prevent this conflict.''
ACTION Contact your HP support representative.
---------------------------------------------------------------
259 MESSAGE DTC not opened by this TermDSM. Possibly your
TermDSM was overridden by another TermDSM. (TDSM
259)
CAUSE Another user of TermDSM has explicitly overridden
your use of TermDSM.
ACTION Locate and coordinate users of TermDSM. This means
two users of TermDSM were directing TermDSM
commands to the same DTC at the same time, and the
other TermDSM user answered "yes" to the override
question (see TermDSM message 35). Other error
messages are likely to be printed. These error
messages should be ignored. There is nothing wrong
with multiple users of TermDSM running at the same
time, as long as they do not try to direct commands
to the same DTC at the same time. The message and
interlock system of message 35 was designed to
prevent this conflict.
---------------------------------------------------------------
260 MESSAGE Bad NMP error code received. (TDSM 260)
CAUSE Unknown error reported by the Distributed Terminal
Subsystem to TermDSM.
ACTION Contact your HP support representative.
---------------------------------------------------------------
261 MESSAGE Bad RMP error code received. (TDSM 261)
CAUSE Unknown error reported by the Distributed Terminal
Subsystem to TermDSM.
ACTION Contact your HP support representative.
---------------------------------------------------------------
262 MESSAGE The DTC subsystem has reported that an error was
detected. (TDSM 262)
CAUSE This is the standard message that precedes specific
error messages.
ACTION Follow the instructions for the error message that
follows this message.
---------------------------------------------------------------
263 MESSAGE An error of unknown type was reported by the DTS
subsystem. (TDSM 263)
CAUSE An error unknown to TermDSM was reported by the
Distributed Terminal Subsystem.
ACTION Contact your HP support representative.
---------------------------------------------------------------
264 MESSAGE The DTC reported an unknown status as a result of
the loopback. Time taken=xx. (TDSM 264)
CAUSE An error unknown to TermDSM was reported by the
Distributed Terminal Subsystem.
ACTION Contact your 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.
---------------------------------------------------------------
270 MESSAGE The port is malfunctioning, or not present on
that SIC. Modem SICs have ports zero to five, and
all other SICs have ports zero to seven. (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 your 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.
---------------------------------------------------------------
271 MESSAGE That SIC is malfunctioning, or not installed.
TermDSM can not always tell the difference between
!!not installed!! and a serious malfunction. (TDSM
271)
CAUSE Possible hardware problem or no card is installed
in that slot.
ACTION Doublecheck 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.
---------------------------------------------------------------
272 MESSAGE The operation was aborted because it was reset.
(TDSM 272)
CAUSE Another TermDSM user reset the operation while in
progress.
ACTION See message 246 for a discussion of multiple
TermDSM operations directed against the same DTC.
---------------------------------------------------------------
273 MESSAGE The modem on that port disconnected. (TDSM 273)
CAUSE The modem on that port was disconnected during the
operation.
ACTION Reconnect the modem and enter the command again.
If there was no modem, then this is an internal
problem. 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.
---------------------------------------------------------------
274 MESSAGE The DTC reported that an unexpected event
occurred. (TDSM 274)
CAUSE A user on that terminal might have entered CTRL Y
or pressed Break.
ACTION Try the operation again without touching the keys
on the terminal under test. If the is no change,
an internal error or hardware failure is indicated.
Contact your 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.
---------------------------------------------------------------
275 MESSAGE The loopback is too long. (TDSM 275)
CAUSE Internal error.
ACTION Contact your HP support representative.
---------------------------------------------------------------
MPE/iX 5.0 Documentation