(TDSM)

You have entered an unknown or incorrect command. Please try again. (TDSM 15)

You have entered something that is not a TermDSM command or a command that is not valid in this context.

Commands that are valid at this time are listed in the prompt. Please try again. Type HELP or refer to the reference documentation for more information.

TermDSM has compiled without $partial eval$ in effect. It cannot continue. This problem must be fixed at the factory. (TDSM 16)

Internal error.

Contact your HP support representative.

Your security level (3) is too low to use TermDSM. Please log on with level 0, 1, or 2 security. (TDSM 17)

You do not have the correct user capabilities to use TermDSM. 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.

Logon as a user with the correct capabilities for the TermDSM functions you wish to use. Refer to reference documentation for the security levels of each command and subcommand.

You have entered a bad port number. Port numbers range from 0 to 7. (TDSM 18)

The value you entered is not a number between zero and seven.

Enter a valid port number. Check the port number on the back of the DTC if necessary.

The port number is missing or invalid. Port numbers range from 0 to 7. (TDSM 19)

The port number was not entered or is unrecognizable.

Enter a valid port number. Refer to the reference documentation for syntax.

You have entered an incorrect ldev number. Ldev numbers are positive integers. (TDSM 20)

The value that you entered as a logical device number is not a number greater than zero.

Enter a valid ldev number. Note that you can also use the port subcommand.

The ldev number is missing or invalid. Ldev numbers are positive integers. (TDSM 21)

The logical device number was not entered or is unrecognizable.

Enter a valid ldev number. Note that you can also use the port subcommand.

You have entered an invalid SIC card number. SIC card numbers range from 0 to 5. (TDSM 22)

The card number that you entered in is not the range zero to five.

Doublecheck the card numbers by looking at the back of the DTC. Enter the card number again.

The SIC card number is missing or invalid. SIC card numbers range from 0 to 5. (TDSM 23)

The card number was not entered or is unrecognizable.

Enter the card number again. Refer to the prompt or to the reference documentation for syntax.

You have entered an incorrect DTC number. Please choose a DTC number from this list. (TDSM 24)

The value entered does not correspond with any DTC on the system.

The DTCs on the system are listed with their numbers. Enter one of the numbers displayed.

The DTC number is missing or invalid. Please choose a DTC number from this list. (TDSM 25)

The DTC number was not entered or is unrecognizable.

The DTCs on the system are listed with their numbers. Enter one of the numbers displayed.

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)

The dump files TRMdddAA through TRMdddZZ already exist. (The sequence ddd is the current Julian date.)

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.

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.

You do not have the correct user capabilities to use this function.

Log on with level 0, 1, or 2 security. Refer to the reference documentation for the security levels of each command and subcommand.

That ldev does not exist. Please check the ldev number, or dump the associated port instead. (TDSM 34)

Although you entered a number in a range that could be an ldev number, that ldev number is not configured on the system.

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).

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)?

More than one person is using TermDSM and directing operations to the same DTC at the same time.

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.

No ldevs seem to be configured on your system. (TDSM 356)

Necessary configuration information does not exist on the system.

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.

The dump process can't find out the length of the data area. (TDSM 37)

Internal error.

Contact your HP support representative.

The data area is longer than TermDSM's dump buffer. (TDSM 38)

Internal error.

Contact your HP support representative.

TermDSM never received a reply to its dump data area request. (TDSM 39)

Internal error.

Contact your HP support representative.

You must have high (1) security to perform this function. For level 1, you need SM or DI capability. (TDSM 42)

You do not have the correct user capabilities to use this function.

Logon as a user with the correct capabilities for the TermDSM functions you wish to use. Refer to the reference documentation for the security levels of each command and subcommand.

You can't do this from your own DTC. Please run TermDSM from another DTC or from the console. (TDSM 43)

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.

Move to a terminal on another DTC or the system console to run TermDSM.

Warning: This will reset all users on that DTC. As many as 48 terminal users could be affected. (TDSM 44)

If you continue, all user sessions on this DTC will be aborted.

If you want to continue, you should alert all the users that their sessions will be aborted.

Your answer must be at least 1 and no more than 65535. (TDSM 56)

The value entered is not in the range 1 to 65535.

Enter a value in the range. Diagnostic loop counts are limited to this range.

Use the CCTL option (:FILE LIST;DEV=LP;CCTL) when printing this file. (TDSM 62)

