[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here

HP OpenVMS System Management Utilities Reference Manual


Previous Contents Index

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.

IO LIST_WWID (Alpha and I64)

Applies only to tape devices on Fibre Channel. Lists all tape device WWIDs that are not yet configured on Fibre Channel.

You can use the output of this command as input to the SYSMAN IO CREATE_WWID and SYSMAN IO REPLACE_WWID commands.


Format

IO LIST_WWID


Example


SYSMAN> IO LIST_WWID
%SYSMAN-I-OUTPUT, command execution on node ROCKY

On port _ROCKY$PGA0:, the following tape WWIDs are not yet configured:

Target 3, LUN 1, COMPAQ   SuperDLT1
WWID=02000008:500E-09E0-0005-30D7

Target 3, LUN 3, COMPAQ   SDX-500C
WWID=0C000008:0800-4606-C00D-473F

Target 4, LUN 1, COMPAQ   SuperDLT1
WWID=02000008:500E-09E0-0005-30D7

Target 4, LUN 3, COMPAQ   SDX-500C
WWID=0C000008:0800-4606-C00D-473F

      

In this example, each drive is listed twice because the tape bridge is dual-ported, with one FC port at target 3 and the other FC port at target 4.

IO LOAD (Alpha and I64)

On Alpha and I64 systems, loads an I/O driver.

On VAX systems, use the SYSGEN command LOAD.

You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO LOAD command.

Note

Be very careful when issuing a SYSMAN IO LOAD command because the system does little error-checking.

Format

IO LOAD filespec


Parameter

filespec

Specifies the file name of the driver to be loaded. This parameter is required.

Qualifier

/LOG=(ALL,DPT)

Controls whether SYSMAN displays information about drivers that have been loaded. The default value for the /LOG qualifier is /LOG=ALL. The driver prologue table (DPT) address is displayed when either /LOG=DPT or /LOG=ALL is specified.

Description

The SYSMAN IO LOAD command loads an I/O driver. VAX system managers use the SYSGEN command LOAD. You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO LOAD command.

Example


SYSMAN> IO LOAD/LOG SYS$DKDRIVER
%SYSMAN-I-IOADDRESS, the DPT is located at address 80D5A000
      

This example loads device SYS$DKDRIVER and displays the address of the driver prologue table (DPT).

IO REBUILD (Alpha and I64)

On Alpha and I64 systems, rebuilds device configuration tables in preparation for using the SYSMAN IO AUTOCONFIGURE command to reconfigure the system.

You must have CMKRNL privilege to use the SYSMAN IO REBUILD command.


Format

IO REBUILD


Parameters

None.

Qualifier

/VERIFY

Causes SYSMAN to read and process the files SYS$SYSTEM:SYS$USER_CONFIG.DAT and SYS$SYSTEM:CONFIG.DAT, but not to apply the files to the I/O database. Messages will be displayed for any errors that are encountered. This command can be used by developers to test new changes to SYS$SYSTEM:SYS$USER_CONFIG.DAT without modifying the current system.

Description

The SYSMAN IO REBUILD command rebuilds the system's device configuration tables by reading and parsing the SYS$SYSTEM:SYS$USER_CONFIG.DAT and SYS$SYSTEM:SYS$CONFIG.DAT files.

To debug modifications to the SYS$SYSTEM:SYS$USER_CONFIG.DAT file, you can use the SYSMAN IO REBUILD and SYSMAN IO AUTOCONFIGURE commands to load drivers without having to reboot. Once you load a driver for an adapter, however, you cannot reload it without rebooting the system.


Example


SYSMAN> IO REBUILD
SYSMAN> IO AUTOCONFIGURE

      

The first command in this example rebuilds device configuration tables. The second command reads the device configuration tables and loads drivers for newly defined drivers.

IO REPLACE_WWID (Alpha and I64)

This command allows a user to replace one tape drive behind a Network Storage Router (NSR) with another tape drive at the same Fibre Channel (FC) Logical Unit Number (LUN) location.

This command updates all the necessary file and memory data structures with the WWID of the new tape drive. The name of the replacement drive will be the same as the name of the original drive.

This command is primarily intended to be used when a hardware problem occurs on a tape drive, and a replacement drive must installed in its place.

The command requires CMKRNL privilege. It applies only to FC tapes behind a Fibre Channel tape bridge such as an NSR or MDR (Modular Data Router).

For more information about Fibre Channel, see the Guidelines for OpenVMS Cluster Configurations.


Format

IO REPLACE_WWID devnam_string/WWID=wwid_string


Parameter

devnam_string

Specifies a tape device name.

Qualifier

/WWID=wwid_string

Specifies a string that comes directly from a SYSMAN IO LIST_WWID display. The use of this qualifier is appropriate only under the circumstances explained in the description below.

Description

You can use the two parameters, devnam_string and wwid_string, with the REPLACE_WWID command to replace a broken tape device with a new device. The command automatically updates the data structures that record the new devnam-WWID correlation, and the device automatically begins to function correctly.

This command is useful in two different cases:

  • In one case, the drive might malfunction and need to be replaced immediately without rebooting the system. If this happens, the drive is physically replaced with a new drive, and the command SYSMAN IO REPLACE_WWID $2$MGAn is issued clusterwide. The /WWID qualifier is not appropriate in this case, because the new WWID is automatically detected using information stored in the device's data structures.
  • In the other case, the drive might malfunction and not be replaced until after the system has been shut down or rebooted. The device name no longer appears in the SHOW DEVICE display because the device failed to configure during the reboot.
    The configuration failure occurred either because the broken drive did not respond, or because the new drive has a different WWID from the one SYSMAN IO AUTOCONFIGURE expected at boot time. Therefore, in this situation, in which the device name is in SYS$DEVICES.DAT but not in the SHOW DEVICE display, use the /WWID qualifier to define the new devnam-WWID correlation.
    Follow these steps clusterwide:
    1. Execute the SYSMAN IO LIST_WWID command to display the new WWID.
    2. Use the command SYSMAN IO REPLACE_WWID $2$MGAn/WWID=new_wwid to define the new correlation.
    3. Use the SYSMAN IO AUTOCONFIGURE command to configure the device.

When you use the SYSMAN IO LIST_WWID command, keep in mind that:

  • You must set the replacement device to the same SCSI target ID as the original device.
  • You must stop all activity on the device before issuing the SYSMAN IO REPLACE_WWID command.
  • The command requires CMKRNL privilege and applies only to FC tapes behind an NSR or MDR.

Example


SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> IO REPLACE_WWID $2$MGA3/WWID=02000008:500E-09E0-0005-30D7
SYSMAN> IO AUTOCONFIGURE
      

In this example, the device named $2$MGA3 malfunctioned and was replaced while the system was down. Upon reboot, the drive did not get configured, because its new WWID did not match the WWID that OpenVMS expected. Therefore, the user redefines the devnam-WWID correlation and is then able to configure $2$MGA3 correctly. The specified WWID comes from the output of the SYSMAN IO LIST_WWID command.

IO SCSI_PATH_VERIFY (Alpha and I64)

On Alpha and I64 systems, the SYSMAN IO SCSI_PATH_VERIFY subcommand checks each SCSI and FC path in the system to determine whether the attached device has been changed. If a device change is detected, then the SCSI or FC path is disconnected in the IO database. This allows the path to be reconfigured on the new device, by using the SYSMAN IO AUTOCONFIGURE command.

You must have CMKRNL privilege to use the SYSMAN IO SCSI_PATH_VERIFY command.


Format

IO SCSI_PATH_VERIFY


Parameters

None.

Qualifiers

None.

Description

You usually enter the SYSMAN IO SCSI_PATH_VERIFY command after performing an online reconfiguration of a SCSI or an FC interconnect. The command reads the device type and device identifier on each SCSI and FC path in the system. If the device does not match the data stored in the IO database, then the path is disconnected in the IO database. Following a SYSMAN IO SCSI_PATH_VERIFY command, you usually enter a SYSMAN IO AUTOCONFIGURE command, which updates the IO database to match the new SCSI or FC configuration.

Example


SYSMAN> IO SCSI_PATH_VERIFY
SYSMAN> IO AUTOCONFIGURE

      

The first command in this example checks all SCSI paths and disconnects the ones that are no longer valid. The second command autoconfigures all devices that are physically attached to the system.

IO SET EXCLUDE (Alpha and I64)

On Alpha and I64 systems, sets the permanent exclusion list to be used when configuring devices automatically.

Format

IO SET EXCLUDE = device_name


Parameter

device_name

Specifies the device type to be excluded from automatic configuration. Use valid device names or mnemonics that indicate the devices to be included in the permanent exclusion list. You can specify wildcards.

Qualifiers

None.

Description

Sets the permanent exclusion list to be used when configuring devices.

You can use this command to permanently specify device autoconfiguration to exclude Fibre Channel port driver devices (FG) and any SCSI port driver devices (PK) at each system boot. (To specify permanently the exclusion or inclusion of devices for the duration of a manual configuration command, use the /EXCLUDE or /SELECT qualifier with the SYSMAN IO AUTOCONFIGURE command.)

You cannot use the SYSMAN IO SET EXCLUDE command to 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.


Example


SYSMAN> IO SET EXCLUDE=(DKC500,DKD*)
      

This example specifies that DKC500 and all DKD devices are not to be autoconfigured.

For additional examples that show how to specify device names, see the /SELECT qualifier.

IO SET PREFIX (Alpha and I64)

On Alpha and I64 systems, sets the prefix list that is used to manufacture the IOGEN Configuration Building Module (ICBM) names.

Format

IO SET PREFIX =icbm_prefix


Parameter

icbm_prefix

Specifies ICBM prefixes. These prefixes are used by the SYSMAN IO AUTOCONFIGURE command to build ICBM image names.

Qualifiers

None.

Description

The SYSMAN IO SET PREFIX command sets the prefix list which is used to manufacture ICBM names.

Example


SYSMAN> IO SET PREFIX=(SYS$,PSI$,VME_)
      

This example specifies the prefix names used by SYSMAN IO AUTOCONFIGURE to build the ICBM names. The prefixes are SYS$, PSI$, and VME_.

IO SHOW BUS (Alpha and I64)

On Alpha and I64 systems, lists all the buses, node numbers, bus names, TR numbers, and base CSR addresses on the system. This display exists primarily for internal engineering support.

On VAX systems, use the SYSGEN command SHOW/BUS.


Parameters

None.

Qualifiers

None.

Description

The SYSMAN IO SHOW BUS command lists all the buses, node numbers, bus names, TR numbers, and base CSR addresses. This display exists primarily for internal engineering support. You must have CMKRNL privilege to use SYSMAN IO SHOW BUS.

Example


SYSMAN> IO SHOW BUS
_Bus__________Node_TR#__Name____________Base CSR__________
LSB           0    1    EV3 4MB        FFFFFFFF86FA0000
LSB           6    1    MEM            FFFFFFFF86FC4000
LSB           7    1    MEM            FFFFFFFF86FCA000
LSB           8    1    IOP            FFFFFFFF86FD0000
XZA XMI-SCSI  0    3    XZA-SCSI       0000008001880000
XZA XMI-SCSI  1    3    XZA-SCSI       0000008001880000
XZA XMI-SCSI  0    4    XZA-SCSI       0000008001900000
XZA XMI-SCSI  1    4    XZA-SCSI       0000008001900000
XMI           4    2    LAMB           0000008001A00000
DEMNA         0    5    Generic XMI    0000008001E80000
DEMNA         0    6    Generic XMI    0000008001F00000
      

This example is from a DEC 7000 Model 600. Displays vary among different Alpha and I64 systems.

The indentation levels are deliberate in this display. They indicate the hierarchy of the adapter control blocks in the system. The column titles in the display have the following meanings:

Column Titles Meaning
Bus Identity of the bus
Node Index into the associated bus array; the bus slot
TR# Nexus number of the adapter to which the specified device is connected
Name Name of the device
Base CSR Base CSR address of the device

On Alpha and I64 systems, you can use the SDA command CLUE CONFIG to display additional information including hardware adapters and devices. This command is documented in the OpenVMS Alpha System Dump Analyzer Utility Manual.

For more information about loading and configuing device drivers, see Writing OpenVMS Alpha Device Drivers in C.

IO SHOW DEVICE (Alpha and I64)

On Alpha and I64 systems, displays information about device drivers loaded into the system, the devices connected to them, and their I/O databases. All addresses are in hexadecimal and are virtual.

On VAX systems, use the SYSGEN command SHOW/DEVICE.


Format

IO SHOW DEVICE


Parameters

None.

Qualifiers

None.

Description

The SYSMAN IO SHOW DEVICE command displays information about the device drivers loaded into the system, the devices connected to them, and their I/O databases.

The SYSMAN IO SHOW DEVICE command specifies that the following information be displayed about the specified device driver:

Driver Name of the driver
Dev Name of each device connected to the driver
DDB Address of the device's device data block
CRB Address of the device's channel request block
IDB Address of the device's interrupt dispatch block
Unit Number of each unit on the device
UCB Address of each unit's unit control block

All addresses are in hexadecimal and are virtual.

For additional information about SYSMAN, see A Comparison of System Management on OpenVMS AXP and OpenVMS VAX (archived) but available on the OpenVMS Documentation CD-ROM) and the HP OpenVMS System Manager's Manual.


