| Previous | Contents | Index |
On Alpha and Integrity servers, removes a record from the System Dump Priority registry file.
DUMP_PRIORITY REMOVE process-name /UIC=uic
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."
/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.
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.)
On Alpha and Integrity servers, lists the contents of the in-memory copy of the System Dump Priority registry file.
DUMP_PRIORITY SHOW
None.
None.
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.
On Alpha and Integrity servers, clears the in-memory copy of the System Dump Priority registry file.
DUMP_PRIORITY UNLOAD
None.
None.
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.
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.
EXIT
None.
None.
Provides online help for using the SYSMAN commands, parameters, and qualifiers. Press Ctrl/Z to exit.
HELP [keyword...]
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.
None.
SYSMAN> HELP DO
|
This command displays help information about the SYSMAN command DO.
On Alpha and Integrity servers, automatically identifies and configures all hardware devices attached to a system by connecting devices and loading their drivers.You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO AUTOCONFIGURE command.
IO AUTOCONFIGURE
None.
/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 24-2 shows /SELECT qualifier examples.
Table 24-2 /SELECT Qualifier Examples Command Devices That Are Configured Devices That Are
Not Configured/SELECT=P* PKA,PKB,PIA None /SELECT=PK* PKA,PKB PIA /SELECT=PKA* PKA PKB,PIA /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 and 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.
The SYSMAN IO AUTOCONFIGURE command identifies and configures all hardware devices attached to a system. It connects devices and loads their drivers. You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO AUTOCONFIGURE command.
| #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.
On Alpha and Integrity servers, connects a hardware device and loads its driver, if the driver is not already loaded.You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO CONNECT command.
Note
Be very careful when issuing a SYSMAN IO CONNECT command because the system does little error-checking. A misspelled device name, for example, will damage the I/O database and could cause the system to fail.
IO CONNECT device-name[:]
device-name[:]
Specifies the name of the hardware device to be connected. The device name requires the following format:device-type controller unit-numberFor example, in the designation LPA0, LP is a line printer on controller A at unit number 0. If you use the /NOADAPTER qualifier, the device is the software to be loaded.
/ADAPTER=tr_number
/NOADAPTER (default)
Specifies the nexus number of the adapter to which the specified device is connected. It is a nonnegative 32-bit integer. The /NOADAPTER qualifier indicates that the device is not associated with any particular hardware. The /NOADAPTER qualifier is compatible with the /DRIVER_NAME qualifier only./CSR=csr_address
Specifies the CSR address for the device being configured. This address must be specified in hexadecimal. You must precede the CSR address with %X. The CSR address is a quadword value that is loaded into IDB$Q_CSR without any interpretation by SYSMAN. This address can be physical or virtual, depending on the specific device being connected:
- /CSR=%X3A0140120 for a physical address
- /CSR=%XFFFFFFFF807F8000 for a virtual address (the sign extension is required for Alpha and Integrity servers virtual addresses)
This qualifier is required if /ADAPTER=tr_number is specified.
/DRIVER_NAME=filespec
Specifies the name of the device driver that you are loading. If you do not specify this qualifier, SYSMAN obtains the default in the same way that the SYSGEN default name is determined. For example, if you want to load the HP-supplied SYS$ELDRIVER.EXE, the prefix SYS$ must be present. Without the SYS$, SYSMAN looks for ELDRIVER.EXE in SYS$LOADABLE_IMAGES. This implementation separates the user device driver namespace from the HP-supplied device driver namespace./LOG=(ALL,CRB,DDB,DPT,IDB,SB,UCB)
/NOLOG (default)
Controls whether SYSMAN displays the addresses of the specified control blocks. The default value for the /LOG qualifier is /LOG=ALL. If /LOG=UCB is specified, a message similar to the following one is displayed:
%SYSMAN-I-IOADDRESS, the UCB is located at address 805AB000/MAX_UNITS=maximum-number-of-units
Specifies the maximum number of units the driver can support. The default is specified in the driver prologue table (DPT) of the driver. If the number is not specified in the DPT, the default is 8. This number must be greater than or equal to the number of units specified by /NUM_UNITS. This qualifier is optional./NUM_UNITS=number-of-units
Specifies the number of units to be created. The starting device number is the number specified in the device name parameter. For example, the first device in DKA0 is 0. Subsequent devices are numbered sequentially. The default is 1. This qualifier is optional./NUM_VEC=vector-count
Specifies the number of vectors for this device. The default vector count is 1. The /NUM_VEC qualifier is optional. This qualifier should be used only when using the /VECTOR_SPACING qualifier. When using the /NUM_VEC qualifier, you must also use the /VECTOR qualifier to supply the base vector./SYS_ID=number-of-remote-system
Indicates the SCS system ID of the remote system to which the device is to be connected. It is a 64-bit integer; you must specify the remote system number in hexadecimal. The default is the local system. This qualifier is optional./VECTOR=(vector-address,...)
Specifies the interrupt vectors for the device or lowest vector. This is either a byte offset into the SCB of the interrupt vector for directly vectored interrupts or a byte offset into the ADP vector table for indirectly vectored interrupts. The values must be longword aligned. To specify the vector address in octal or hexadecimal, precede the address with %O or %X, respectively. The /VECTOR qualifier is required when you use the /ADAPTER=tr_number qualifier or the /NUM_VEC=vector-count qualifier. You can list up to 64 vectors./VECTOR_SPACING=number-of-bytes-between-vectors
Specifies the spacing between vectors. Specify the amount as a multiple of 16 bytes. The default is 16. You must specify both the base vector with /VECTOR and the number of vectors with /NUM_VEC. This qualifier is optional.
The SYSMAN IO CONNECT command connects a hardware device and loads its driver, if the driver is not already loaded. You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO CONNECT command.The chapter "Managing Peripheral Devices" in the HP OpenVMS System Manager's Manual contains information about file-based device configuration support.
| #1 |
|---|
SYSMAN> IO CONNECT DKA0:/DRIVER_NAME=SYS$DKDRIVER/CSR=%X80AD00-
/ADAPTER=4/NUM_VEC=3/VECTOR_SPACING=%X10/VECTOR=%XA20/LOG
%SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40
%SYSMAN-I-IOADDRESS, the DDB is located at address 805AA740
%SYSMAN-I-IOADDRESS, the DPT is located at address 80D2A000
%SYSMAN-I-IOADDRESS, the IDB is located at address 805AEE80
%SYSMAN-I-IOADDRESS, the SB is located at address 80417F80
%SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0
|
The command in this example connects device DKA0, loads driver SYS$DKDRIVER, and specifies the following data:
Physical CSR address
Adapter number
Number of vectors
Spacing between vectors
Interrupt vector addressThe /LOG qualifier displays the addresses of all control blocks, as shown.
| #2 |
|---|
SYSMAN> IO CONNECT DKA0:/DRIVER_NAME=SYS$DKDRIVER/CSR=%X80AD00-
/ADAPTER=4/VECTOR=(%XA20,%XA30,%XA40)/LOG=(CRB,DPT,UCB)
%SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40
%SYSMAN-I-IOADDRESS, the DPT is located at address 80D2A000
%SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0
|
The command in this example connects device DKA0, loads driver SYS$DKDRIVER, and specifies the following data:
Physical CSR address
Adapter number
Addresses for interrupt vectorsThe /LOG qualifier displays the addresses of the channel request block (CRB), the driver prologue table (DPT), and the unit control block (UCB).
| #3 |
|---|
SYSMAN> IO CONNECT FTA0:/DRIVER=SYS$FTDRIVER/NOADAPTER/LOG=(ALL)
%SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40
%SYSMAN-I-IOADDRESS, the DDB is located at address 805AA740
%SYSMAN-I-IOADDRESS, the DPT is located at address 80D2A000
%SYSMAN-I-IOADDRESS, the IDB is located at address 805AEE80
%SYSMAN-I-IOADDRESS, the SB is located at address 80417F80
%SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0
|
The command in this example connects pseudoterminal FTA0, loads driver SYS$FTDRIVER, and uses the /NOADAPTER qualifier to indicate that FTA0 is not an actual hardware device. The /LOG=(ALL) qualifier displays the addresses of all control blocks, as shown.
For more information about loading and configuring device drivers, see
Writing OpenVMS Alpha Device Drivers in C (Margie Sherlock and
Leonard S. Szubowicz, Digital Press, 1996).
IO CREATE_WWID (Alpha and Integrity servers)
Assigns a specific, previously unused device name to a specific, previously unused worldwide identifier (WWID) from the SYSMAN IO LIST_WWID display.HP recommends that you execute this command clusterwide and that you follow the command with a SYSMAN IO AUTOCONFIGURE command to actually configure the device.
IO CREATE_WWID devnam_string/WWID=wwid_string
devnam_string
Specifies a device-name string. The string must be in the form $2$MGAn, where n is less than 9999.
/WWID=wwid_string
Specifies a WWID string that comes directly from a SYSMAN IO LIST_WWID display.This qualifier is required.
This command is an alternative to the SYSMAN IO FIND_WWID command, which selects system-generated device names for the discovered WWIDs. Do not, however, use the SYSMAN IO CREATE_WWID command after the SYSMAN IO FIND_WWID command to redefine WWID correlations. Also, do not specify device and WWID strings in the SYSMAN IO CREATE_WWID command that are specified elsewhere in the cluster.
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> IO CREATE_WWID $2$MGA5/WWID=04100022:"DEC TZ89 (C) DECCX939S2777"
SYSMAN> IO CREATE_WWID $2$MGA3/WWID=02000008:500E-09E0-0005-30D7
SYSMAN> IO AUTOCONFIGURE
|
The commands in this example create two device names, $2$MGA5 and $2$MGA3, and configure the devices.
The SYSMAN IO FIND_WWID command probes all Fibre Channel ports, detects all previously undiscovered tapes and medium changers behind a Network Storage Router (NSR) or a Modular Data Router (MDR), and assigns a worldwide identifier (WWID) to each one.The command also displays a list of the devices and their assigned device names and automatically records this information in the SYS$SYSTEM:SYS$DEVICES.DAT file. Finally, the command updates relevant local and clusterwide memory structures.
To configure newly attached Fibre Channel tapes, use this command prior to running the SYSMAN command IO AUTOCONFIGURE.
You must have CMKRNL privilege to use the SYSMAN IO FIND_WWID command.
For more information about Fibre Channel, see the Guidelines for OpenVMS Cluster Configurations.
IO FIND_WWID
Prior to configuring a tape device on Fibre Channel ports, the worldwide identifier (WWID) of the device must be detected and stored, along with a device name, in the text file SYS$SYSTEM:SYS$DEVICES.DAT. You use the SYSMAN command IO FIND_WWID to accomplish this.The SYSMAN IO FIND_WWID command probes all Fibre Channel ports and locates all tape and medium changer devices. For tapes and medium changers that have not been detected by any previous SYSMAN IO FIND_WWID command, IO FIND_WWID assigns a device name, retrieves the WWID of the device, stores the device name and WWID data in the SYS$SYSTEM:SYS$DEVICES.DAT file, and updates memory structures.
Because the main goal of SYSMAN IO FIND_WWID is to populate the SYS$DEVICES.DAT file, you need to invoke the SYSMAN IO FIND_WWID command only one time for each new device. Note that using the SYSMAN IO FIND_WWID command for the first time detects all existing tape and medium changer devices on the system at that time.
Once the information is stored in the file, subsequent use of the SYSMAN IO AUTOCONFIGURE command reads the file and configures the tape and medium changer devices automatically, loading or connecting the device drivers as needed. The SYS$DEVICES.DAT file is read during each system reboot, initiating the automatic configuration of tapes and medium changers on the Fibre Channel. (SYSMAN IO FIND_WWID does not load or connect the actual device drivers.)
Note
If you add more devices to the system at a later time, you must powercycle the MDR to update internal mapping information. You must also run the SYSMAN IO FIND_WWID command again to append the new device information to the SYS$DEVICES.DAT file.Similarly, for the Network Storage Router (NSR), the LUN map must be updated.
In an OpenVMS cluster environment, you must run the SYSMAN IO FIND_WWID command on each node in the cluster to update various data structures in memory. Alternatively, you can run SYSMAN IO FIND_WWID on one node, and then reboot the other nodes that share that same system disk, because the SYS$DEVICES.DAT file is read at boot time and causes memory structures to be correctly initialized.
In the case of multiple system disks in the cluster, ensure that all copies of the SYS$DEVICES.DAT file are kept consistent, preferably by running the SYSMAN IO FIND_WWID command on all nodes. Alternatively, you can run IO FIND_WWID to update just one SYS$DEVICES.DAT file, and then manually edit the remaining SYS$DEVICES.DAT files by cutting and pasting the appropriate devnam/WWID records from the original file to the target files.
HP recommends that you refrain from copying the entire original file to another system disk, because the SYS$DEVICES.DAT file is also used to define Port Allocation Classes, and PAC entries could be inadvertently transferred to the target system.
SYSMAN> IO FIND_WWID
%SYSMAN-I-OUTPUT, command execution on node SAMPLE
On port _SAMPLE$PGA0:, the following tape WWIDs and their proposed
device names have been found but not yet configured:
[Device $2$GGA0]
WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017"
[Device $2$MGA0]
WWID=04100022:"DEC TZ89 (C) DECCX939S2777"
[Device $2$MGA1]
WWID=04100022:"DEC TZ89 (C) DECCX942S6295"
|
This is a configuration example using a TL891 tape library. The SYSMAN command IO FIND_WWID displays a list of all previously undiscovered tape devices and their device names.
Note that the overall WWID consists of everything to the right of the equal sign. Each such WWID is unique; however, the header portion might not be unique, because the header reflects only the basic type and length of the the WWID data.
The SYSMAN IO FIND_WWID command automatically records the information about the new tape devices in SYS$SYSTEM:SYS$DEVICES.DAT:
$ TYPE SYS$SYSTEM:SYS$DEVICES.DAT ! ! Updated 23-OCT-2002 14:17:41.85: DEC TL800 ! [Device $2$GGA0] WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017" ! ! ! Updated 23-OCT-2002 14:17:41.93: DEC TZ89 ! [Device $2$MGA0] WWID=04100022:"DEC TZ89 (C) DECCX939S2777" ! ! ! Updated 23-OCT-2002 14:17:42.01: DEC TZ89 ! [Device $2$MGA1] WWID=04100022:"DEC TZ89 (C) DECCX942S6295" !You would then use the SYSMAN command IO CONFIGURE to configure these devices. After you completed this step, the SHOW DEVICE/FULL command would display the worldwide identifier of the tape.
| Previous | Next | Contents | Index |