Checking for the Occurrence of a Dump

Because AutoRestart/iX guarantees automatic startup and dump-to-disk after a system software failure, you might not notice that a dump has occurred on your system. It is important that you establish procedures requiring regular checks for dump information in your dump files.

	NOTE: You should check your system daily for evidence of a system abort and dump.

One way that you can check your system is to execute BLDDUMP and use the LIST command to list dump file information. Execute BLDDUMP either interactively or from a regularly scheduled job. Examine the output for evidence of a dump file that contains dump information from a system abort. In the following example, BLDDUMP shows that the dump file DUMP1 has 330 megabytes of new dump information that resulted from a system abort that occurred since the last time that you checked.

:RUN BLDDUMP.HP36375.TELESUP

(#7) blddump > LIST



Autoboot Status                                      YES

Dump to tape if dump-to-disk is not successful?      NO



DUMP FILE NAME      DUMP FILE       CURRENT SIZE    PROTECTED?

 (ID + "MEM")       MAXIMUM SIZE    OF CONTENTS

                    (megabytes)     (megabytes)

--------------      ------------    -------------   ----------

DUMP1MEM              417                330           YES

Another way to check for a system abort and dump is to enable system console logging and to regularly examine system console log files for evidence of a system abort. Refer to System Startup, Configuration, and Shutdown Reference Manual (32650-90042) for details on enabling and examining system console logging.