>[snip] Expanded storage is one of those things that, for a combination of
>technical and marketing reasons, had its day in the sun and has gone, while
>VIO continues.
It's back, just called "Flash Express" these days. It's used for paging, and
for some other things (or things to come) just
arna Walle):
https://developer.ibm.com/tv/category/mpt/
From: Jesse 1 Robinson <jesse1.robin...@sce.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 11/05/2016 17:05
Subject: Re: Whither VIO?
Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Mea
On Wed, 11 May 2016 13:09:45 -0400, Tony Harminc wrote:
>
>The biggest reason to use VIO rather than the various alternatives
>mentioned is that it is compatible. An existing application need know
>nothing about it, and can be offered improved performance with no code
>changes. In these days of
On 11 May 2016 at 10:07, Martin Packer wrote:
> The nasty answer to "what happened to VIO?" is "nothing". :-) :-(
>
> Seriously, it remains as before but implemented in central storage rather
> than expanded.
VIO long predates the existence of expanded storage. It was
On 11 May 2016 at 12:05, Jesse 1 Robinson wrote:
> One question I have. In a previous life, we defined VIO (I believe) to device
> 3314 even though we had none left on the floor. The device type was still
> valid in IOGEN at that time, and I was told that device
rogram Co-Manager
>323-715-0595 Mobile
>626-302-7535 Office
>robin...@sce.com
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of David Betten
>Sent: Wednesday, May 11, 2016 8:41 AM
>To: IBM-MAIN@LISTSERV
: (External):Re: Whither VIO?
When I was in DFSORT, I always recommended not using VIO for sort work data
sets. We felt it was better to let DFSORT manage the use of storage for
intermediate work space via Hiperspace, Memory Object or Dataspace. One
advantage was that DFSORT has controls over the total
.UA.EDU
> Date: 05/11/2016 11:12 AM
> Subject: Re: Whither VIO?
> Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
>
> I said in another thread that VIO was one of the worse DIM exploiters for
> CPU usage - in the Orange "Coffee Table" book of DIM
rno...@klm.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 11/05/2016 15:32
Subject:Re: Whither VIO?
Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
I heard rumors that VIO is that CPU expensive and that I/O is that fast
nowadays, that it is VIO is not wor
On 5/11/2016 7:31 AM, Vernooij, CP (ITOPT1) - KLM wrote:
I heard rumors that VIO is that CPU expensive and that I/O is that fast
nowadays, that it is VIO is not worth the extra CPU anymore.
We use VIO for (nearly) ALL temporary data sets. (VIO MAXSIZE is set to
the highest supported value of
] On Behalf
Of Martin Packer
Sent: 11 May, 2016 16:08
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Whither VIO?
The nasty answer to "what happened to VIO?" is "nothing". :-) :-(
Seriously, it remains as before but implemented in central storage rather
than expanded.
With the improved
Series (With Marna Walle):
https://developer.ibm.com/tv/category/mpt/
From: Lizette Koehler <stars...@mindspring.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 11/05/2016 14:55
Subject:Re: Whither VIO?
Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
My guess would be:
DASD is faster
Virtual Tape is faster
Central Memory is plentiful (for some shops)
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jerry Callen
> Sent: Wednesday, May 11, 2016 6:51 AM
> To:
13 matches
Mail list logo