Document revision date: 19 July 1999 | |
Previous | Contents | Index |
On Alpha systems, loads an I/O driver. On VAX systems, use the SYSGEN command LOAD.You must have CMKRNL and SYSLCK privileges to use the IO LOAD command.
IO LOAD filespec
filespec
Specifies the file name of the driver to be loaded. This parameter is required.
/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.
The 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 IO LOAD command.
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).
On Alpha systems, rebuilds device configuration tables in preparation for using the IO AUTOCONFIGURE command to reconfigure the system.You must have CMKRNL privilege to use the IO REBUILD command.
IO REBUILD
None.
/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.
The 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 IO REBUILD and 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.
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 SCSI_PATH_VERIFY (Alpha Only)
On Alpha systems, the 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 IO AUTOCONFIGURE command.You must have CMKRNL privilege to use the IO SCSI_PATH_VERIFY command.
IO SCSI_PATH_VERIFY
None.
None.
You usually enter the 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 an IO SCSI_PATH_VERIFY command, you usually enter an IO AUTOCONFIGURE command, which updates the IO database to match the new SCSI or FC configuration.
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.
On Alpha systems, sets the permanent exclusion list to be used when configuring devices automatically.
IO SET EXCLUDE = (device_name)
(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.
None.
Sets the permanent exclusion list to be used when configuring devices.
SYSMAN> IO SET EXCLUDE=(DKC500,DKD*) |
This example specifies that DKC500 and all DKD devices are not to be autoconfigured.
Refer to the /SELECT qualifier for additional examples that show how to specify device names.
On Alpha systems, sets the prefix list that is used to manufacture the IOGEN Configuration Building Module (ICBM) names.
IO SET PREFIX =icbm_prefix
icbm_prefix
Specifies ICBM prefixes. These prefixes are used by the IO AUTOCONFIGURE command to build ICBM image names.
None.
The IO SET PREFIX command sets the prefix list which is used to manufacture ICBM names.
SYSMAN> IO SET PREFIX=(SYS$,PSI$,VME_) |
This example specifies the prefix names used by IO AUTOCONFIGURE to build the ICBM names. The prefixes are SYS$, PSI$, and VME_.
On Alpha 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.
None.
None.
The 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 IO SHOW BUS.
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 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 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, refer
to Writing OpenVMS Alpha Device Drivers in C.
IO SHOW DEVICE (Alpha Only)
On Alpha 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.
IO SHOW DEVICE
None.
None.
The 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 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.
Refer to A Comparison of System Management on OpenVMS AXP and OpenVMS VAX1 and the OpenVMS System Manager's Manual for additional information about SYSMAN.
SYSMAN> IO SHOW DEVICE |
The following example is a sample display produced by the 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 NLDRIVERSYS$TTDRIVER, OPERATOR, and NLDRIVER do not have devices associated with them.
1 This manual has been archived but is available in PostScript and DECW$BOOK (Bookreader) formats on the OpenVMS Documentation CD-ROM. A printed book can be ordered through DECdirect (800-354-4825). |
On Alpha systems, displays the permanent exclusion list used in the autoconfiguration of devices.
IO SHOW EXCLUDE
None.
None.
The IO SHOW EXCLUDE command displays the permanent exclusion list on the console. This list is used in the autoconfiguration of devices.
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.
On Alpha systems, displays the current prefix list used in the manufacture of IOGEN Configuration Building Module (ICBM) names.
IO SHOW PREFIX
None.
None.
The IO SHOW PREFIX command displays the current prefix list on the console. This list is used by the IO AUTOCONFIGURE command to build ICBM names.
SYSMAN> IO SHOW PREFIX %SYSMAN-I-IOPREFIX, the current prefix list is: SYS$,PSI$,VME_ |
This example shows the prefixes used by IO AUTOCONFIGURE to build ICBM names.
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 LOADTo see all the status messages on remote nodes for the DCL command, you can use the following SYSMAN command:
SYSMAN> DO LICENSE LOAD
LICENSE LOAD product
product
Specifies the name of the product whose license you want to activate.
/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 Compaq.
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, refer to the OpenVMS License Management Utility Manual.
SYSMAN> LICENSE LOAD FORTRAN |
This example activates the license for Digital Fortran for OpenVMS. Because the license is for a Compaq product, the command does not include the /PRODUCER qualifier.
Deactivates licenses registered in the LICENSE database.Requires CMKRNL, SYSNAM, and SYSPRV privileges.
LICENSE UNLOAD [product]
product
Specifies the name of the product whose license you want to deactivate. If you enter the LICENSE UNLOAD command without specifying a product name, the system deactivates all available registered licenses.
/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 Compaq.
You can use the LICENSE UNLOAD command to deactivate 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, refer to the OpenVMS License Management Utility Manual.
SYSMAN> LICENSE UNLOAD FORTRAN |
This command deactivates the license for DEC Fortran for OpenVMS. Because the license is for a Compaq product, the command does not include the /PRODUCER qualifier.
Bypasses validation of parameter values. SYSMAN parameter validation ensures that the parameters fall within the defined minimum and maximum values specified in the PARAMETERS SET command.
PARAMETERS DISABLE CHECKS
None.
None.
The PARAMETERS DISABLE CHECKS command enables you to override minimum and maximum values established for system parameters. SYSMAN does parameter checks by default. If you attempt to set parameter values outside the allowable limits when checks are enabled, the operating system issues an error message. By disabling checks you can set parameter values regardless of the minimum and maximum limits.
Note
Range checks are enabled by default because Compaq suggests that systems operate within these minimum and maximum values. Setting parameters outside these limits can result in system failures or hangs.
SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/DEFAULT=SYS$SYSTEM/PRIVILEGES=CMEXEC SYSMAN> PARAMETERS SET MAXPROCESSCNT 10 %SMI-E-OUTRANGE, parameter is out of range SYSMAN> PARAMETERS DISABLE CHECKS SYSMAN> PARAMETERS SET MAXPROCESSCNT 10 |
In this example, the initial attempt to set MAXPROCESSCNT below the minimum fails because range checks are enabled. However, once range checks are disabled, the PARAMETERS SET MAXPROCESSCNT command succeeds.
Validates all parameter values to ensure that they fall within the defined minimum and maximum values.Because range checks are enabled by default, use PARAMETERS ENABLE CHECKS after entering a PARAMETERS DISABLE CHECKS command.
PARAMETERS ENABLE CHECKS
None.
None.
SYSMAN> PARAMETERS DISABLE CHECKS SYSMAN> PARAMETERS SET WSMAX 20 SYSMAN> PARAMETERS ENABLE CHECKS SYSMAN> PARAMETERS SET WSMAX 30 %SMI-E-OUTRANGE, parameter is out of range SYSMAN> PARAMETERS SHOW WSMAX Parameter Name Current Default Minimum Maximum Unit Dynamic WSMAX 2000 1024 60 6400 pages |
The PARAMETERS ENABLE CHECKS command in this example shows that when range checking is disabled, the system accepts a working set value (WSMAX) of 20. However, once range checking is enabled with the PARAMETERS ENABLE CHECKS command, the system does not accept a WSMAX below the minimum, which is 60.
Previous | Next | Contents | Index |
privacy and legal statement | ||
6048PRO_068.HTML |