Example


SYSMAN> IO SHOW DEVICE
      

The following example is a sample display produced by the SYSMAN IO SHOW DEVICE command:


__Driver________Dev_DDB______CRB______IDB______Unit_UCB_____
SYS$FTDRIVER
                FTA 802CE930 802D1250 802D04C0
                                                 0 801C3710
SYS$EUDRIVER
                EUA 802D0D80 802D1330 802D0D10
                                                 0 801E35A0
SYS$DKDRIVER
                DKI 802D0FB0 802D0F40 802D0E60
                                                 0 801E2520
SYS$PKADRIVER
                PKI 802D1100 802D13A0 802D1090
                                                 0 801E1210
SYS$TTDRIVER
OPERATOR
NLDRIVER

SYS$TTDRIVER, OPERATOR, and NLDRIVER do not have devices associated with them.

IO SHOW EXCLUDE (Alpha and I64)

On Alpha and I64 systems, displays the permanent exclusion list used in the autoconfiguration of devices.

Format

IO SHOW EXCLUDE


Parameters

None.

Qualifiers

None.

Description

The SYSMAN IO SHOW EXCLUDE command displays the permanent exclusion list on the console. This list is used in the autoconfiguration of devices.

Example


SYSMAN> IO SHOW EXCLUDE
%SYSMAN-I-IOEXCLUDE, the current permanent exclusion list is: DKC500,DKD*
      

