
Write Track Data
Hex Code
Data Address
Count
A5
The main storage location of the first data byte
to be written.
Number of data bytes to be written.
Description:
The Write Track Data command transfers multiple records from the
channel to a track.
Write Track Data is valid only in the domain of a Locate Record Extended
command that specifies an Update Write Trackset operation code. If Write Track
Data is received outside the domain of a Locate Record, execution is terminated
with status that includes unit check (Command Reject, format 0, message 2,
Invalid Command Sequence).
If Write Track Data was not immediately preceded by a Locate Record Extended
command with an operation that allows Write Track Data or another Write Track
Data command, execution is terminated with status that includes unit check
(Command Reject, format 0, message 2, Invalid Command Sequence).
The first Write Track Data command in a Locate Record Extended domain orients
to the beginning of the first data area (excluding R0) following the orientation
established by the Locate Record Extended command and transfers each data area
on the track until End-of-Track is reached. If End-of-Track is detected before a data
area is found, the command is terminated with status that includes unit check (No
Record Found).
The second and subsequent Write Track Data commands in a domain attempt to
advance to the next track, orient to first data area (excluding R0) transfer each data
area on the track until End-of-Track is reached. If no user data area is detected on
the next track, execution is terminated with status that includes unit check (No
Record Found).
The “next” track is the track corresponding to the next ‘1’ bit in the Extended
Parameter.
If the Transfer Length Factor (or Blocksize) value is not equal to the value in the
data length field in the count area of any record being updated, the record is not
updated and the operation is terminated with status that includes unit check (Invalid
Track Format).
If the channel truncates data transfer due to exhaustion of the CCW byte count, the
storage director will do one of the following:
If the truncation occurs in the middle of a data area then pad to the end of that
data area with zeros and then present Channel End and Device End status.
If the truncation occurs in between two data areas then present Channel End
and Device End status.
No exception condition is reported as the result of the truncation of data transfer by
the channel. If an exception condition is detected after the channel has truncated
data transfer, Unit Check status is included with Channel End and Device End.
4-102
Internal Disk Subsystem Reference Guide
Содержание 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 ...