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]

1  –  Parameter

 process-name

    The exact name of the process. If the process name is mixed-case
    or includes spaces or any other nonstandard OpenVMS characters,
    you must enclose it in double quotes; for example, "My Process".

    You can use wildcard characters (* and %). Because these
    characters are valid characters in any process name, you must
    include the wildcard flag /WILD_CARD. Setting the /WILD_CARD flag
    for a specific process entry tells BUGCHECK to treat the asterisk
    (*) and percent-sign (%) as wild cards.

2  –  Qualifiers

2.1    /INFORMATIONAL

       /INFORMATIONAL (default)
       /NOINFORMATIONAL

    On Alpha and Integrity servers, allows you to control the output
    of informational messages, for example, in command procedures.
    These qualifiers allow you to suppress or reinstate the display
    of informational messages.

    Suppressing messages can also be useful when you are running in a
    software installation environment and want to avoid the display
    of informational messages. The default is /INFORMATIONAL.

2.2    /UIC

    Specifies the UIC of the entry to add. You must enclose the UIC
    in brackets ([ ]). You can specify the /UIC with an octal number
    (for example, [377,377]) or in the identifier form (for example,
    [SYSTEM] or [VMS,USER]).

    Wildcards are allowed as follows:

    Wildcard
    Example        Description

    /UIC = [*]     To select processes with the specified name in any
                   UIC.
    /UIC =         To select processes with the specified name in the
    [group,*]      group called "group".
    /UIC =         To select processes with the specified name in
    [100,*]        group 100>.

                                   NOTE

       You cannot use wildcards within identifier names or within
       UIC numbers. For example, /UIC=[USER*,*] or /UIC=[17*,100]
       are not allowed.

2.3    /WILD_CARD

       /WILD_CARD
       /NOWILD_CARD

    Specifies whether or not wildcard characters in the process name
    are to be treated as wildcards. Note, however, that you cannot
    add the same process name and UIC combination both with and
    without the /WILD_CARD qualifier. If the combination has already
    been specified, use the DUMP_PRIORITY MODIFY command to change
    the wildcard setting.

    The /WILD_CARD setting affects only the process name. Wildcards
    are always allowed in the UIC.

3  –  Example

  SYSMAN>  DUMP_PRIORITY ADD "MyPro*"/UIC=[*]/WILD_CARD
  SYSMAN> DUMP_PRIORITY LIST
  %SYSMAN-I-OUTPUT, command execution on node VMS73

  Process name    UIC                                 Wild Card
  MyPro*          [*]                                 Y

      The first command in this example adds an entry to the System
      Dump Priority registry. The process name is "MyPro*" with any
      UIC, and BUGCHECK will treat the asterisk (*) in MyPro* as a
      wildcard when the registry is loaded into memory.

      BUGCHECK treats the UIC wildcard asterisk (*) as a wildcard,
      even if you do not specify the /WILD_CARD qualifier on the
      command line.

      The Y under the Wild Card heading means that the /WILD_CARD
      qualifier has been specified on the command line and a wildcard
      has been specified in the process name.