This example shows the permanent exclusion list used in the autoconfiguration of devices; the current list contains DKC500 and all DKD devices.

IO SHOW PREFIX (Alpha and I64)

On Alpha and I64 systems, displays the current prefix list used in the manufacture of IOGEN Configuration Building Module (ICBM) names.

Format

IO SHOW PREFIX


Parameters

None.

Qualifiers

None.

Description

The SYSMAN IO SHOW PREFIX command displays the current prefix list on the console. This list is used by the SYSMAN IO AUTOCONFIGURE command to build ICBM names.

Example


SYSMAN> IO SHOW PREFIX
%SYSMAN-I-IOPREFIX, the current prefix list is: SYS$,PSI$,VME_
      

This example shows the prefixes used by SYSMAN IO AUTOCONFIGURE to build ICBM names.

LICENSE LOAD

Activates licenses registered in the LICENSE database.

Requires CMKRNL, SYSNAM, and SYSPRV privileges.

Note

Except for the number of status messages returned, the following commands are functionally equivalent:


SYSMAN> LICENSE LOAD
$ LICENSE LOAD

To see all the status messages on remote nodes for the DCL command, you can use the following SYSMAN command:


SYSMAN> DO LICENSE LOAD

Format

LICENSE LOAD product


Parameter

product

Specifies the name of the product whose license you want to activate.

Qualifiers

/DATABASE=filespec

Specifies the location of the LICENSE database. The default file specification is SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. Using the /DATABASE qualifier is not necessary if you use the default LICENSE database name and location.

/PRODUCER=string

Specifies the name of the company that owns the product for which you have a license. Use this qualifier only if the product is from a company other than HP.

Description

You can use the LICENSE LOAD command to activate licenses on multiple systems and on nonlocal systems in the system management environment. The SYSMAN LICENSE commands are a subset of the License Management Facility (LMF) commands. For more information about the LMF, see the HP OpenVMS License Management Utility Manual.

Example


SYSMAN> LICENSE LOAD FORTRAN
      

This example activates the license for HP Fortran for OpenVMS. Because the license is for a HP product, the command does not include the /PRODUCER qualifier.


Previous Next Contents Index