John Kim wrote:
The following lessens my confidence;
1) Why default is off, even if it's good enough to be a performance
escalation
That's SOP for new, optional function delivered for z/OS. Such options
almost always default to NO or OFF or whatever means "same as before".
After one or more releases, they often change to YES or ON or "the new
way". In this case, a Health Check "nags" at you until you enable
Hiperdispatching or shut down the check.
2) The majority of installations that bring in a z10 are not turning on
I did not know that. Where did you hear that? Cheryl's newsletter?
Another source?
3) Large installations are very afraid to "rock the boat". Anything
can affect Production workload is guilty until proven innocent.
4) Applying two dozens of APARs is somewhat risky
How do these truisms qualify as a "con" for HiperDispatch?
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
