Alternate paths to disk storage
Sometimes when a program requests storage I/O, the pathway between the processor complex and disk storage is found to be busy because of an earlier I/O request on the same storage director (SD). When there is only 1 path defined through a storage director between the processor complex and disk storage, the program I/O request must wait for the earlier request to complete. When there is more than one path from a processor complex to disk storage, a program requesting storage I/O does not need to wait for an earlier request to complete. An alternate pathway can be selected automatically.
Pathways between the processor complex and disk storage are defined by the I/O configuration data set (IOCDS) for each installed processor. IOCDSs are created by an IBM-supplied I/O configuration program (IOCP) and are modified whenever there are any alterations required in the installed I/O configuration. For example, adding a new DASD controller would involve an addition to the IOCDS as part of the installation. The IOCP required for creating and maintaining IOCDSs is not a part of the z/TPF-supplied product. There is a separate IOCP associated with each IBM® processor. For information about devices available on the System/370 processor, see IBM System/370 Input/Output Configurator.
The following are considerations that relate specifically to the use of alternate pathways to disk storage in z/TPF systems:
The symbolic device address (SDA), which uniquely identifies an I/O device, will be either 370-like with 3 hexadecimal digits for communications, tape devices, and so on, or may be 4 hexadecimal digits for MPIF and DASD devices. In order to simplify the construction of symbolic device addresses, the channel path identifier (CHPID), control unit (CU), and device number should be used to form the SDA. For example, an SDA for device 0 on CU C accessible from CHPID 4, would be 4C0.
For single processor, non-loosely coupled systems with no DASD RPQs, each DASD has 1 subchannel defined. Multiple paths to a DASD are reflected in the subchannel information block (SCHIB) associated with that DASD. The IOCDS for this configuration is similar to that required by z/OS® and VM. In this configuration, the channel redrive RPQ is optional.
When multiple paths are associated with a DASD, the lowest numbered CHPID should be used to form the SDA.
All DASD control units in a loosely coupled configuration require the concurrency filter lock facility (CFLF). Additionally, the channel redrive RPQ is required on the processors. CFLF can perform error recovery on another channel; therefore, the static switch RPQ is not used. However, CFLF still uses the channel redrive to prevent the CPU from becoming I/O bound.
Parent topic: Database support
Previous topic: Database device addressing
Next topic: Permanent record area
Alternate paths to disk storageSometimes when a program requests storage I/O, the pathway between the processor complex and disk storage is found to be busy because of an earlier I/O request on the same storage director (SD). When there is only 1 path defined through a storage director between the processor complex and disk storage, the program I/O request must wait for the earlier request to complete. When there is more than one path from a processor complex to disk storage, a program requesting storage I/O does not need to wait for an earlier request to complete. An alternate pathway can be selected automatically.Pathways between the processor complex and disk storage are defined by the I/O configuration data set (IOCDS) for each installed processor. IOCDSs are created by an IBM-supplied I/O configuration program (IOCP) and are modified whenever there are any alterations required in the installed I/O configuration. For example, adding a new DASD controller would involve an addition to the IOCDS as part of the installation. The IOCP required for creating and maintaining IOCDSs is not a part of the z/TPF-supplied product. There is a separate IOCP associated with each IBM® processor. For information about devices available on the System/370 processor, see IBM System/370 Input/Output Configurator.The following are considerations that relate specifically to the use of alternate pathways to disk storage in z/TPF systems:The symbolic device address (SDA), which uniquely identifies an I/O device, will be either 370-like with 3 hexadecimal digits for communications, tape devices, and so on, or may be 4 hexadecimal digits for MPIF and DASD devices. In order to simplify the construction of symbolic device addresses, the channel path identifier (CHPID), control unit (CU), and device number should be used to form the SDA. For example, an SDA for device 0 on CU C accessible from CHPID 4, would be 4C0.For single processor, non-loosely coupled systems with no DASD RPQs, each DASD has 1 subchannel defined. Multiple paths to a DASD are reflected in the subchannel information block (SCHIB) associated with that DASD. The IOCDS for this configuration is similar to that required by z/OS® and VM. In this configuration, the channel redrive RPQ is optional.When multiple paths are associated with a DASD, the lowest numbered CHPID should be used to form the SDA.All DASD control units in a loosely coupled configuration require the concurrency filter lock facility (CFLF). Additionally, the channel redrive RPQ is required on the processors. CFLF can perform error recovery on another channel; therefore, the static switch RPQ is not used. However, CFLF still uses the channel redrive to prevent the CPU from becoming I/O bound.Parent topic: Database supportPrevious topic: Database device addressingNext topic: Permanent record area
การแปล กรุณารอสักครู่..