-------------------------<snip>---------------------
Sorry for a newbie to jump in here...
But I have a question: why IBM doesn't increase the clock of mainframe CPU?
There is no need or there are some technical problems?
I'm now working at one customer's site and every day's afternoon is a
terrible time for all developers working on their development system: we
just cannot use TSO/ISPF! You must wait 4 or 5 seconds for a response
and sometimes you just hang there. The cause is that most teams will do
their batch tests at that time thus eating all of CPU cycles. I guess
they might need a more powerful CPU? (This situation has last for three
months since I came here)
------------------------<unsnip>--------------------
It's not as simple as that; other components have to be able to work
with the timing adjustment and may not be capable of doing so. Why?
Various reasons that can include design limitations and component
limitations. Even the lengths of PC board connections can enter into the
equation,not to mention the cables that connect PC boards. And
reliability might suffer, as we once learned with a S370/158 AP. One
tri-lead that was too long by 1" lead to machine checks galore.
Customers were VERY UNHAPPY with all the unplanned outages!
The situation you describe might be an ideal oppurtunity to show off
your tuning expertise!
----------------------------------------------------------------------
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
