My recommendation was specifically for z/OS; I don't know how z/VSE handles multiple READs, and I would expect most CMS I/O to be native CMS, BFS or SFS.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Tuesday, March 2, 2021 11:57 AM To: [email protected] Subject: Re: Large block interface for VB On Tue, 2 Mar 2021 16:35:46 +0000, Seymour J Metz wrote: >For best performance, NCP should match the number of DECBs you allocate and >you should do a READ on each of them. If real storage is an issue, reduce that >number appropriately. When you hit EOF (EODAD is entered), stop issuing READ. > (Decades old experience:) Of course, if the programmer is coding for overlapped I/O, the access method may be unable to detect EOF before the program has issued several more READs. MVS BSAM somehow handles this correctly: READs beyond EOF just don't happen. CMS/XA OS emulation was terrible. READs were synchronous: control did not return to the caller until channel/device end and DECB was posted. Additional READs intended to be asynchronous read garbage data or got I/O errors. I used the same code on both OSes. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