Informational message.

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.

The following two files make up the DTC dump. Please deliver both to your HP representative. (TDSM 64)

Informational message.

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.

There are no DTCs configured on your system. (TDSM 70)

Necessary configuration information does not exist on the system.

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.

There are more DTCs on your system than TermDSM can reference. Here are the ones TermDSM can reference. (TDSM 71)

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.

Contact your HP support representative.

You can't reset your own port or ldev. Please run TermDSM from a different port or ldev to do this. (TDSM 80)

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.

If you want to reset the port you are using, move to another port or the system console to run TermDSM.

That ldev is unknown (not configured). Please check the ldev number, or use reset port. (TDSM 81)

Although a number was entered in a range that could be an ldev number, that number is not configured on the system.

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).

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.

You do not have the correct user capabilities to do this function.

Logon as a user with the correct capabilities for the functions you wish to use. Refer to the reference documentation for the security level of each command and subcommand.

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.

You do not have the correct user capabilities to do this function.

Logon as a user with the correct capabilities for the TermDSM functions you wish to use. Use the appropriate reference materials to determine the security level of each command and subcommand.

TermDSM could not open the DTC manager, so the DTC dump could not be obtained. (TDSM 93)

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.

Contact your HP support representative (if it is an internal error).

You can't test your own port. Please run TermDSM from another port. (TDSM 110)

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.

If you want to test the port to which you are logged on, move to another port or the system console to run TermDSM.

Please put a loopback hood on the port, before answering the "How may times?" question. (TDSM 113)

The hardware must be present before the diagnostic is run.

Refer to the appropriate TermDSM manual for information on port loopback tests.

Please connect and make ready (power on, remote mode, etc.) a supported terminal, before answering the "How many times?" question. (TDSM 114)

The hardware must be present before the diagnostic is run.

Refer to the appropriate TermDSM manual for information on terminal loopback tests.

Please connect and make ready (power on, remote mode, etc.) a supported printer (or terminal), before answering the "How many times?" message. (TDSM 115)

The hardware must be present before the diagnostic is run.

Refer to the appropriate TermDSM manual for information on the port test.

Warning: The LDM dump is suspect. Consecutive dumps did not match. (TDSM 121)

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.

Submit the dump to your HP support representative.

You can't reset your own SIC. Please run TermDSM from another SIC or DTC, or from the console. (TDSM 122)

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.

Move to a port on a different DTC or SIC, or to the system console, to run TermDSM.

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)

The NMCONFIG.PUB.SYS file does not exist, or has no DTCs configured.

Check the NMCONFIG.PUB.SYS file for proper DTC and terminal configurations (using NMMGR), then shutdown and restart the system.

DTC and mainframe software versions are incompatible. (TDSM 200)

Incompatibilities were found between subsystem software on the HP 3000 and subsystem software on the DTC.

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.

Bad message length. (TDSM 201)

Internal error.

Contact your HP support representative.

Invalid operation. (TDSM 203)

Internal error.

Contact your HP support representative.

Request not supported. (TDSM 204)

Internal error.

Contact your HP support representative.

Sub request not supported. (TDSM 205)

Internal error.

Contact your HP support representative.

Entity not supported. (TDSM 206)

Internal error.

Contact your HP support representative.

No such entity. (TDSM 207)

Internal error.

Contact your HP support representative.

No parm for entity. (TDSM 208)

Internal error.

Contact your HP support representative.

The DTC reported an error or failure. (TDSM 213)

Internal error.

Contact your HP support representative.

End of Record received. Time = xx msec. (TDSM 218)

Probable hardware failure.

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.

Too many characters came back. Time = xx msec. (TDSM 219)

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.

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.

Parity error. Time = xx msec. (TDSM 220)

Probable hardware failure.

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.

Hardware receive overrun. Time = xx msec. (TDSM 221)

Probable hardware failure.

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.

Framing error. Time = xx msec. (TDSM 222)

Probable hardware failure.

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.

SIC Buffer overflow. Time = xx msec. (TDSM 223)

Internal error.

Contact you HP support representative.

No record separator in Vplus. Time = xx msec. (TDSM 226)

Probable hardware failure.

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.

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)

No or too few characters came back from the loopback.

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.

Alternate end-of-record received. Time = xx msec. (TDSM 230)

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.

Subsystem break. Time = xx msec. (TDSM 231)

Probable hardware failure.

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.

No modem was connected during the operation. Time = xx msec. (TDSM 232)

During the test, the modem on that port was disconnected.

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.

Console attention. Time = xx msec. (TDSM 234)

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.

Operation aborted. (TDSM 235)

The operation was aborted by the DTC. Possibly, the download file is invalid.

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.

End of dump file encountered. (TDSM 236)

The end of the DTC upload (dump) file was encountered when there was still more information to write.

Verify that there is sufficient disc space (approx. 2200 sectors are required). Otherwise, contact your HP support representative.

Security invalid. (TDSM 238)

Internal error.

Contact your HP support representative.

Bad packet. (TDSM 239)

Internal error.

Contact your HP support representative.

During a DTC reset/dump request from the mainframe. (TDSM 240)

Informational message which can be printed after an error message. It describes in which phase of an operation the error occurred.

Refer to the cause and action descriptions for the actual error message preceding message 240.

During the DTC download operation. (TDSM 241)

Informational message which may be printed after an error message. It describes in which phase of an operation the error occurred.

Refer to the cause and action descriptions for the actual error message preceding message 241.

During a DTC upload (dump) operation. (TDSM 242)

Informational message which may be printed after an error message. It describes in which phase of an operation the error occurred.

Refer to the cause and action descriptions for the actual error message preceding message 242.

Bad parameter from TermDSM. (TDSM 243)

Internal error.

Contact your HP support representative.

Timeout waiting for the DTC to respond. The DTC may be powered off, malfunctioning, or misconfigured. (TDSM 244)

The TermDSM command resulted in an instruction being sent to a DTC, and the DTC did not respond.

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.

Write to IEEE 802.3 DAM failed. (TDSM 245)

Internal error.

Contact your HP support representative.

Bad Network Management packet received from DTC. (TDSM 247)

Internal error.

Contact your HP support representative.

The DTC requested to be downloaded during the operation. (TDSM 248)

The DTC was trying to power up at the same time you were trying to access it.

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.

The DTC requested that it be dumped during the operation. (TDSM 249)

The DTC detected an internal error at the same time you were trying to access it through TermDSM.

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.

DTC and mainframe software versions are incompatible. (TDSM 250)

Incompatibilities were found between subsystem software on the HP 3000 and subsystem software on the DTC.

Contact your HP support representative.

Bad RMP packet received from DTC. (TDSM 251)

Internal error.

Contact your HP support representative.

Could not open the download or dump file. (TDSM 252)

Files pertaining to this operation cannot be accessed.

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.

Unable to get a system timer. (TDSM 253)

Internal error.

Contact your HP support representative.

Software bug encountered. (TDSM 254)

Internal error.

Contact your HP support representative.

Dump overflow: DTC sent more data than expected. (TDSM 255)

Internal error.

Contact your HP support representative.

MPE/XL create object failed. (TDSM 256)

Internal error.

Contact your HP support representative.

Unknown internal error. (TDSM 257)

Internal error.

Contact your HP support representative.

Application request timeout occurred. (TDSM 258)

Internal error. This means two users of TermDSM were directing TermDSM commands to the same DTC at the same time, and the other TermDSM user answered "yes" to the override question (see TermDSM message 35). Other error messages are likely to be printed also, because your operations were interrupted. These error messages should be ignored. There is nothing wrong with multiple users of TermDSM running at the same time, as long as they do not try to direct commands to the same DTC at the same time. The message and interlock system of TermDSM message 35 was designed to prevent this conflict.''

Contact your HP support representative.

DTC not opened by this TermDSM. Possibly your TermDSM was overridden by another TermDSM. (TDSM 259)

Another user of TermDSM has explicitly overridden your use of TermDSM.

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.

Bad NMP error code received. (TDSM 260)

Unknown error reported by the Distributed Terminal Subsystem to TermDSM.

Contact your HP support representative.

Bad RMP error code received. (TDSM 261)

Unknown error reported by the Distributed Terminal Subsystem to TermDSM.

Contact your HP support representative.

The DTC subsystem has reported that an error was detected. (TDSM 262)

This is the standard message that precedes specific error messages.

Follow the instructions for the error message that follows this message.

An error of unknown type was reported by the DTS subsystem. (TDSM 263)

