Example 1: //EX1 DD UNIT=VIO //EX2 DD DSNAME=&&TEMPDS,UNIT=SYSDA //EX3 DD DSNAME=&&TEMPDS(MEM1),UNIT=VIRT3 //EX4 DD DSNAME=&&MYDS,UNIT=VIO,SPACE=(360,(5,30)), // DISP=(,PASS),DCB=(RECFM=FB,LRECL=80,BLKSIZE=360)
In these examples, the system assigned during system initialization the group names VIO, SYSDA, and VIRT3 as eligible for VIO processing. "Confidentially doc, I am the wabbit." Bugs Bunny Sent with Proton Mail secure email. On Monday, August 4th, 2025 at 9:28 AM, Jay Maynard <000005997213d6c2-dmarc-requ...@listserv.ua.edu> wrote: > I had thought that having UNIT=VIO was required by various parts of z/OS, > stretching back to the very beginning. Every shop I've ever worked in has > had it as a matter of course. > > Every shop, that is, until my current one. Instead, it has UNIT=VIODA for > the same purpose. > > It has now bitten us i nthe butt, and I've put in a request to have out > systems contractor define UNIT=VIO as a duplicate of UNIT=VIODA. > > Has anyone else ever run into a shop that didn't have UNIT=VIO? > -- > Jay Maynard > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN