Network Dump Manager Error Messages

**** DUMP ERROR 1: PATH ALREADY DELETED FROM SYSTEM

The Network Dump Manager attempted to look up information about the SDLC link driver being dumped, but was unable to locate all of the information. This is probably because the driver had already been shut down. A heavy system load or a hung system console can delay the Dump Manager long enough to cause it to time out and shut down. Note that no dump file was produced.

If the problem continues and you need a good dump file, try reducing the system load.

**** DUMP ERROR 2: LACK OF MEMORY PREVENTS DUMPS

This message appears only during system boot. At boot time, the Network Dump Manager could not obtain a block of system memory, which is required to produce SDLC link hardware dumps. If the system comes up, the Network Dump Manager will not work, attempts to produce link dumps will be ignored, and no more Network Dump Manager errors will appear.

Take a system memory dump if the system comes up, and then call your Hewlett-Packard support contact. If the system seems to operate normally (except for this condition), continue to use the link until this condition is resolved.

**** DUMP ERROR 3: CANNOT ACCESS INTERRUPT SYSTEM

The Network Dump Manager located information about the SDLC link hardware, but received an error when attempting to obtain an interrupt list head from the I/O system. Note that no dump file was produced.

Issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, take a system memory dump and call your Hewlett-Packard support contact, who will need to analyze the "Llio Status" error that was logged.

**** DUMP ERROR 4: CANNOT CREATE DUMP FILE

The Network Dump Manager completed all hardware-dump setup, but was not able to open a new disk file to hold the dump. Either 100 dumps are already on the system, or another problem (for example, a lask of disk space or directory space) exists. Note that no new dump file was produced.

Issue the MPE LISTF command to find all NETDMPnn.PUB.SYS files, and then purge any of those files that are unnecessary. Also, check disk space usage. You can try to create a file in PUB.SYS yourself (by issuing the MPE BUILD command) to test for any errors. If the problem continues, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "Hpe Status" error that was logged.

**** DUMP ERROR 5: CANNOT FREEZE MEMORY

The Network Dump Manager received an error from the system while trying to freeze a part of the dump file into memory. If the system is heavily loaded, too much memory might be in use. Otherwise, a system problem might exist. Note that a partial dump file was produced.

If the problem continues, try reducing the system load. If that does not solve the problem, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, take a system memory dump and call your Hewlett-Packard support contact, who will need to analyze the "Hpe Status" error that was logged. Also, your Hewlett-Packard support contact might be able to analyze the partial dump file that was created, depending on how much of the file the Network Dump Manager was able to freeze before the error occurred.

**** DUMP ERROR 6: CANNOT DUMP DRIVER MEMORY

The Network Dump Manager received an error while trying to send a message through the system by using the SDLC link driver's port, requesting a driver memory dump. The driver might have already been shut down or an operating system problem might exist. Note that an empty dump file was produced.

Purge the empty dump file that was produced. Then, check for other SDLC link driver error messages that were generated (see "SDLC Link Driver Error Messages" earlier in this appendix). You should especially check for link driver error message number 1033. If that message was generated, it might indicate that the dump took too long to produce. (This caused the driver to be shut down, deleting its memory.) A heavy system load can cause the dump to take too long. If no other messages were generated, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "Hpe Status" error that was logged.

**** DUMP ERROR 7: UNEXPECTED INTERRUPT RECEIVED

The Network Dump Manager received an interrupt message from the I/O system, containing an address that did not point to a valid DMA completion entry in the Dump Manager's memory area. The SDLC link hardware or I/O bus hardware might be too faulty to produce a good dump. Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but corrupt hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably intermittently faulty. If the system crashes, take a system memory dump. Also, because the link hardware might have also corrupted other system memory, you should restart the system. Then, call your Hewlett-Packard support contact, who will need to replace the PSI card in the system.

**** DUMP ERROR 8: SOFT CARD ERROR DURING DUMP

Only the soft error "SERR_MORE" was expected, but the SDLC link hardware reported some other soft error. The link hardware or I/O bus hardware might be too faulty to produce a good dump. Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but corrupt hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 9: HARD CARD ERROR DURING DUMP

No hard errors are expected during a dump, but the SDLC link hardware reported one. The link hardware or I/O bus hardware is too faulty to produce a good dump. Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 10: INCOMPLETE CARD DMA TRANSFER

