I've done the same thing. In my case, it was TSOE TRANSMIT, which at the time used VIO for the temporary data set created for transmission purposes. That can be changed in PARMLIB IKJTSOxx TRANSREC to something other than VIO. VIO really makes no sense in a modern mainframe environment but can still cause mischief if not throttled back.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, February 23, 2018 7:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Count with no Data and no Key ? (CKD internals again) On Fri, 23 Feb 2018 14:49:05 +0000, Christopher Y. Blaicher <cblaic...@syncsort.com> wrote: > >The access methods detect the key=0, count=0 records and process them as EOF, >which is how they signify the end of a PDS member. Every member has an EOF >record with the rare exception of a member that ends at the end of the track >on the last track of a data set. ... > VIO has its own surprising rules. I once (circa XA) caused paging space exhaustion by reading an uninitialized data set allocated as UNIT=VIO,SPACE=(0,large) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
