The original job asked for only 10 tracks. I reran the job for a 50-cylinder
data set. This time the allocation went to real DASD. In my 20 years at SCE, I
don't recall anyone lobbying for a higher VIO limit.
IGD101I SMS ALLOCATED TO DDNAME (ALLOCVIO)
DSN (SYS16129.T090644.RA000.ALLOCVIO.R0104602 )
STORCLAS (STANDARD) MGMTCLAS ( ) DATACLAS (STANDARD)
VOL SER NOS= ATMP03
.
.
.
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 Ed Jaffe
Sent: Friday, May 06, 2016 5:18 PM
To: [email protected]
Subject: (External):Re: Using TYPE=MEMORY (or VIO?)
On 5/6/2016 1:44 PM, Jesse 1 Robinson wrote:
> STORGRP SG VIO VIO
> NAME TYPE MAXSIZE UNIT
> --(2)--- -------(3)------ --(4)-- (5)-
> VIODA VIO 13500 3390
>
> Compared with Ed, we have a very low limit indeed.
VIO MaxSize is expressed in K-bytes. Assuming the standard twelve 4K blocks per
track, 13500 K is less than 19 cyls. I'm gonna go out on a limb here and
suggest this number hasn't been revisited since SMS first started handling VIO
in ~1992 when MVS could still IPL in 16M of real.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
