In
<77142d37c0c3c34da0d7b1da7d7ca34333375...@nwt-s-mbx1.rocketsoftware.com>,
on 03/20/2012
at 10:12 PM, Bill Fairchild <bfairch...@rocketsoftware.com> said:
>What exactly does "MB/second mean when referring to how much data
>can be copied from a DASD to a tape?
It normally refers to the data that are actually copied, not to data
that are skipped.
>What if there is nothing written on the tracks,
Then that, like short blocks, may slow you down.
>If all they have written on them is R0, am I still transferring
>data at the rate of 100MB/sec?
The Devil is in the details. Are you copying the R0's? If so, those
data count. If not, not. In either case processing large numbers of
tracks with R0 only will make it harder to maintain 100 MB/s.
>If each track were half full, would my effective data transfer rate
>be only 50 MB/sec?
How many half track are you writing to tape per second? With your
roundoff, 4,000 half tracks per second and 2,000 full tracks per
second are both 100 MB/s.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
