In <[EMAIL PROTECTED]>, on 11/26/2005
at 08:58 PM, Mohamed Juma <[EMAIL PROTECTED]> said:
>1. How you put your policy to upgrade the CPU or to go
>to new bigger processor, is it just when you suffer
>from 100% CPU usage or what are the criteria used for
>that?
Is the work getting done in accordance with your SLA? Do you project
that the work will continue getting done for the forseeable future? If
yes, you don't need a new CPU, even if you see long periods of 100%
CPU use. If it looks the the work won't get done in accordance with
your SLA next quarter, then you need to upgrade even if you never see
100% CPU utilization.
What's your lead time for an upgrade? You need to order it early
enough so that it's there, installed and in production before the
balloon goes up. Planning.
What's the cost of not meeting your SLA?
>2. Regarding the operating system: when you decide to
>go to higher version?
Well before the old one goes out of service; much earlier if you need
new functionality. How disruptive is an IPL. Have you taken regression
checking into account?
>are you puting maintenance every 6 months as example
I used to do it much more often, but let service age for 90 days. You
need to decide what balance of PUT, RSU and HIPER service makes sense
for your installation.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
