 |
» |
|
|
|
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 “TermDSM Commands” for more information. |
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 Hewlett-Packard support representative. |
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 “TermDSM Commands” for the security levels of each command
and subcommand. |
MESSAGE: You have
entered a bad port number. Port numbers range from 0 to 23. (TDSM
18) | CAUSE:
You have entered an invalid port number. Port numbers range from
0 to 7 for DTC 16 and DTC 48, from 0 to 15 for DTC 16iX/16MX, and
from 0 to 23 for DTC 72MX. ACTION:
The port number was not entered or is unrecognizable. |
MESSAGE: The port
number is missing or invalid. Port numbers range from 0 to 23. (TDSM
19) | |
MESSAGE: You have
entered a bad 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. |
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. |
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 is not in the range from zero to
five. Card number range from 0 to 1 for DTC 16, 1 for DTC 16iX/16MX,
from 0 to 5 for DTC 48, and from 0 to 3 for DTC 72MX. ACTION:
Double check the card numbers by looking at the back of the DTC.
Enter the card number again. |
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 “TermDSM Commands” for syntax. |
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. |
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 one
of the numbers displayed. |
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 nnn is a 3 digit number and aa is 2 alphabetic characters.
(TDSM 27) | CAUSE:
The dump files TRMdddAA
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. |
MESSAGE: Your security
level (3) is too low to take dumps. Please log on with level 2 security
to dump ports, or level 1 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 “TermDSM Commands” for the security
levels of each command and subcommand. |
MESSAGE: Your security
level is too low to reprogram EEPROM. Please log on with level 1
security to reprogram EEPROM. (TDSM 33) For level 1, you need SM or DI capability. | CAUSE:
You do not have the correct user capabilities to use this function. ACTION:
Log on with level 1 security. Refer to Chapter 4 “TermDSM Commands” for the security levels of each command
and subcommand. |
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). |
MESSAGE: Someone
else is using TermDSM to troubleshoot that DTC. Find that person
and have them exit TermDSM. If you cannot locate that user, you
may override them. (TDSM 35) | 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. The override 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. |
MESSAGE: No ldevs
seem to be configured on your system. (TDSM 36) | 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. |
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. |
MESSAGE: The data
area is longer than TermDSM's dump buffer. (TDSM 38) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: TermDSM
never received a reply to its dump data area request. (TDSM 39) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
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 “TermDSM Commands” for the security levels of each command
and subcommand. |
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. |
MESSAGE: Warning:
This will reset all users on that DTC. (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. |
MESSAGE: Warning:
This will reset all users on that SNP. As many as 256 virtual circuits
could be affected. (TDSM 45) | CAUSE:
If you continue, all user sessions on this SNP will be aborted. ACTION:
If you want to continue, you should alert all the users that their
sessions will be aborted. |
MESSAGE: Warning:
This will abort all users on that MUX. As many as 24 users could
be affected. (TDSM 49) | CAUSE:
If you continue, all user sessions on this asynchronous processor
board (mux card) on the DTC 72MX will be aborted. ACTION:
If you want to continue, you should alert all the users that their
sessions will be aborted. |
MESSAGE: Warning:
There will be no file created to keep the trace data. To get the
trace data, please perform a port dump BEFORE stopping the trace.
(TDSM 50) | CAUSE:
Extended tracing on a port on an asynchronous processor board will
not be stored into a disk file. ACTION:
Before terminating an extended tracing on a port with TRACEOFF,
do a port dump to keep the trace data into a disk file. |
MESSAGE: Warning:
The trace data will be overwritten by this command. To get the trace
data, please perform a port dump first. (TDSM 51) | CAUSE:
This warning is issued when you enter the TRACEOFF
subcommand. ACTION:
To save the trace data on an asynchronous port, do a port dump before
issuing the TRACEOFF subcommand
to terminate extended tracing. |
MESSAGE: Each DTC
selftest can take as long as 7 minutes. Enter a Control-Y to stop
the selftest loop (the Control-Y will take effect when the current
selftest finishes). (TDSM 53) | CAUSE:
This warning is issued when you issue a SELFTEST
subcommand to initiate DTC selftest. ACTION:
Continue with the DTC selftest if you want. You can terminate selftest
anytime by pressing [CTRL]-Y. |
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. |
MESSAGE: Please deliver
the following SNP dump to your HP representative. (TDSM 63) | CAUSE:
Informational message. ACTION:
Document the problem (the reason you took the dump), and deliver
it to your HP support representative along with the dump file, preferably
on magnetic tape. |
MESSAGE: The following
two files make up the DTC dump. Please deliver both to your HP representative.
(TDSM 64) | CAUSE:
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. ACTION:
Please deliver the following VC dump to your HP representative.
(TDSM 65) |
MESSAGE: Please deliver
the following VC dump to your HP representative. (TDSM 65) | 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. |
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. |
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 120 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. |
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. |
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). |
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 “TermDSM Commands” for the security level of each command
and subcommand. |
MESSAGE: You must
have high (1) or medium (2) security to test ports, and high (1)
security to selftest 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 “TermDSM Commands” for the security level of each command
and subcommand. |
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). |
MESSAGE: You can't
test your own port. Please run TermDSM from another port. (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) | 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) | 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) | 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) | 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) | 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. |
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. |
MESSAGE: You can't
reset your own SNP. Please run TermDSM from another PAD or SIC or
DTC, or from the console. | CAUSE:
Your own session is on this SNP (DTC/X.25 XL Network Access card).
If you wish to reset an SNP you cannot be logged onto that card. ACTION:
Move to a port on a different PAD, DTC, or SNP, or to the system
console, to run TermDSM. |
MESSAGE: You can't
dump your own SNP. Please run TermDSM from another PAD or SIC or
DTC, or from the console. | CAUSE:
Your own session is on this SNP (DTC/X.25 XL Network Access card).
If you wish to dump an SNP you cannot be logged onto that card. ACTION:
Move to a port on a different PAD, DTC, or SNP, or to the system
console, to run TermDSM. |
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 180) | CAUSE:
The NMCONFIG.PUB.SYS file does
not exist, or has no DTCs configured. ACTION:
Check the NMCONFIG.PUB.SYS file
for proper DTC/terminal configurations and validate (using NMMGR),
then shutdown and restart the system. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
MESSAGE: SIC Buffer
overflow. Time = xx msec. (TDSM 223) | CAUSE:
Internal error. ACTION:
Contact you HP support representative. |
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. |
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. |
MESSAGE: Alternate
end-of-record received. Time = xx msec. (TDSM 230) | 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. |
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. |
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. |
MESSAGE: Console
attention. Time = xx msec. (TDSM 234) | 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. |
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. |
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. |
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. |
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. |
MESSAGE: Bad parameter
from TermDSM. (TDSM 243) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The TermDSM
command resulted in an instruction being sent to a DTC, and the
DTC did not respond. | CAUSE:
Timeout waiting for the DTC to respond. The DTC may be powered off,
malfunctioning, or misconfigured. (TDSM 244) 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. |
MESSAGE: Write to
IEEE 802.3 DAM failed. (TDSM 245) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: This DTC
is owned by another TermDSM. Possibly, your TermDSM was overridden
by that TermDSM. | CAUSE:
Only one TermDSM session may be active at one time on a DTC. Possibly,
another TermDSM session was started on the DTC and has overwritten
your original TermDSM session. ACTION:
Find out who else is running TermDSM on the DTC. Coordinate your
effort with the other user to avoid TermDSM session conflict. |
MESSAGE: Bad NMP
packet received from DTC. (TDSM 247) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
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. |
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. |
MESSAGE: DTC and
host RMP 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. |
MESSAGE: Bad RMP
packet received from DTC. (TDSM 251) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
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 disk space exists to create
the dump file. Approximately 2200 sectors of disk space is required.
If enough disk space is available (or if you were not trying to
perform a dump operation), contact your HP support representative. |
MESSAGE: Unable to
get a system timer. (TDSM 253) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Dump overflow:
DTC sent more data than expected. (TDSM 255) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Dump overflow:
DTC sent more data than expected. (TDSM 255) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
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. |
MESSAGE: Bad RMP
return code received. (TDSM 261) | CAUSE:
Unknown error reported by the Distributed Terminal Subsystem to
TermDSM. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
subsystem has reported that an error was detected. Here is the specific
message: (TDSM 262) | CAUSE:
This is the standard message that precedes specific error messages. ACTION:
Contact your HP support representative. |
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. |
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. |
MESSAGE: Please perform
a DTC reset instead of board reset. (TDSM 266) | CAUSE:
The DTC 16iX/16MX has only one board; resetting a board is the same
as resetting a DTC. ACTION:
Do a DTC reset instead of a board reset. |
MESSAGE: Please perform
a DTC upload instead of board upload. (TDSM 267) | CAUSE:
The DTC 16iX/16MX has only one board; uploading a board is the same
as uploading a DTC. ACTION:
Do a DTC upload instead of a board upload. |
MESSAGE: You have
entered an incorrect ROM code version.) | 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.) | 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.) | 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) | 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) | CAUSE:
Internal error. ACTION:
Contact you HP support representative. |
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. |
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 you HP support representative. |
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 you HP support representative. |
MESSAGE: Dump failed.
Bad reply (llio) status from DTCM. (TDSM 283) | CAUSE:
An internal error. ACTION:
Contact you HP support representative. |
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 you HP support representative. |
MESSAGE: Unknown
download file requested in RMP packet. (TDSM 303) | CAUSE:
An internal error. ACTION:
Contact you HP support representative. |
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. |
MESSAGE: Unable to
get an LLIO message frame. (TDSM 308) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: DTCM produced
an unknown action code. (TDSM 309) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Unable to
get an outbound packet buffer. (TDSM 317) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Unable to
write to an outbound packet buffer. (TDSM 318) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Unable to
send an LLIO message. (TDSM 319) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: DTCM encountered
an unspecified error. (TDSM 320) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: DTCM captured
an unknown escapecode. (TDSM 321) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: DTC configuration
file too large for buffer. (TDSM 322) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: Please reset
or dump the specific PAD VC from ldev option. (TDSM 323) | CAUSE:
The user attempted to reset or dump a PAD VC using the VC
subcommand. PAD connections can only be dumped or reset from the
Ldev subcommand. ACTION:
Determine the ldev number that is associated with the PAD connection
and retry the reset or dump operation using the Ldev
subcommand. |
MESSAGE: The system
is a HOST BASED X25. However the specified DTC has no SNP card.
(TDSM 324) | CAUSE:
There is no DTC/X.25 XL Network Access (SNP) card mounted in the
DTC that you specified in the TermDSM command. ACTION:
Verify the number that TermDSM associated with the DTC containing
the DTC/X.25 XL Network Access card. Reenter the command with the
correct DTC number specified. |
MESSAGE: Some other
DTC is already tracing. (TDSM 325) | CAUSE:
Only one DTC can be tracing at a time. ACTION:
Turn off tracing on the other DTC and try again. |
MESSAGE: This requested
DTC is already tracing. (TDSM 326) | CAUSE:
Tracing has already been turned on for the specified DTC. ACTION:
None required. |
MESSAGE: This DTC
is not tracing. (TDSM 327) | CAUSE:
Tracing is turned off on the specified DTC. ACTION:
Turn on tracing for the specified DTC. |
MESSAGE: Invalid
board number — out of range. (TDSM 328) | CAUSE:
The specified board number does not exist. ACTION:
Check the board installed in the DTC and re-specify the correct
board number. |
MESSAGE: Indicated
board is absent or is not an SNP card. (TDSM 329) | CAUSE:
The board specified does not exist in the DTC or is not an SNP card. ACTION:
Verify that the required board is in the DTC. If you are trying
to configure an SNP board, verify that the board you specified is
an SNP board. |
MESSAGE: Trace file
could not be opened. (TDSM 330) | CAUSE:
The file where tracing messages are logged could not be opened. ACTION:
Contact your HP support representative. |
MESSAGE: X.25 has
not been started on indicated SNP card. (TDSM 332) | CAUSE:
The specified SNP card has not had X.25 started up on it. ACTION:
Contact your HP support representative. |
MESSAGE: X.25 is
not configured for indicated SNP card. (TDSM 331) | CAUSE:
The indicated SNP card does not have X.25 configured for it. ACTION:
Contact your HP support representative. |
MESSAGE: X.25 or
X.25/PADSUP not stopped. (TDSM 333) | CAUSE:
The operation you attempted required that X.25 or X.25/PADSUP be
stopped and it was still running. ACTION:
Start up X.25 on the specified card and try again or specify a card
that has X.25 started. |
MESSAGE: DTCM reports
unexpected SIC UPLOAD request. (TDSM 334) | CAUSE:
Internal error. ACTION:
Contact your HP representative. |
MESSAGE: This port
is already under extended trace. (TDSM 335) | CAUSE:
Informational message. ACTION:
Issue the TRACESHOW command to see which ports
on the DTC are currently under extended trace. |
MESSAGE: Another
port on this MUX is already under extended trace. (TDSM 336) | CAUSE:
Only one port on an asynchronous processor board (mux card) can
have extended trace at one time. ACTION:
Turn off extended tracing on a traced port before activating extended
tracing on another port on the same asynchronous processor board. |
MESSAGE: No port
on this MUX is under extended trace. (TDSM 337) | CAUSE:
Informational message. ACTION:
You may issue the TRACEON command to activate
extended tracing on any port on this asynchronous processor board
(mux card). |
MESSAGE: DTCM reports
that DTC reset is not complete yet. (TDSM 338) | CAUSE:
A TermDSM command has been issued against a DTC that is currently
undergoing selftest. ACTION:
A DTC selftest may take up to seven minutes. Wait for this duration
before issuing a TermDSM command against the DTC. |
MESSAGE: This is
not a DTC 72MX, DTC 16iX, or DTC 16MX. (TDSM 339) | CAUSE:
A TermDSM command that is only valid for DTC 72MX/16iX/16MX is issued
against a DTC 16 or DTC 48. ACTION:
Do not use this TermDSM command on a DTC 16 or DTC 48. |
MESSAGE: This is
not a MUX board. (TDSM 340) | CAUSE:
A TermDSM command that is only valid for asynchronous processor
boards (MUX board) on DTC 72MX is issued against a wrong type of
card. ACTION:
Verify that you have specified the right DTC number and board number
on the DTC. Only asynchronous processor boards on DTC 72MX can accept
this TermDSM command. |
MESSAGE: The DTC
is not up during showtrace on a MUX board. (TDSM 341) | CAUSE:
A TRACESHOW command has been issued against a
DTC that is not up. ACTION:
Verify that you have specified that right DTC number. The DTC must
be up in order for a TRACESHOW to list ports
with extended tracing. |
MESSAGE: You cannot
reset a LAN board. (TDSM 342) | CAUSE:
A RESET MUX command was issued against a LAN
board on a DTC 72MX. ACTION:
Verify the board number in the RESET MUX command.
You cannot reset a LAN board on a DTC 72MX. You can only reset asynchronous
processor boards (mux cards on a DTC 72MX). |
MESSAGE: Hardware
loopback is not supported on a DTC 72MX, DTC 16iX, or DTC 16MX.
(TDSM 343) | CAUSE:
A hardware loopback was issued against a DTC 72MX, DTC 16iX, or
DTC 16MX. Hardware loopback is only supported on DTC 16 and DTC
48. ACTION:
Verify the DTC number on the TermDSM command. Make sure the DTC
is a not a DTC 72MX, DTC 16iX, or DTC 16MX. |
MESSAGE: The DTC
returned an NMP error code of !. (TDSM 400) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP version mismatch. (TDSM 401) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP token error or unknown VC number during DUMP. (TDSM
402) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP bad port. (TDSM 403) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP loopback aborted. (TDSM 404) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP loopback modem error. (TDSM 405) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an NMP loopback time out. (TDSM 406) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an UNKNOWN VC number. (TDSM 407) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
returned an RMP error code of !. (TDSM 450) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an RMP version mismatch. (TDSM 451) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported an RMP token error. (TDSM 452) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The DTC
reported a SIC board not up. (TDSM 500) | CAUSE:
The serial interface card (SIC) in the DTC is not working. ACTION:
Contact your HP support representative. |
MESSAGE: The llio
error occurred when TERMDSM tried to get SYSBASE. (TDSM 590) | CAUSE:
Internal Error. ACTION:
Contact your HP support representative. |
MESSAGE: The system
is PC BASED. TERMDSM doesn't support PC BASED. (TDSM 591) | CAUSE:
The user attempted to run TermDSM on a system managed by the OpenView
DTC Manager. Such systems are said to be "PC-based,"
and TermDSM is not supported on PC-based systems. ACTION:
See the manual titled Using HP OpenView DTC Manager
for information on obtaining diagnostic information for terminal
and printer connections on PC-based systems. |
MESSAGE: The system
is HOST BASED TIO. TERMDSM only supports X25 functions on HOST BASED
X25. (TDSM 592) | CAUSE:
The user entered an X.25 diagnostic command while running TermDSM
on a host-based system that is not configured to support X.25 connections.
X.25 commands are not available on systems that support terminal
(TIO) I/O only. ACTION:
None. (Consult this manual to determine which TermDSM commands are
supported on host-based systems configured for TIO only.) |
MESSAGE: You have
entered an invalid SNP card number. SNP card numbers range from
0 to 5. (TDSM 604) | CAUSE:
The user entered an invalid number when asked to specify the card
number of the DTC/X.25 Network Access card (SNP card). ACTION:
Enter the number of the DTC slot that contains the SNP card on which
you want the TermDSM command to operate. SNP cards are allowed in
slots 0 through 3 for DTC 72MX, slots 1 through 5 for DTC 48,
and 2 for DTC 16; therefore, the valid range for the SNP card number
is 0 through 5. For example, to execute a DUmp command
for an SNP card contained in slot 3 of the DTC designated as DTC
#1, you would enter the following subcommand at the DUmp
subcommand prompt: SN 1,3 |
MESSAGE: The SNP
card number is missing or invalid. SNP card numbers range from 0
to 5. (TDSM 605) | CAUSE:
The user entered a TermDSM subcommand specifying the SNp
option but did not specify a valid DTC/X.25 Network Access card
(SNP) number. ACTION:
Reenter the subcommand specifying a valid card number for the SNP
card. The SNP card number corresponds to the slot number in the
DTC where the card is contained. The valid range of SNP card numbers
is 0 to 3 for DTC 72MX, 1 through 5 for DTC 48, and 2 for DTC 16. For example, to execute a DUmp command
for an SNP card contained in slot 3 of the DTC designated as DTC
#1, you would enter the following subcommand at the DUmp
subcommand prompt: SN 1,3 |
MESSAGE: You have
entered a bad VC number. VC numbers range from 0 to 4095. (TDSM
606) | CAUSE:
The user entered an invalid number when asked to specify the VC
number associated with the virtual circuit on which the TermDSM
function is to be performed. ACTION:
Enter the number that corresponds to the VC on which the TermDSM
function is to be performed. Valid numbers range from 0 to 4095. |
MESSAGE: The VC number
is missing or invalid. VC numbers range from 0 to 4095. (TDSM 607) | CAUSE:
The user entered a TermDSM subcommand specifying the VC
option but did not specify a valid VC (virtual circuit) number. ACTION:
Reenter the subcommand specifying a valid VC number. Virtual circuits
may be numbered from 0 through 4095. For example, to execute a DUmp command
for VC #15 active on an SNP card in slot 3 of DTC #1, you would
enter the following subcommand at the DUmp subcommand
prompt: V 1,3,15 |
MESSAGE: You have
entered an invalid X25 address. The X25 address may be up to 15
digits from 0 to 9. (TDSM 608) | CAUSE:
The user entered an invalid X.25 address during execution of the
XNetwork subcommand of the DIag
function of TermDSM. ACTION:
Determine the correct X.25 destination address as configured on
the Level 3 Configuration screen in NMMGR. Reenter the XNetwork
subcommand using the correct X.25 address. For example, to perform a loopback for an SNP card contained
in slot 3 of the DTC designated as DTC #1, with a destination address
configured as 345678, you would enter the following subcommand at
the DIag subcommand prompt: XN 1,3,345678 |
MESSAGE: The X25
address is missing or invalid. The X25 address may be up to 15 digits
from 0 to 9. (TDSM 609) | CAUSE:
The user failed to enter a valid X.25 address during execution of
the XNetwork subcommand of the DIag
function of TermDSM. ACTION:
Determine the correct X.25 destination address as configured on
the Level 3 Configuration screen in NMMGR. Reenter the XNetwork
subcommand using the correct X.25 address. For example, to perform a loopback for an SNP card contained
in slot 3 of the DTC designated as DTC #1, with a destination address
configured as 345678, you would enter the following subcommand at
the DIag subcommand prompt: XN 1,3,345678 |
MESSAGE: You have
entered a bad X25 status option. X25 status options range from 1
to 4. (TDSM 610) | CAUSE:
The user entered an invalid status option for the SNp
subcommand of the TermDSM STatus function. ACTION:
Reenter the subcommand using one of the valid status options, as
follows: 1 = Global 2 = Level 2 3 = Level 3 4 = PAD For example, to obtain information about the status of PAD
support on an SNP card contained in slot 3 of the DTC designated
as DTC #1, you would enter the following subcommand at the status
subcommand prompt: SN 1,3,4 |
MESSAGE: The X25
status option is missing or invalid. X.25 status options range from
1 to 4. (TDSM 611) | CAUSE:
The user failed to enter a valid status option for the SNp
subcommand of the TermDSM STatus function. ACTION:
Reenter the subcommand using one of the valid status options, as
follows: 1 = Global 2 = Level 2 3 = Level 3 4 = PAD For example, to obtain information about the status of PAD
support on an SNP card contained in slot 3 of the DTC designated
as DTC #1, you would enter the following subcommand at the status
subcommand prompt: SN 1,3,4 |
MESSAGE: You have
entered a bad X25 trace option. X25 trace options range from 1 to
3. (TDSM 612) | CAUSE:
The user entered an invalid trace option for the TermDSM TRACEON
function. ACTION:
Reenter the command using one of the valid trace options, as follows: 1 = VC 2 = Level 2 3 = Level 3 For example, to turn on a level 2 trace for an SNP card contained
in slot 3 of the DTC designated as DTC #1, you would enter
the following: TRACEON 1,3,2 |
MESSAGE: The X25
trace option is missing or invalid. X25 trace options range from
1 to 3. (TDSM 613) | CAUSE:
The user failed to enter a valid trace option for the TermDSM TRACEON
function. ACTION:
Reenter the command using one of the valid trace options, as follows: 1 = VC 2 = Level 2 3 = Level 3 For example, to turn on a level 2 trace for an SNP card contained
in slot 3 of the DTC designated as DTC #1, you would enter
the following: TRACEON 1,3,2 |
MESSAGE: You have
entered a bad linkname. X25 linkname may be up to 8 ASCII characters.
(TDSM 614) | CAUSE:
During execution of the TRACEON
function, the user entered an invalid linkname. ACTION:
Enter a valid linkname for the trace file. This is the linkname
as configured in NMMGR and can be up to 8 ASCII characters. |
MESSAGE: The X25
linkname is missing or invalid. X25 linkname may be up to 8 ASCII
characters. (TDSM 615) | CAUSE:
During execution of the TRACEON
function, the user failed to enter a valid X.25 linkname. ACTION:
Enter a valid file name for the trace file. The file name can be
up to 8 alphanumberic characters and must start with a letter. |
MESSAGE: TRACE will
be used as X25 trace filename by default. (TDSM 617) | CAUSE:
During execution of the TRACEON
function, the user pressed the carriage return when prompted for
a trace file name. ACTION:
None. This message is for information only. |
MESSAGE: There is
no TRACE in progress. (TDSM 618) | CAUSE:
The user entered a TRACEOFF command
to stop a trace but there was no trace active. ACTION:
None. This message is for information only. |
MESSAGE: You have
entered an invalid ROM version. The ROM version is made up of 8
ASCII characters. (TDSM 630) | CAUSE:
During execution of the reprogramming EEPROM process, the user entered
an invalid ROM version. ACTION:
Enter a valid ROM version for the reprogramming EEPROM process. |
MESSAGE: The ROM
version is missing or invalid. The ROM version is made up of 8 ASCII
characters. (TDSM 631) | CAUSE:
During execution of the reprogramming EEPROM process, the user failed
to enter a ROM version or entered an invalid ROM version. ACTION:
Enter a valid ROM version for the reprogramming EEPROM process. |
MESSAGE: TermDSM
did not set the DTC to IDLE during
EEPROM reprogramming. (TDSM 634) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: The EEPROM
reprogramming was successfully completed. (TDSM 635) | CAUSE:
This message is for information only. ACTION:
None. This message is for information only. |
MESSAGE: The EEPROM
reprogramming process is executing. The process takes about 7-10
minutes. Warning: Interrupting the process can be fatal to the DTC.
(TDSM 636) | CAUSE:
Warning message. ACTION:
None. This message is for information only. |
MESSAGE: TermDSM
will now reprogram EEPROM with version XXX. (TDSM 637) | 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. |
MESSAGE: Fatal error
occurred during EEPROM reprogramming process. Please contact HP
representative to recover the DTC. (TDSM 638) | CAUSE:
Internal error. ACTION:
Contact your HP support representative. |
MESSAGE: You have
entered an invalid MUX board number. MUX board numbers range from
0 to 3. (TDSM680) | CAUSE:
The MUX board number you have entered is not in the range from 0
to 3 ACTION:
Double check the MUX board number by looking at the back of the
DTC 72MX. Enter the board number again. This TermDSM command is
only supported for asynchronous processor boards on DTC 72MX. |
MESSAGE: The MUX
board is missing or invalid. MUX board numbers range from 0 to 3.
(TDSM 681) | CAUSE:
The MUX board number was not entered or is unrecognizable. ACTION:
Enter the MUX board number again. Refer to the prompt or Chapter 4 “TermDSM Commands” for syntax. This
command is only supported for asynchronous processor boards on DTC
72MX. |
MESSAGE: You have
entered a bad port number. Port numbers range from 0 to 23. (TDSM
682) | CAUSE:
The port number that you entered is not in the range from zero to
23. ACTION:
Double check the port number by looking at the device connection
on the DTC. Enter the port number again. This command is only supported
for ports on DTC 72MX. |
MESSAGE: The port
number is missing or invalid. Port numbers range from 0 to 23. (TDSM
683) | CAUSE:
The port number was not entered or is unrecognizable. ACTION:
Enter the port number again. Refer to the prompt or Chapter 4 “TermDSM Commands” for syntax. This
command is only supported for ports on DTC 72MX. |
MESSAGE: Please put
a loopback hood on the SNP card before answering the "How
many times?" question. (TDSM 700) | CAUSE:
A loopback hood must be in place before the diagnostic is run. ACTION:
Place loopback hood on the SNP card and continue. |
MESSAGE: Please set
up the environment for the network loopback test on the SNP card
before answering the 'How may times?' question. (TDSM 701) | CAUSE:
Supported hardware must be present and ready before the diagnostic
is run. ACTION:
Make the appropriate hardware ready and continue. |
MESSAGE: Termdsm
could not open the DTC manager, so the SNP dump could not be obtained.
(TDSM 720) | 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 you HP support representative (if it is an internal error). |
MESSAGE: Dump fail:
Send or Receive of dump request failed. (TDSM 721) | CAUSE:
Internal error. ACTION:
Contact you HP support representative. |
MESSAGE: Dump failed:
Bad function in reply to dump request. (TDSM 722) | CAUSE:
Internal error. ACTION:
Contact you HP support representative. |
MESSAGE: Dump failed:
Bad reply (llio) status from DTCM. (TDSM 723) | CAUSE:
Internal error. ACTION:
Contact you HP support representative. |
MESSAGE: Timeout
(no response from the network). Verify the physical connection to
the network, and ensure that the X25 address is correctly configured.
(TDSM 800) | CAUSE:
A timeout occurred before TermDSM received a response from the network. ACTION:
Make sure all physical network connections are in place. If physical
connections are OK, run NMMGR to verify that the X.25 address is
correctly configured. If the problem persists, contact you HP support
representative. |
MESSAGE: The call
has been accepted by another node on the network. Verify the correct
configuration of the X25 address. (TDSM 801) | CAUSE:
The user was attempting to perform a loopback test, but the connection
was accepted by a different node on the network. This could happen
if the X.25 address configured for loopback belongs to a different
system instead of the local system. ACTION:
Run NMMGR and correct the X.25 address configured for loopback on
the level 3 configuration screen. |
MESSAGE: The call
has been refused by the network. Verify the address configuration
and the number of VCs configured. (TDSM 802) | CAUSE:
The user was attempting to perform a loopback test on an SNP card
but the network would not accept the call. ACTION:
Run NMMGR to correct any problems with the DTC/X.25 Network Access
card (SNP card) configuration. |
MESSAGE: Bad card.
(TDSM 803) | CAUSE:
The DTC/X.25 Network Access card (SNP) being tested is bad. ACTION:
Contact your HP support representative. |
MESSAGE: All ports
are bad. (TDSM 804) | CAUSE:
All ports on the DTC/X.25 Network Access card (SNP) being tested
are bad. ACTION:
Contact your HP support representative. |
MESSAGE: Some ports
are bad. (TDSM 805) | CAUSE:
Some ports on the DTC/X.25 Network Access card (SNP) being tested
are bad. ACTION:
Contact your HP support representative. |
MESSAGE: Unknown
Cable. (TDSM 806) | CAUSE:
TermDSM does not recognize the cable interfacing the DTC/X.25 Network
Access card (SNP card) to the network. ACTION:
Replace cable with a supported network interface cable. |
|
