DUMPANALYZER displays the following error messages if an abnormal condition occurs.
ACCEPT: AX OK TO USE <file title> OR AX RESTART TO SPECIFY NEW TITLE
The code file timestamp on disk did not match the timestamp on the dump tape. Enter OK to use the code file on disk, or RESTART to cause the code file to be closed and DUMPANALYZER to be suspended. DUMPANALYZER proceeds if OK is specified.
DISPLAY: DUMP TAPE HAS BAD INFORMATION IN RECORD <#>, AT LOCATION <#>.
Data on the dump tape failed the consistency check, causing DUMPANALYZER to terminate.
DISPLAY: BAD DATA RECOVERY IN RECORD <#>, AT LOCATION <#>.
Data on the dump tape failed the consistency check, but redundancies in the way that these data were stored on the tape allowed limited recovery of that data. DUMPANALYZER then proceeds.
DISPLAY: BAD DUMPANALYZER INPUT CARDS
DUMPANALYZER was unable to decipher an input card. The card image appears on the printout with a line of asterisks (*) pointing to the unknown word, and processing terminates.
DISPLAY: BAD MCP STACK POINTER
DUMPANALYZER found that the stack vector descriptor at D[0]+2 did not address present memory. This condition is usually caused when an end-of-file condition occurs prematurely on the dump tape, or when the last memory module is taken offline and no MEMDUMP disk is available, which causes termination of processing. Rerun DUMPANALYZER with RAWDUMP and DEBUG set; DUMPANALYZER then produces a raw dump of the contents of the tape without checking D[0]+2.
DUMPANALYZER FAULT <#> messages are given for the first, second, third, fourth, and tenth faults and for every tenth fault thereafter (20, 30, 40, and so forth).
DISPLAY: CANNOT ANALYZE - MCP INCOMPATIBLE WITH DUMPANALYZER.
The MCP level recorded on the dump tape did not match the level of DUMPANALYZER. You can avoid this incompatibility by ensuring that the level of DUMPANALYZER is always exactly the same as the level of the MCP that wrote the dump tape.
DISPLAY: CANNOT ANALYZE -USE PREVIOUS DUMP ANALYZER
The level of the MCP as recorded on the dump tape was lower than the level compiled into DUMPANALYZER, causing DUMPANALYZER to terminate. Use the proper level of DUMPANALYZER for a rerun.
DISPLAY: ERROR UNABLE TO GENERATE GLOBAL IDENTIFIERS, CAUSE = <cause>.
One of four causes caused failure in the MCP global identifier routine. Two of these causes indicate either improper compilation, a DUMPANALYZER bug, or code file corruption (LEVEL and SIZE). I/O exceptions give rise to the other two causes, RDMCP (code file) and RDFILE (internal file). Global name generation is terminated, NONAMES is invoked, and DUMPANALYZER analysis proceeds. You can rerun DUMPANALYZER with the DEBUG command to get a program dump of the terminated global identifier routine.
DISPLAY: SAVE ABORTED—FILE IN USE BY ANOTHER PROGRAM
The SAVE command was terminated because exclusive access could not be gained to the DP file used for saving the dump. Either terminate the other program(s) accessing the file, or create the SAVE dump on a family other than the family where the DP file currently resides.
DISPLAY: SAVE ABORTED FOR INSUFFICIENT DISK SPACE
The SAVE command was terminated because not enough disk space was available to hold the saved dump file.
DISPLAY: SAVE ABORTED FOR DIRECT I/O ERROR, RD=<result descriptor>
The SAVE command was terminated because of a disk unit read or write error. The result descriptor gives information about the error.
