In my opinion, zAAPs, and zIIPS and zFLS and all of the newfangled
processor type were created solely by IBM hardware gurus who could
not get IBM Marketing to reduce the prices of their CPs and the
software running on their CPs, and these hardware types knew that
if marketing wasn't going to reduce the price of z/SYSTEM hardware,
that they'd have no jobs in the future, and they invented these new
engines, and all of the software scheduling, monitoring, managing,
etc. so they could keep their jobs creating z/SYSTEM hardware.
And of course, now, we users have to learn how to introduce these new
engines, how to set parameters (e.g., this thread), how to select what
work can be used on them, how to recover and account their costs, i.e., we have
to spend our time (our money) on our people costs,
which means our companies have to pay a lot more people money to save any
hardware money on these cheaper engines.
I can see NO virtue in these processors as technical designs, as the
added software decision logic to decide on what to run where is unquestionably
an unnecessary overhead, and technically we'd be far
better served, with less overhead and no new people training costs, had IBM
marketing instead reduced the prices of their CPs and
associated CP-driven software costs.
That the hardware guys had to invent these devices so they could be
priced cheaper - now those guys do deserve great credit for solving
a problem they shouldn't have had to solve - and for making it possible
for future zSYSTEMS to exist in the artificial pricing world of IBM.
Barry Merrill
Herbert W. Barry Merrill, PhD
President-Programmer
Merrill Consultants
MXG Software
10717 Cromwell Drive
Dallas, TX 75229
www.mxg.com
P.S. My opinion has been affirmed by many leading IBM Technicians,
privately.
----------------------------------------------------------------------
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
