The "all 16 extents" applies to VIOMAXSIZE calculation, by the way.
Cheers, Martin Sent from my iPad > On 20 May 2016, at 17:26, Paul Gilmartin <[email protected]> wrote: > >> On 2016-05-19, at 15:04, Longabaugh, Robert E wrote: >> >> ... Also VIO would get all 16 extents at once, so saying TRK(1,1) was not better than saying TRK(16). When a job did the VIO allocation, it got the page slots. >> > Perhaps not quite. My experience is that it gets the page slot as each page > is accessed. Thereby hangs a tale. > > I had a job that passed a temp DS I had overallocated as CYL(0,large); primary > 0 to circumvent the then behavior of reading residual data if the DS was never > written; EODAD was entered at end-of-extent. > > Then I tried UNIT=VIO. Worked fine and only page slots actually written were > allocated. Until once when the first step didn't open it for output. In the > second step, VIO read every slot looking for EOF. Page storage exhaused. > For everybody. Ouch! > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN >Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
