 |
HP OpenVMS System Management Utilities Reference
Manual
DUMP_PRIORITY ADD (Alpha and I64)
On Alpha and I64 systems, 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.
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]
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.
Qualifiers
/INFORMATIONAL (default)
/NOINFORMATIONAL
On Alpha and I64 systems, allows you to suppress or reinstate the
display of informational messages. Suppressing message can be useful
when you are running in a software installation environment and want to
avoid the display of informational messages.
/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 = [group,*]
|
To select processes with the specified name in the group called
"group".
|
/UIC = [100,*]
|
To select processes with the specified name in 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 /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.
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.
DUMP_PRIORITY LIST (Alpha and I64)
On Alpha and I64 systems, lists the contents of the System Dump
Priority registry file.
Format
DUMP_PRIORITY LIST
Parameters
None.
Qualifiers
None.
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.)
DUMP_PRIORITY LOAD (Alpha and I64)
On Alpha and I64 systems, loads the contents of the System Dump
Priority registry file into memory for BUGCHECK to use.
Format
DUMP_PRIORITY LOAD
Parameters
None.
Qualifiers
None.
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.
DUMP_PRIORITY MODIFY (Alpha and I64)
On Alpha and I64 systems, modifies an entry in the System Dump Priority
registry file.
Format
DUMP_PRIORITY MODIFY process-name /UIC=uic [/NEWUIC=newuic][/WILD_CARD]
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.
Qualifiers
/INFORMATIONAL (default)
/NOINFORMATIONAL
On Alpha and I64 systems, allows you to suppress or reinstate the
display of informational messages. Suppressing message can be useful
when you are running in a software installation environment and want to
avoid the display of informational messages.
/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 = [group,*]
|
To select processes with the specified name in the group called
"group".
|
/UIC = [100,*]
|
To select processes with the specified name in 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 /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.
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.)
- 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*.
- 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.
- The third DUMP_PRIORITY MODIFY command
modifies only the process name wildcarding flag with the /WILD_CARD
qualifier.
DUMP_PRIORITY REMOVE (Alpha I64)
On Alpha and I64 systems, removes a record from the System Dump
Priority registry file.
Format
DUMP_PRIORITY REMOVE process-name /UIC=uic
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.
Qualifier
/INFORMATIONAL (default)
/NOINFORMATIONAL
On Alpha and I64 systems, allows you to suppress or reinstate the
display of informational messages. Suppressing message can be useful
when you are running in a software installation environment and want to
avoid the display of informational messages displayed.
/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.
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.)
DUMP_PRIORITY SHOW (Alpha and I64)
On Alpha and I64 systems, lists the contents of the in-memory copy of
the System Dump Priority registry file.
Format
DUMP_PRIORITY SHOW
Parameters
None.
Qualifiers
None.
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.
DUMP_PRIORITY UNLOAD (Alpha and I64)
On Alpha and I64 systems, clears the in-memory copy of the System Dump
Priority registry file.
Format
DUMP_PRIORITY UNLOAD
Parameters
None.
Qualifiers
None.
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.
EXIT
Terminates the SYSMAN session and returns control to the DCL command
level. Any profile changes, established on the local node with the
command SET PROFILE, are restored to their values at the time SYSMAN
was invoked. You can also press Ctrl/Z to exit at any time.
Format
EXIT
Parameters
None.
Qualifiers
None.
HELP
Provides online help for using the SYSMAN commands, parameters, and
qualifiers. Press Ctrl/Z to exit.
Format
HELP [keyword...]
Parameter
keyword
Specifies the command, parameter, or qualifier for which you want help.
If you omit the keyword, the HELP command displays a list of Help
topics and prompts you for a particular keyword.
Qualifiers
None.
Example
This command displays help information about the SYSMAN command DO.
IO AUTOCONFIGURE (Alpha and I64)
On Alpha and I64 systems, automatically identifies and configures all
hardware devices attached to a system by connecting devices and loading
their drivers.
On VAX systems, use the SYSGEN command AUTOCONFIGURE.
You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO
AUTOCONFIGURE command.
Format
IO AUTOCONFIGURE
Parameters
None.
Qualifiers
/SELECT=(device_name)
Specifies the device type to be automatically configured. Use valid
device names or mnemonics that indicate the devices to be included in
the configuration. You can use wildcard characters with this qualifier.
See the Usage Notes under the /EXCLUDE qualifier for notes that apply
to both qualifiers.
Table 21-2 shows /SELECT qualifier examples.
/EXCLUDE=(device_name)
Specifies the device type that should not be automatically configured.
Use valid device names or mnemonics that indicate the devices to be
excluded from the configuration. You can use wildcard characters with
this qualifier.
Usage Notes for the /SELECT and /EXCLUDE Qualifiers
- The /SELECT and /EXCLUDE qualifiers are not mutually exclusive, as
they are on VAX systems. You can specify both qualifiers on the command
line.
- You can use the /SELECT and /EXCLUDE qualifiers to permanently
specify device autoconfiguration to include and exclude Fibre Channel
port driver devices (FG) and any SCSI port driver devices (PK) for the
duration of a manual autoconfiguration command. (To permanently specify
devices to be excluded at each system boot, use the SYSMAN command IO
SET EXCLUDE.)
You cannot use the /SELECT and /EXCLUDE qualifiers to
include and exclude any of the following device types:
- SCSI class-driver devices (DK, MK, GK) whose names include a port
allocation class or an HSZ allocation class
- Fibre Channel class-driver devices (PG, DG, GG)
This restriction also applies to SCSI devices on OpenVMS Alpha
Version 7.1 systems, if the SCSI device names include a port allocation
class.
/LOG
Controls whether the SYSMAN IO AUTOCONFIGURE command displays
information about loaded devices.
Description
The SYSMAN IO AUTOCONFIGURE command identifies and configures all
hardware devices attached to a system. VAX system managers use the
SYSGEN command AUTOCONFIGURE. It connects devices and loads their
drivers. You must have CMKRNL and SYSLCK privileges to use the SYSMAN
IO AUTOCONFIGURE command.
Examples
#1 |
SYSMAN> IO AUTOCONFIGURE/EXCLUDE=DKA0
|
This command autoconfigures all devices on the system except DKA0.
IO AUTOCONFIGURE automatically configures all standard devices that are
physically attached to the system, except for the network
communications device.
#2 |
SYSMAN> IO AUTOCONFIGURE/LOG
|
The /LOG qualifier displays information about all the devices that
AUTOCONFIGURE loads.
|