(Kept debugger only.) Opens a process dump for analysis with
the System Code Debugger (SCD). The qualifier /PROCESS_DUMP is
required and distinguishes this command from the one that invokes
the System Dump Debugger (SDD), ANALYZE/CRASH_DUMP.
The qualifier /IMAGE_PATH=directory-spec is optional, and
specifies the search path the debugger is to use to find the
debugger symbol table (DST) files. The debugger builds an image
list from the saved process image list. When you set an image
(the main image is automatically set), the debugger attempts to
open that image in order to find the DSTs.
If you include the /IMAGE_PATH=directory-spec qualifier, the
debugger searches for the .DST file in the specified directory.
The debugger first tries to translate directory-spec as the
logical name of a directory search list. If that fails, the
debugger interprets directory-spec as a directory specification,
and searches that directory for matching .DSF or .EXE files. A
.DSF file takes precedence over an .EXE file. The name of the
.DSF or .EXE file must match the image name.
If you do not include the /IMAGE_PATH=directory-spec qualifier,
the debugger looks for the DST file first in the directory
that contains the dump file. If that fails, the debugger next
searches directory SYS$SHARE and then directory SYS$MESSAGE. If
the debugger fails to find a DST file for the image, symbolic
information available to the debugger is limited to global and
universal symbol names.
The debugger checks for link date-time mismatches between the
dump file image and the DST file and issues a warning if one is
discovered.
The parameter dumpfile is the name of the process dump file to be
analyzed. Note that the process dump file type must be .DMP and
the DST file type must be either .DSF or .EXE.
For more information about using SCD, see the HP OpenVMS System
Analysis Tools Manual.
Related commands:
ANALYZE/CRASH_DUMP
CONNECT %NODE
SDA