HP 3000 Manuals HP 3000 Manuals
Appendix A TermDSM Messages
----------------------------------------------------------------------------------------
15 MESSAGE You have entered an unknown or incorrect command. Please try
again. (TDSM 15)
CAUSE You have entered something that is not a TermDSM command or a
command that is not valid in this context.
ACTION Commands that are valid at this time are listed in the prompt.
Please try again. Type HELP or refer to chapter 4 for more
information.
----------------------------------------------------------------------------------------
16 MESSAGE TermDSM has compiled without $partial eval$ in effect. It cannot
continue. This problem must be fixed at the factory. (TDSM 16)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
17 MESSAGE Your security level (3) is too low to use TermDSM. Please log on
with level 0, 1, or 2 security. (TDSM 17) For level 0, you need
SM capability. For level 1, you need SM or DI capability. For
level 2, you need SM or DI or OP capability.
CAUSE You do not have the correct user capabilities to use TermDSM.
ACTION Logon as a user with the correct capabilities for the TermDSM
functions you wish to use. Refer to chapter 4 for the security
levels of each command and subcommand.
----------------------------------------------------------------------------------------
18 MESSAGE You have entered a bad port number. Port numbers range from 0 to
7. (TDSM 18)
CAUSE The value you entered is not a number between zero and seven.
ACTION Enter a valid port number. Check the port number on the back of
the DTC if necessary.
----------------------------------------------------------------------------------------
19 MESSAGE The port number is missing or invalid. Port numbers range from 0
to 7. (TDSM 19)
CAUSE The port number was not entered or is unrecognizable.
ACTION Enter a valid port number. Refer to the prompt or chapter 4 for
syntax.
----------------------------------------------------------------------------------------
20 MESSAGE You have entered an c ldev number. Ldev numbers are positive
integers. (TDSM 20)
CAUSE The value that you entered as a logical device number is not a
number greater than zero.
ACTION Enter a valid ldev number. Note that you can also use the port
subcommand.
----------------------------------------------------------------------------------------
21 MESSAGE The ldev number is missing or invalid. Ldev numbers are positive
integers. (TDSM 21)
CAUSE The logical device number was not entered or is unrecognizable.
ACTION Enter a valid ldev number. Note that you can also use the port
subcommand.
----------------------------------------------------------------------------------------
22 MESSAGE You have entered an invalid SIC card number. SIC card numbers
range from 0 to 5. (TDSM 22)
CAUSE The card number that you entered in is not the range zero to
five.
ACTION Doublecheck the card numbers by looking at the back of the DTC.
Enter the card number again.
----------------------------------------------------------------------------------------
23 MESSAGE The SIC card number is missing or invalid. SIC card numbers
range from 0 to 5. (TDSM 23)
CAUSE The card number was not entered or is unrecognizable.
ACTION Enter the card number again. Refer to the prompt or chapter 4
for syntax.
----------------------------------------------------------------------------------------
24 MESSAGE You have entered an incorrect DTC number. Please choose a "DTC
number" from this list. (TDSM 24)
CAUSE The value entered does not correspond with any DTC on the
system.
ACTION The DTCs on the system are listed with their numbers. Enter one
of the numbers displayed.
----------------------------------------------------------------------------------------
25 MESSAGE The DTC number is missing or invalid. Please choose a "DTC
number" from this list. (TDSM 25)
CAUSE The DTC number was not entered or is unrecognizable.
ACTION The DTCs on the system are listed with their numbers. Enter on
of the numbers displayed.
----------------------------------------------------------------------------------------
27 MESSAGE TermDSM cannot do the dump because there are already too many
dump files. Please purge some. Dump files are of the form
TRMnnnaa.PUB.SYS. where nn is a 3 digit number and aa is 2
alphabetic characters. (TDSM 27)
CAUSE The dump files TRMAA through TRMdddZZ already exist. (The
sequence ddd is the current Julian date.)
ACTION Delete some files beginning with the file called TRMdddAA since
this is the oldest file. Note that if all files for this Julian
date already exist, there are over 600 dump files for today.
You can delete most of these files.
----------------------------------------------------------------------------------------
32 MESSAGE Your security level (3) is too low to take dumps. Please log on
with level 2 security to dump ports, or level 0 security to dump
ports and DTCs. (TDSM 32) For level 1, you need SM or DI
capability. For level 2, you need SM or DI or OP capability.
CAUSE You do not have the correct user capabilities to use this
function.
ACTION Log on with level 0, 1, or 2 security. Refer to chapter 4 for
the security levels of each command and subcommand.
----------------------------------------------------------------------------------------
34 MESSAGE That ldev does not exist. Please check the ldev number, or dump
the associated port instead. (TDSM 34)
CAUSE Although you entered a number in a range that could be an ldev
number, that ldev number is not configured on the system.
ACTION Verify the ldev number by entering the SHOWJOB command. You can
also dump information associated with the device by using the
PORT subcommand (which uses the physical address instead of the
ldev number).
----------------------------------------------------------------------------------------
35 MESSAGE That DTC is owned by another person running TermDSM. You may
override that user and continue. (WARNING : This may have
unpredictable results. It's safer to find the other user and
exit TermDSM. (TDSM 35) Do you want to override the other user
(yes or no)?
CAUSE More than one person is using TermDSM and directing operations
to the same DTC at the same time.
ACTION It is permissible for two or more users to run TermDSM
simultaneously as long as the users do not reference the same
DTC. In this case, message 35 will not appear. If one TermDSM
user chooses to override another by continuing, it is likely
that the overridden TermDSM will produce error messages. This
facility is provided for the case where a terminal running
TermDSM is hung and therefore cannot exit the program. Note
that if one TermDSM user resets the port of another TermDSM
user, this can cause the system to go down.
----------------------------------------------------------------------------------------
36 MESSAGE No ldevs seem to be configured on your system. (TDSM 356)
CAUSE Necessary configuration information does not exist on the
system.
ACTION Make sure the file NMCONFIG.PUB.SYS exists. Bring the system
down and back up again, making sure that the proper SYSGEN files
are used. (The SYSGEN files used are determined by the boot
path. The file NMCONFIG.PUB.SYS is used automatically.) If the
problem persists, contact your HP support representative.
----------------------------------------------------------------------------------------
37 MESSAGE The dump process can't find out the length of the data area.
(TDSM 37)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
38 MESSAGE The data area is longer than TermDSM's dump buffer. (TDSM 38)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
39 MESSAGE TermDSM never received a reply to its dump data area request.
(TDSM 39)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
42 MESSAGE You must have high (1) security to perform this function. (TDSM
42) For level 1, you need SM or DI capability.
CAUSE You do not have the correct user capabilities to use this
function.
ACTION Logon as a user with the correct capabilities for the TermDSM
functions you wish to use. Refer to chapter 4 for the security
levels of each command and subcommand.
----------------------------------------------------------------------------------------
43 MESSAGE You can't do this from your own DTC. Please run TermDSM from
another DTC or from the console. (TDSM 43)
CAUSE If you were permitted to selftest, dump, or reset the DTC to
which you are logged on, your session would be aborted and you
would be unable to get the test results.
ACTION Move to a terminal on another DTC or the system console to run
TermDSM.
----------------------------------------------------------------------------------------
44 MESSAGE Warning: This will reset all users on that DTC. As many as 48
terminal users could be affected. (TDSM 44)
CAUSE If you continue, all user sessions on this DTC will be aborted.
ACTION If you want to continue, you should alert all the users that
their sessions will be aborted.
----------------------------------------------------------------------------------------
56 MESSAGE Your answer must be at least 1 and no more than 65535. (TDSM 56)
CAUSE The value entered is not in the range 1 to 65535.
ACTION Enter a value in the range. Diagnostic loop counts are limited
to this range.
----------------------------------------------------------------------------------------
62 MESSAGE Use the CCTL option (:FILE LIST;DEV=LP;CCTL) when printing this
file. (TDSM 62)
CAUSE Informational message.
ACTION When printing the dump file, use the CCTL option in the print
file equation. This will format the printed output in an
organized way. Printed output of dump files will be acceptable
if they are not printed with the CCTL option.
----------------------------------------------------------------------------------------
64 MESSAGE The following two files make up the DTC dump. Please deliver
both to your HP representative. (TDSM 64)
CAUSE Informational message.
ACTION Document the problem (the reason you took a dump), and deliver
it to your HP support representative along with the dump files,
preferably on magnetic tape.
----------------------------------------------------------------------------------------
70 MESSAGE There are no DTCs configured on your system. (TDSM 70)
CAUSE Necessary configuration information does not exist on the
system.
ACTION Check the NMCONFIG.PUB.SYS file for proper DTC configuration
(using :NMMGR). Bring the system down and back up again. If the
problem persists, contact your HP support representative.
----------------------------------------------------------------------------------------
71 MESSAGE There are more DTCs on your system than TermDSM can reference.
Here are the ones TermDSM can reference. (TDSM 71)
CAUSE You are using more than 32 DTCs on the system. You will not be
able to perform any TermDSM functions on any DTCs that are not
listed in this message.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
80 MESSAGE You can't reset your own port or ldev. Please run TermDSM from a
different port or ldev to do this. (TDSM 80)
CAUSE Verify the ldev numbers entered. If you want to reset a port,
you cannot be logged on to that port; the operation will abort
your session.
ACTION If you want to reset the port you are using, move to another
port or the system console to run TermDSM.
----------------------------------------------------------------------------------------
81 MESSAGE That ldev is unknown (not configured). Please check the ldev
number, or use reset port. (TDSM 81)
CAUSE Although a number was entered in a range that could be an ldev
number, that number is not configured on the system.
ACTION Verify the ldev number by entering the SHOWJOB command. You can
also reset ports by using the PORT subcommand (which uses the
physical address instead of the ldev number).
----------------------------------------------------------------------------------------
82 MESSAGE You must have high (1) or medium (2) security to do resets, and
high (1) security to reset DTCs. (TDSM 82) For level 1, you need
SM or DI capability. For level 2, you need SM or DI or OP
capability.
CAUSE You do not have the correct user capabilities to do this
function.
ACTION Logon as a user with the correct capabilities for the functions
you wish to use. Refer to chapter 4 for the security level of
each command and subcommand.
----------------------------------------------------------------------------------------
86 MESSAGE You must have high (1) or medium (2) security to test ports, and
high (1) security to selftest DTCs. (TDSM 86) For level 1, you
need SM or DI capability. For level 2, you need SM or DI or OP
capability.
CAUSE You do not have the correct user capabilities to do this
function.
ACTION Logon as a user with the correct capabilities for the TermDSM
functions you wish to use. Refer to chapter 4 for the security
level of each command and subcommand.
----------------------------------------------------------------------------------------
93 MESSAGE TermDSM could not open the DTC manager, so the DTC dump could
not be obtained. (TDSM 93)
CAUSE Internal error, unless another TermDSM was being run against
that same DTC and you chose not to override the other user.
There is no error in this case.
ACTION Contact your HP support representative (if it is an internal
error).
----------------------------------------------------------------------------------------
110 MESSAGE You can't test your own port. Please run TermDSM from another
port. (TDSM 110)
CAUSE Doublecheck 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.
----------------------------------------------------------------------------------------
113 MESSAGE Please put a loopback hood on the port, before answering the
"How may times?" question. (TDSM 113)
CAUSE The hardware must be present before the diagnostic is run.
ACTION Refer to chapter 3 for information on port loopback tests.
----------------------------------------------------------------------------------------
114 MESSAGE Please connect and make ready (power on, remote mode, etc.) a
supported terminal, before answering the "How many times?"
question. (TDSM 114)
CAUSE The hardware must be present before the diagnostic is run.
ACTION Refer to chapter 3 for information on terminal loopback tests.
----------------------------------------------------------------------------------------
115 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)
CAUSE The hardware must be present before the diagnostic is run.
ACTION Refer to chapter 3 for information on the port test.
----------------------------------------------------------------------------------------
121 MESSAGE Warning: The LDM dump is suspect. Consecutive dumps did not
match. (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.
----------------------------------------------------------------------------------------
122 MESSAGE You can't reset your own SIC. Please run TermDSM from another
SIC or DTC, or from the console. (TDSM 122)
CAUSE Your own session is on this SIC (serial interface card). If you
wish to reset a SIC, you cannot be logged onto that card; 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 SIC, or to the system
console, to run TermDSM.
----------------------------------------------------------------------------------------
170 MESSAGE The Distributed Terminal Subsystem software does not exist.
Please verify that the NMCONFIG.PUB.SYS file is correct and
validated, and the system has booted up without errors. This
situation prevents TermDSM from continuing. (TDSM 170)
CAUSE The NMCONFIG.PUB.SYS file does not exist, or has no DTCs
configured.
ACTION Check the NMCONFIG.PUB.SYS file for proper DTC and terminal
configurations (using NMMGR), then shutdown and restart the
system.
----------------------------------------------------------------------------------------
200 MESSAGE DTC and mainframe software versions are incompatible. (TDSM 200)
CAUSE Incompatibilities were found between subsystem software on the
HP 3000 and subsystem software on the DTC.
ACTION Contact your HP support representative to check the DTCM and
download file versions with NMMAINT. If this is not the problem,
the cause is an internal error.
----------------------------------------------------------------------------------------
201 MESSAGE Bad message length. (TDSM 201)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
203 MESSAGE Invalid operation. (TDSM 203)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
204 MESSAGE Request not supported. (TDSM 204)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
205 MESSAGE Sub request not supported. (TDSM 205)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
206 MESSAGE Entity not supported. (TDSM 206)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
207 MESSAGE No such entity. (TDSM 207)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
208 MESSAGE No LABELM2 for entity. (TDSM 208)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
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. If 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.
CAUSE 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) 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
message 35 was designed to prevent this conflict.
CAUSE Internal error.
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 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.
----------------------------------------------------------------------------------------
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.
----------------------------------------------------------------------------------------
280 MESSAGE Dump failed. Open of DTCM failed, or DTC owned and not
overridden (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.
----------------------------------------------------------------------------------------
281 MESSAGE Dump failed: Send or Receive of dump request failed. (TDSM 281)
CAUSE An internal error. This message is written to dump files and
never appears as an error message to a user.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
282 MESSAGE Dump failed: Bad function in internal error reply to dump
request.(TDSM 282)
CAUSE An internal error. This message is written to dump files and
never appears as an error message to a user.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
283 MESSAGE Dump failed. Bad reply (llio) status from DTCM. (TDSM 283)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
290 MESSAGE Sorry, TermDSM does not provide services for the console. (TDSM
290)
CAUSE The user entered the ldev number of the physical console for a
reset or dump. TermDSM cannot act upon the physical console
port because it is not on the DTC. TermDSM can only operate on
ldev numbers and ports that are on the DTC. Note: The
discussion here is for the physical console, not a terminal
which has taken control of the logical console via the CONSOLE
command.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
300 MESSAGE IPC message received in wrong subque. (TDSM 300)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
301 MESSAGE DTCM port data area not initialized. (TDSM 301)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
302 MESSAGE Bad machine type found in RMP packet. (TDSM 302)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
303 MESSAGE Non supported download file type found in RMP packet. (TDSM 303)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
304 MESSAGE Bad source IEEE 802.3 address found in RMP packet. (TDSM 304)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
305 MESSAGE Bad session ID found in RMP packet. (TDSM 305)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
306 MESSAGE Bad path id received from NDM. (TDSM 306)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
307 MESSAGE Boot (download) complete message received before expected. (TDSM
307)
CAUSE It has finished the download of its operating firmware before
the DTCM expected it.
ACTION Look on the console for a "boot complete" message. Otherwise,
enter the command again. If the problem persists, contact your
HP support representative.
----------------------------------------------------------------------------------------
308 MESSAGE IO-get-frame failed. (TDSM 308)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
309 MESSAGE Unimplemented action called. (TDSM 309)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
310 MESSAGE Bad download file type. (TDSM 310)
CAUSE Possible corrupt download file.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
311 MESSAGE Bad reply from memory manager for Aux data area. (TDSM 311)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
312 MESSAGE DCC sent bad reply in response to config. data request. (TDSM
312)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
313 MESSAGE DTC did not request the configuration to be download. (TDSM 313)
CAUSE After a download, the DTC did not request its configuration.
ACTION Look at the console for a message saying "configuration
complete". Otherwise, enter the command again. If the problem
persists, contact your HP support representative.
----------------------------------------------------------------------------------------
314 MESSAGE DCC did not reply to configuration data request. (TDSM 314)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
315 MESSAGE Unexpected RMP packet received. (TDSM 315)
CAUSE Internal error.
ACTION Contact your HP support representative.
----------------------------------------------------------------------------------------
316 MESSAGE DTC unexpectedly requested configuration information to be
downloaded. (TDSM 316)
CAUSE The DTC requested its configuration information at a time the
DTCM did not expect it.
ACTION Monitor the console for messages saying the configuration is
complete. Otherwise, enter the command again. If the problem
persists, contact your HP support representative.