On Alpha and Integrity servers, adds an entry to the System Dump
Priority registry file.
The registry data file is the permanent database that survives
reboots. It is loaded into memory during a boot. (You can use the
DUMP_PRIORITY LOAD command at any time to load the contents of
this file into memory.)
When you add an entry to the registry file, you must specify
both the process name and UIC. If you attempt to add an entry
that already exists, the system displays the following message:
"SMI-I-SDPDUPIGN, duplicate record creation ignored."
How Dump Priority Works
BUGCHECK uses the loaded contents of the System Dump Priority
registry to select priority processes to dump early on during a
selective dump. Adding a dump priority for a process increases
the likelihood that the process will be included in a dump, if
there is insufficient space for all processes. (The ADD command
only adds an entry to the System Dump Priority registry permanent
file. For BUGCHECK to be able to see the entry, you must also
enter a DUMP_PRIORITY LOAD command.)
BUGCHECK also keeps its own in-memory hardcoded list of priority
processes, which are always treated as priority processes, even
if the System Dump Priority registry is empty. These processes
are the following:
Process Name UIC
MSCPmount [1,4]
AUDIT_SERVER [1,4]
NETACP [1,4]
NET$ACP [1,3]
REMACP [1,3]
LES$ACP [1,4]
Note that you cannot see, change, or delete these default
processes with DUMP_PRIORITY commands.
If you enter a process into the System Dump Priority registry,
that process is dumped earlier, because user-specified priority
processes are dumped before processes that are hardcoded into
BUGCHECK.
Keep in mind that BUGCHECK keeps track of the processes that have
been dumped, so that no process is dumped twice.
Format
DUMP_PRIORITY ADD process-name /UIC=uic [/WILD_CARD]
Additional Information:
explode
extract