HP OpenVMS System Manager's Manual, Volume 1:... |
Managing Peripheral Devices |
|
|
| |
Connecting Devices and Loading Device Drivers
The AUTOCONFIGURE command connects all devices physically attached to the system and loads their device drivers. Using AUTOCONFIGURE saves effort and reduces the possibility of error.
The site-independent startup command procedure, STARTUP.COM, automatically configures devices, because it includes the AUTOCONFIGURE command.
On VAX systems, the following commands in STARTUP.COM perform autoconfiguration:
$ SYSGEN := $SYSGEN $ SYSGEN AUTOCONFIGURE ALLOn Alpha or I64 systems, the following commands in STARTUP.COM perform autoconfiguration:
$ SYSMAN := $SYSMAN $ SYSMAN IO AUTOCONFIGUREDuring autoconfiguration, the CONFIGURE phase of STARTUP.COM creates a detached process to perform the following tasks:
| For this discussion, an HSx device can be an HSC, HSG, or HSJ device. |
Some controllers, such as the HSZ series, allow you to quiesce the SCSI bus and then add or remove a device. When you add a device, you must rerun AUTOCONFIGURE. Note however, that for served storage devices, your system must be running the CONFIGURE process.
In certain cases, you might want to suppress autoconfiguration of devices in system startup. See the following sections for more details.
| Topic | For More Information |
|---|---|
|
Manually connecting
devices and loading drivers1
|
Manually Connecting Devices and Loading Device Drivers (VAX Only)
|
|
Manually connecting
devices and loading drivers2
|
Manually Connecting Devices and Loading Device Drivers (Alpha and I64)
|
|
Suppressing autoconfiguration
|
Suppressing the Autoconfiguration of Devices
|
Manually Connecting Devices and Loading Device
Drivers (VAX Only) ![]()
On VAX systems, whenever possible, use the SYSGEN command
AUTOCONFIGURE to connect standard devices and load device drivers.
However, in some cases, such as connecting non-HP devices,
you cannot use the AUTOCONFIGURE command. In addition, AUTOCONFIGURE
does not connect the following devices or load their device drivers:
In addition to these devices, other devices and drivers might be present that AUTOCONFIGURE does not connect and load. On VAX systems, use the System Generation utility (SYSGEN) to manually connect devices and load device drivers.
For more information, refer to the SYSGEN section of HP OpenVMS System Management Utilities Reference Manual: M--Z and the OpenVMS VAX Device Support Manual . (The latter manual has been archived.)
| Use extreme care when issuing SYSGEN CONNECT and LOAD commands because the system does little error checking. An incorrect vector address or misspelled device name, for example, will damage the I/O database and could cause the system to fail. |
To connect the console storage device on VAX systems, use the following CONNECT command:
$RUN SYS$SYSTEM:SYSGENSYSGEN>CONNECT CONSOLESYSGEN>EXIT
| This command may be different on some platforms. See the VAX installation and upgrade manual for information about the console commands available for your specific platform. |
To connect the network communications logical device on VAX systems, run the appropriate startup files for the particular network protocol. For example, three common net stack startups are:
|
@SYS$STARTUP:TCPIP$STARTUP
|
! TCP/IP Services
|
|
@SYS$STARTUP:NET$STARTUP
|
! DECnet-Plus
|
|
@SYS$STARTUP:STARTNET
|
! DECnet Phase IV
|
For information about connecting virtual terminals and loading their driver, see Managing Virtual Terminals.
For information about configuring virtual terminals in conjunction with TCP/IP Services Telnet, see hp TCP/IP Services for OpenVMS Management.
A HP-supplied driver named SYS$SYSTEM:CONINTERR.EXE permits real-time processes to connect to interrupt vectors for quick response to and special handling of real-time events. The driver is not associated with any specific device type. Refer to the OpenVMS VAX Device Support Manual for more information. (This manual has been archived.)
The commands in the following example autoconfigure the devices attached to a VAX system, and connect the console block storage device and the network software device:
$RUN SYS$SYSTEM:SYSGENSYSGEN>AUTOCONFIGURE ALLSYSGEN>CONNECT CONSOLESYSGEN>EXIT$@SYS$MANAGER:STARTNET
Manually Connecting Devices and Loading Device
Drivers (Alpha and I64) ![]()
On Alpha and I64 systems,
commands for connecting devices and loading their drivers are in
the System Management utility (SYSMAN). All SYSMAN commands that
control and display the I/O configuration on an Alpha and I64 system
contain the prefix IO.
Whenever possible, it is preferable to use the IO AUTOCONFIGURE command to connect standard devices and load device drivers.
IO AUTOCONFIGURE does not connect or load the device driver for the network communications logical device. In addition, other devices and drivers might exist that IO AUTOCONFIGURE does not connect and load.
You can connect unattached devices and devices that have nonstandard names, as well as load device drivers with the SYSMAN commands IO CONNECT and IO LOAD.
For more information, refer to the SYSMAN section of HP OpenVMS System Management Utilities Reference Manual: M--Z and Writing OpenVMS Alpha Device Drivers in C.
| Exercise great care in issuing IO CONNECT and IO LOAD commands. Incorrect use of these commands could cause the system to fail. |
To connect the network communications logical device on Alpha, run the appropriate startup files for the particular network protocol. For example, three common net stack startups are:
|
@SYS$STARTUP:TCPIP$STARTUP
|
! TCP/IP SERVICES
|
|
@SYS$STARTUP:NET$STARTUP
|
! DECnet-Plus
|
|
@SYS$STARTUP:STARTNET
|
! DECnet Phase IV
|
The commands in the following example autoconfigure the devices physically attached to the Alpha or I64 system, load their drivers, and connect the network software device:
Virtual TerminalsSYSMAN>IO AUTOCONFIGURE ALLSYSMAN>EXIT$@SYS$MANAGER:STARTNET
For information about connecting virtual terminals and loading their driver, see Managing Virtual Terminals.
For information about configuring virtual terminals in conjunction with TCP/IP Services Telnet, see hp TCP/IP Services for OpenVMS Management.
Suppressing the Autoconfiguration of Devices ![]()
Autoconfiguration
of devices saves effort and reduces the possibility of error. However,
you might want to suppress autoconfiguration for the following reasons:
To suppress autoconfiguration, add the following command as the last line of SYS$MANAGER:SYCONFIG.COM:
$ STARTUP$AUTOCONFIGURE_ALL == 0
1 VAX specific
2 Alpha and I64 specific
( Number takes you back )
|
|