
Channel end has been previously accepted and the operation is now complete,
but device end has not been presented to the channel.
Busy status has previously been sent and the logical volume is now not busy.
The resulting device end has not been presented to the channel.
The logical volume changed states, and that status has not been presented to
the channel. See “State-Change Interruption.”
Address Associated with Pending Status
All status conditions are associated with a specific logical volume address.
State-Change Status
State-Change Interruption
A state-change interruption is the combination of three device status bits: attention,
device end, and unit exception. As with all status, busy can also be included.
Note:
Unit check may also be included if the logical volume has previously
received a Perform Subsystem Function command with a Set Special
Intercept Condition order.
The term
state-change interruption
is used in this manual for the former term
pack-change interruption
. A state-change interruption occurs for a state change in
the subsystem or the logical volume. The following conditions cause a
state-change interruption:
Logical volume goes from not-ready to the ready state.
Long busy condition no longer exists for the logical volume.
Set System Characteristics order changes stored values for a path group. This
state change is issued only to channels in the path group that changed. See
"Set System Characteristics - PSF Order Code x'1D'" on page 4-129.
State-change interruptions are sent to each LPAR.
Note:
For a state-change interruption, a host program can issue the following
CCWs to determine the current status of the subsystem:
Sense ID
Read Device Characteristics
Read Configuration Data
Sense Subsystem Status
Effect of Subsystem and Device State on Status Presented to
Command
The status presented to commands depends on:
The particular command code.
The state of the subsystem.
The state of the device addressed.
Most channel commands are concerned with data transfer control to cause data to
be moved to or from a disk track (or disk track image for a cache hit). Examples of
these commands are Seek, Set Sector, Read Data, and Write Key & Data. Data
transfer command chains are issued by application programs or by data
management programs acting on the behalf of the application. In almost all cases
these CCW chains have Define Extent or Set File Mask as the first command of the
Chapter 2. Processing Commands and Presenting Status
2-5
Содержание Multiprise 3000
Страница 1: ...S 390 Multiprise 3000 Enterprise Server R IBM Internal Disk Subsystem Reference Guide SA22 1025 00 ...
Страница 2: ......
Страница 3: ...S 390 IBM Internal Disk Subsystem Reference Guide SA22 1025 00 ...
Страница 32: ...2 12 Internal Disk Subsystem Reference Guide ...
Страница 38: ...3 6 Internal Disk Subsystem Reference Guide ...
Страница 182: ...4 144 Internal Disk Subsystem Reference Guide ...
Страница 198: ...5 16 Internal Disk Subsystem Reference Guide ...
Страница 214: ...6 16 Internal Disk Subsystem Reference Guide ...
Страница 234: ...A 10 Internal Disk Subsystem Reference Guide ...
Страница 238: ...B 4 Internal Disk Subsystem Reference Guide ...
Страница 243: ...4 lease the Code or any copy of it Appendix C Warranties C 5 ...
Страница 244: ...C 6 Internal Disk Subsystem Reference Guide ...
Страница 248: ...D 4 Internal Disk Subsystem Reference Guide ...
Страница 254: ...X 6 Internal Disk Subsystem Reference Guide ...
Страница 263: ......
Страница 264: ...IBM Printed in the United States of America on recycled paper containing 10 recovered post consumer fiber SA22 1 25 ...