how_to_capture_a_vms_crash_dump
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
how_to_capture_a_vms_crash_dump [2018/09/07 19:04] – created lricker | how_to_capture_a_vms_crash_dump [2018/09/07 19:47] – lricker | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== HOW TO CAPTURE A CRASH DUMP ===== | ===== HOW TO CAPTURE A CRASH DUMP ===== | ||
- | Sometimes a VMS problem manifests itself as a system crash. | + | Sometimes a VMS problem manifests itself as a system crash. |
- | crash is not an accident or a mistake -- it is an intentional response by | + | Team) -- to protect data on disk from any corruption, for example, due to a severe programming error or hardware fault. |
- | the operating system | + | |
- | Team -- to protect data on disk from any corruption | + | |
- | programming error or hardware fault). | + | |
- | A VMS system crash always stops/ | + | A VMS system crash always stops/ |
- | the complete contents of physical memory (or as much of it as possible) into | + | |
- | the "crash dump file" (usually SYS$SYSTEM: | + | |
- | system, either stopping at the system console' | + | |
- | manual action to power-down, repair and/or reboot), or rebooting the system | + | |
- | as configured by the console' | + | |
- | After the next reboot, the contents of the crash dump file SYSDUMP.DMP will | + | After the next reboot, the contents of the crash dump file SYSDUMP.DMP will either "just sit there," |
- | either "just sit there," | + | startup command files are properly configured -- those contents will be copied into another, secondary or alternate crash dump file (this preserves each crash-instance in the case of a cascading series of crashes only minutes apart). |
- | (which could be minutes, or years, in the future), or -- if the system' | + | |
- | startup command files are properly configured -- those contents will be | + | |
- | copied into another, secondary or alternate crash dump file (this preserves | + | |
- | each crash-instance in the case of a cascading series of crashes only minutes | + | |
- | apart). | + | |
- | As a VMS sys-admin, you should know precisely how your VMS system(s) are | + | As a VMS sys-admin, you should know precisely how your VMS system(s) are configured to handle your SYSDUMP.DMP file upon reboot after a crash. |
- | configured to handle your SYSDUMP.DMP file upon reboot after a crash. | + | |
- | PARSEC can assist you with information on determining your systems' | + | |
- | both in this wiki and/or with an MEP white-paper (available through your | + | |
- | PARSEC Account Representative). | + | |
how_to_capture_a_vms_crash_dump.txt · Last modified: 2018/09/10 21:40 by lricker