1 DUMP_PRIORITY Several DUMP_PRIORITY subcommands exist on Alpha and Integrity servers. Select the one you want from the choices below. The ADD command contains a description of the System Dump Priority registry data file, whose contents DUMP_PRIORITY commands affect. 2 ADD 3 and 4 Integrity 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] 5 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. 5 Qualifiers /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. /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. /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. 5 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. 2 LIST 3 and 4 Integrity On Alpha and Integrity servers, lists the contents of the System Dump Priority registry file. Format DUMP_PRIORITY LIST 5 Example SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCPmount [SYSTEM] N NETACP [SYSTEM] N NET$ACP [1,3] N REMACP [1,3] N LES$ACP [SYSTEM] N SYSMAN> The command in this example produces a list of the contents of the System Dump Priority registry, including the process name and UIC of each entry. The list also shows N under the Wild Card heading, which indicates that BUGCHECK is to match the process name exactly during a crash. (However, N or Y under Wild Card is important only if the the process name contains one or more wildcard characters.) 2 LOAD 3 and 4 Integrity On Alpha and Integrity servers, loads the contents of the System Dump Priority registry file into memory for BUGCHECK to use. Format DUMP_PRIORITY LOAD 5 Example SYSMAN> DUMP_PRIORITY SHOW %SMI-F-SDPNOTLOAD, System Dump Priority not loaded SYSMAN> DUMP_PRIORITY LOAD SYSMAN> DUMP_PRIORITY SHOW %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCPmount [SYSTEM] N NETACP [SYSTEM] N NET$ACP [00001,000003] N REMACP [00001,000003] N LES$ACP [SYSTEM] N SYSMAN> The first command in the example displays the message that the System Dump Priority registry file has not been loaded into memory. The second command loads the registry file into memory for BUGCHECK to use, and the third command displays the contents of the registry file that have been loaded into memory. 2 MODIFY 3 and 4 Integrity On Alpha and Integrity servers, modifies an entry in the System Dump Priority registry file. Format DUMP_PRIORITY MODIFY process-name /UIC=uic [/NEWUIC=newuic][/WILD_CARD] 5 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 the process name in double quotes; for example, "My Process". Also, when you enter a DUMP_PRIORITY MODIFY command, be sure to enter the process name exactly as it is displayed when you enter a DUMP_PRIORITY LIST command, because the system searches for that process name to find the entry to modify. If you attempt to modify an existing entry where the modification can result in a duplicate, the system displays the following message: "SMI-I-SDPDUPIGN, duplicate record creation ignored." The existing record is not removed. 5 Qualifiers /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. /UIC Specifies the UIC of the entry in the registry that you want to modify. The UIC and process name together make the entry unique. Specify the UIC as it is displayed when you enter the DUMP_PRIORITY LIST command. /NEWUIC Modifies the UIC of an entry that you specify by its process name and current UIC. You can specify the /NEWUIC 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. /WILD_CARD /WILD_CARD /NOWILD_CARD The /WILD_CARD qualifier, used together with the MODIFY command, modifies the wildcard setting on the entry that you are modifying. If you omit /WILD_CARD, the current wildcard setting is retained. 5 Example SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCP* [SYSTEM] Y NETACP [SYSTEM] N SYSMAN> DUMP_ PRIORITY MODIFY "MSCP*"/UIC=[SYSTEM]/NEWUIC=[TEST]/NOWILD_CARD 1 SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCP* [TEST] N NETACP [SYSTEM] N SYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[TEST]/NEWUIC=[*] 2 SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCP* [*] N NETACP [SYSTEM] N SYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[*]/WILD_CARD 3 %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCP* [*] Y NETACP [SYSTEM] N Refer to the numbers at the end of the DUMP_PRIORITY MODIFY command lines in the example, which correspond to the numbered explanations that follow. (The DUMP_PRIORITY LIST command, after each MODIFY command, displays the results of the modifications in the System Dump Priority registry.) 1 The first DUMP_PRIORITY MODIFY command modifies the MSCP* entry with the current UIC [SYSTEM] the new UIC [TEST]. It also changes the /WILD_CARD flag to /NOWILD_CARD. If the System Dump Priority registry is then loaded into memory, BUGCHECK will not treat the asterisk (*) in the process name as a wildcard, but rather, will do an exact character match of MSCP*. 2 The second DUMP_PRIORITY MODIFY command modifies only the UIC of the entry to [*]. Omitting the /[NO]WILD_CARD qualifier will leave the current setting unchanged. 3 The third DUMP_PRIORITY MODIFY command modifies only the process name wildcarding flag with the /WILD_CARD qualifier. 2 REMOVE 3 Integrity On Alpha and Integrity servers, removes a record from the System Dump Priority registry file. Format DUMP_PRIORITY REMOVE process-name /UIC=uic 4 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 the process name in double quotes; for example, "My Process". Also, when you enter a DUMP_PRIORITY REMOVE command, be sure to enter the process name exactly as it is displayed when you enter a DUMP_PRIORITY LIST command, because the system searches for that process name to find the entry to remove. If you attempt to remove a nonexistent entry from the System Dump Priority registry, the system displays the following message: "SMI-I- SDPRNOTREM, no record removed." When the system cannot find the entry to modify, it displays the following message: "SMI_ F_SDPRNOTFOUND, system dump priority record not found." 4 Qualifier /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. /UIC Specifies the UIC of the entry in the registry that you want to remove. The UIC and process name together make the entry unique. Specify the UIC as it is displayed when you enter the DUMP_PRIORITY LIST command. 4 Example SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCPmount [SYSTEM] N NETACP [SYSTEM] N NET$ACP [1,3] N REMACP [1,3] N LES$ACP [SYSTEM] N SYSMAN> DUMP_PRIORITY REMOVE "MSCPmount"/UIC=[SYSTEM] SYSMAN> DUMP_PRIORITY LIST %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card NETACP [SYSTEM] N NET$ACP [1,3] N REMACP [1,3] N LES$ACP [SYSTEM] N The DUMP_PRIORITY REMOVE command in this example removes the entry MSCPmount with the UIC of [SYSTEM] from the System Dump Priority registry file. (The process name MSCPmount is enclosed in quotes because it is mixed-case.) 2 SHOW 3 and 4 Integrity On Alpha and Integrity servers, lists the contents of the in- memory copy of the System Dump Priority registry file. Format DUMP_PRIORITY SHOW 5 Example SYSMAN> DUMP_PRIORITY SHOW %SMI-F-SDPNOTLOAD, System Dump Priority not loaded SYSMAN> DUMP_PRIORITY LOAD SYSMAN> DUMP_PRIORITY SHOW %SYSMAN-I-OUTPUT, command execution on node VMS73 Process name UIC Wild Card MSCPmount [SYSTEM] N NETACP [SYSTEM] N NET$ACP [00001,000003] N REMACP [00001,000003] N LES$ACP [SYSTEM] N SYSMAN> The first DUMP_PRIORITY SHOW command in the example results in the display indicating that the System Dump Priority registry file has not been loaded into memory. The second DUMP_PRIORITY SHOW command, which follows a LOAD command, displays an in- memory copy of the file. 2 UNLOAD 3 and 4 Integrity On Alpha and Integrity servers, clears the in-memory copy of the System Dump Priority registry file. Format DUMP_PRIORITY UNLOAD 5 Example SYSMAN> DUMP_PRIORITY UNLOAD SYSMAN> DUMP_PRIORITY SHOW %SMI-F-SDPNOTLOAD, System Dump Priority not loaded Following a DUMP_PRIORITY UNLOAD command, the DUMP_PRIORITY SHOW command in this example displays the message that the System Dump Priority registry no longer has an in-memory copy of the file.