Which is why we turn off fast write. Waits for the record to be physically written before the next record is sent.
On Thu, Dec 13, 2012 at 11:37 AM, Ron Hawkins <[email protected]> wrote: > Mike, > > Have you confirmed with each DASD vendor that the contents of the channel > command generated by TRKFMT ERASDATA are actually passed to the disk drive > for drive types, parity schemes and volume formats? > > To paraphrase your description, TRKFMT writes fulltrack records to cache > then an empty track record to cache. The empty track record is all that > makes it to the physical disk drives. > > In the case of Hitachi Dynamic Pools (HDP), if you erase a whole 38MB chunk > like this there is nothing destaged and the chunk goes back in the free > pool. > > Ron -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
