I misspoke. VIO goes to virtual storage, which is central as available and eventually to AUX if need be. Like John, we probably have some ACS limits on VIO that I'm not privy to. For sure 'UNIT=VIO' gets a JCL error here because that esoteric is not defined in the IODF.
I don't do C, so I'm not familiar with TYPE=MEMORY. Is that translated to VIO in z/OS? . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Martin Packer Sent: Friday, May 06, 2016 10:14 AM To: [email protected] Subject: (External):Re: Using TYPE=MEMORY (or VIO?) Paging space or memory? VIO can go to Central Storage - if you have some. I suspect you don't. :-( Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Cloud & Systems Performance, IBM +44-7802-245-584 email: [email protected] Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker Podcast Series (With Marna Walle): https://developer.ibm.com/tv/category/mpt/ From: John McKown <[email protected]> To: [email protected] Date: 06/05/2016 18:05 Subject: Re: Using TYPE=MEMORY (or VIO?) Sent by: IBM Mainframe Discussion List <[email protected]> On Fri, May 6, 2016 at 12:00 PM, Jesse 1 Robinson <[email protected]> wrote: > After stating flatly that we do not support VIO, I ran a test and learned > otherwise. For sure we do not support the esoteric name 'VIO'. In my > previous shop IIRC it was implemented as 'SYSVIO'. I don't know why > the name change, but I would guess it's to avoid canned jobs from > gobbling up > paging space, although nothing would prevent someone from changing 'VIO' to > a supported name. > We avoid gobbling up page space by having the ACS routines allow something with UNIT=VIO to actually be VIO only if the &MAXSIZE is not too large. But we're a small shop & shrinking. Most people here just use UNIT=SYSDA and we set the ACS routines up to "do the right thing" based on the data set criteria. It's easier on users who just don't want to be bothered. > > I see this in my test job, which seems to indicate that the data set > really went to VIO: > > IGD101I SMS ALLOCATED TO DDNAME (ALLOCVIO) > DSN (SYS16127.T095147.RA000.ALLOCVIO.R0108161 ) > STORCLAS (STANDARD) MGMTCLAS ( ) DATACLAS (STANDARD) > VOL SER NOS= VIO > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Paul Gilmartin > Sent: Friday, May 06, 2016 9:25 AM > To: [email protected] > Subject: (External):Re: Using TYPE=MEMORY (or VIO?) > > On 2016-05-06, at 09:35, Jesse 1 Robinson wrote: > > > > ... , be aware that some customers (like us) did away with VIO a > > long > time ago. > > > Did they tend to preserve their VIO esoteric name? > > Could you even count on the same esoteric name's existing even in all > shops supporting VIO? > > I sometimes distribute JCL using a JCL symbol for VIO. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > -- The unfacts, did we have them, are too imprecisely few to warrant our certitude. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