The Network Dump Manager requested an exact read of the SDLC link hardware memory, but the hardware reported a residual count, which indicates that some of the data was not transferred. The link hardware or I/O bus hardware might be too faulty to produce a good dump. Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Then, call your Hewlett-Packard support contact, who will need to replace the PSI card in the system.

**** DUMP ERROR 11: CARD NOT READY DURING DUMP

While linking the next memory transfer, the Network Dump Manager discovered that the SDLC link hardware did not set its "ready bit." A soft error or hard error, describing the reason, was probably also set at that time. The link hardware or I/O bus hardware might be too faulty to produce a good dump. Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 12: FATAL CARD ERROR DURING DUMP

While linking the next memory transfer, the Network Dump Manager discovered that the SDLC link hardware died with a "fatal error" while the dump was in progress. The link hardware or I/O bus hardware might be too faulty to produce a good dump, or a power failure might have occurred. (A power failure can produce a false fatal error, but it still aborts the dump.) Note that a partial dump file was produced.

The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file unless a power failure occurred. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 13: CANNOT GET DUMP TIMER

The Network Dump Manager received an error from the system while attempting to obtain a watchdog timer for its side of the dump operation. The system might be under a heavy load and using all of the timers, or an operating system problem might exist. Note that no dump file was produced.

If the system is heavily loaded, try reducing the load by aborting some jobs or sessions. If the problem continues, take a system memory dump. Also, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "Llio Status" error that was logged.

**** DUMP ERROR 14: NOT-READY CARD PREVENTS DUMP

After dumping SDLC link driver data, the Network Dump Manager checked the SDLC link hardware and found it "not ready." A hard error was probably also set. The link hardware cannot be dumped, and it might be faulty. Note that a partial dump file was produced.

The partial dump file that was produced contains only link driver data. Your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 15: FATAL CARD ERROR PREVENTS DUMP

After dumping SDLC link driver data, the Network Dump Manager checked the SDLC link hardware and found a "fatal error." The link hardware cannot be dumped and might be faulty, or a power failure might have occurred. (A power failure can produce a false fatal error, but it still aborts the dump.) Note that a partial dump file was produced.

The partial dump file that was produced contains only link driver data. So, your Hewlett-Packard support contact might be able to analyze the file unless a power failure occurred. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "IO Status" error that was logged and replace the PSI card in the system.

**** DUMP ERROR 18: TIMEOUT CAUSED INCOMPLETE DUMP

The Network Dump Manager timed out while waiting for the system to dump the SDLC link driver context or while waiting for SDLC link hardware memory DMA. The Dump Manager can be delayed too long by a heavy system load or a hung system console. The SDLC link driver has a similar timer running to delay shutdowns while dumping is in progress. Note that an empty or corrupt dump file might have been produced.

If a dump file was created, your Hewlett-Packard support contact might be able to analyze it, depending on how much processing the Network Dump Manager was able to do before the error occurred. If the problem continues and you need a good dump file, try reducing the system load.

**** DUMP ERROR 19: DRIVER MEMORY DUMP FAILED

In response to the Network Dump Manager's request to the system to dump the SDLC link driver's context-area memory, the system sent a reply message that contains an error. The driver might have already been shut down or an operating system problem might exist. Note that an empty dump file was produced.

Purge the empty dump file that was produced. Then, check for other SDLC link driver error messages that were generated (see "SDLC Link Driver Error Messages" earlier in this appendix). You should especially check for link driver error message number 1033. If that message was generated, it might indicate that the dump took too long to produce. (This caused the driver to be shut down, deleting its memory.) A heavy system load can cause the dump to take too long. If no other messages were generated, issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the "Llio Status" error that was logged.

**** DUMP ERROR $nnnn

The Network Dump Manager detected an error, but because of a software bug no message text was supplied or the Dump Manager incorrectly reported an illegal error number. The error number is displayed as a hexadecimal value (nnnn). Note that an empty or corrupt dump file might have been produced.

If a dump file was created, your Hewlett-Packard support contact might be able to analyze it. Note what you were doing when the error occurred, and write down all console messages that were displayed at the time this message was displayed. Issue the SWITCHNMLOG command (see chapter 6 of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact and submit an SR.