An error unknown to TermDSM was reported by the Distributed Terminal Subsystem.

Contact your HP support representative.

The DTC reported an unknown status as a result of the loopback. Time taken=xx. (TDSM 264)

An error unknown to TermDSM was reported by the Distributed Terminal Subsystem.

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.

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)

The DTC has reported that the port in question is bad or does not exist.

Note the range of ports in the error message. If you are specified a port that does not exist, verify the information to determine the correct port. For reset and dump, you can specify an ldev number instead of the port to do the operation. If the port does exist, a hardware failure has probably occurred. Contact your HP support representative. You can obtain additional information by running the card selftest (through the SIC subcommand of the TermDSM RESET command), the DTC selftest, and the DTC offline diagnostics.

That SIC is malfunctioning, or not installed. TermDSM can not always tell the difference between !!not installed!! and a serious malfunction. (TDSM 271)

Possible hardware problem or no card is installed in that slot.

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.

The operation was aborted because it was reset. (TDSM 272)

Another TermDSM user reset the operation while in progress.

See message 246 for a discussion of multiple TermDSM operations directed against the same DTC.

The modem on that port disconnected. (TDSM 273)

The modem on that port was disconnected during the operation.

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.

The DTC reported that an unexpected event occurred. (TDSM 274)

A user on that terminal might have entered CTRL Y or pressed Break.

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.

The loopback is too long. (TDSM 275)

Internal error.

Contact your HP support representative.

Dump failed. Open of DTCM failed, or DTC owned and not overridden (TDSM 280)

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.

If the problem persists, take another dump. If you are sure another user was not involved, contact your HP support representative.

Dump failed: Send or Receive of dump request failed. (TDSM 281)

An internal error. This message is written to dump files and never appears as an error message to a user.

Contact your HP support representative.

Dump failed: Bad function in internal error reply to dump request.(TDSM 282)

An internal error. This message is written to dump files and never appears as an error message to a user.

Contact your HP support representative.

Dump failed. Bad reply (llio) status from DTCM. (TDSM 283)

Internal error.

Contact your HP support representative.

Sorry, TermDSM does not provide services for the console. (TDSM 290)

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.

Contact your HP support representative.

IPC message received in wrong subque. (TDSM 300)

Internal error.

Contact your HP support representative.

DTCM port data area not initialized. (TDSM 301)

Internal error.

Contact your HP support representative.

Bad machine type found in RMP packet. (TDSM 302)

Internal error.

Contact your HP support representative.

Non supported download file type found in RMP packet. (TDSM 303)

Internal error.

Contact your HP support representative.

Bad source IEEE 802.3 address found in RMP packet. (TDSM 304)

Internal error.

Contact your HP support representative.

Bad session ID found in RMP packet. (TDSM 305)

Internal error.

Contact your HP support representative.

Bad path id received from NDM. (TDSM 306)

Internal error.

Contact your HP support representative.

Boot (download) complete message received before expected. (TDSM 307)

It has finished the download of its operating firmware before the DTCM expected it.

Look on the console for a boot complete message. Otherwise, enter the command again. If the problem persists, contact your HP support representative.

IO-get-frame failed. (TDSM 308)

Internal error.

Contact your HP support representative.

Unimplemented action called. (TDSM 309)

Internal error.

Contact your HP support representative.

Bad download file type. (TDSM 310)

Possible corrupt download file.

Contact your HP support representative.

Bad reply from memory manager for Aux data area. (TDSM 311)

Internal error.

Contact your HP support representative.

DCC sent bad reply in response to config. data request. (TDSM 312)

Internal error.

Contact your HP support representative.

DTC did not request the configuration to be download. (TDSM 313)

After a download, the DTC did not request its configuration.

Look at the console for a message saying configuration complete. Otherwise, enter the command again. If the problem persists, contact your HP support representative.

DCC did not reply to configuration data request. (TDSM 314)

Internal error.

Contact your HP support representative.

Unexpected RMP packet received. (TDSM 315)

Internal error.

Contact your HP support representative.

DTC unexpectedly requested configuration information to be downloaded. (TDSM 316)

Internal error. The DTC requested its configuration information at a time the DTCM did not expect it.

Monitor the console for messages saying the configuration is complete. Otherwise, enter the command again. If the problem persists, contact your HP support representative.

Contact your HP support representative.