We found that HyperPAV made a major improvement to the run time for one of our
large CMS applications.
Make sure you're current on maintenance. We've had a few problems with DASD
replication that might have been avoided if we had all of the Hyperswap and
HyperPAV-related PTF's on. We have most of them on now.
Dennis O'Brien
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your unit."
-- August 1993 issue of PS Magazine, preventive maintenance magazine of the US
Army
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Marcy Cortes
Sent: Saturday, September 18, 2010 21:18
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] DEFINE HYPERPAV requirement
I'd like to hear some hyperpav experiences.
How are they working for you and under what conditions are they best used?
We haven't experimented yet because of other i/o tricks going on here.
Marcy
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of O'Brien, Dennis L
Sent: Saturday, September 18, 2010 12:43 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: [IBMVM] DEFINE HYPERPAV requirement
I prefer to have all device-related statements for guests in the directory,
even those that are only defined by commands, such as HyperPAV aliases. I'm
running into the restriction that the combined length of all COMMAND statements
cannot exceed 3071 characters. Currently, each HyperPAV alias must be defined
with a separate command, e.g.
COMMAND DEFINE HYPERPAV 1380 BASE 1300
COMMAND DEFINE HYPERPAV 1381 BASE 1300
.
.
COMMAND DEFINE HYPERPAV 139F BASE 1300
I know I can squeeze in a few more statements by using the minimum
abbreviations, e.g. CMD DEF HYPERPAV 1380 BASE 1300, but that doesn't really
solve the problem. I also don't want to move the code to PROFILE EXEC, because
then it's not obvious to someone looking at the directory that there are more
devices defined elsewhere. What I'd really like is support for ranges on
DEFINE HYPERPAVALIAS. That way I could replace 32 statements for individual
aliases with one COMMAND DEFINE HYPERPAV 1380-139F BASE 1300.
Am I the only one with this problem? Would this be a good candidate for a WAVV
requirement?
Dennis O'Brien
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your unit."
-- August 1993 issue of PS Magazine, preventive maintenance magazine of the US
Army
