Re: Maintenance Windows

[Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx]

gee...i wonder if David knows of a change management package that i could 
use...hmm??? <vbg>

Thanks,
Tommy Holden



From:
David Gibbs <david@xxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
03/17/2009 12:22 PM
Subject:
Re: Maintenance Windows
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Dave Boettcher wrote:
> What is your practice for maintenance of existing programs? 
> Is there a set time each week that users know the system will be down 
for maintenance?
> Or can maintenance be done at any time?

Strictly speaking, I don't work on a 'production system' ... but I have in 
the past.

IMO, it depends on the impact and urgency of the change.  If the impact is 
light and urgency high, I would roll the change out live.  If the impact 
is high or the urgency low, then the change would be delayed or rolled out 
in a managed way.

High impact changes would be anything that the user will immediately 
notice or any database change.

A change control system makes rolling out changes of any impact level much 
easier <of course/>.   Wish I had one back then.

david
(who works for MKS, a change control vendor, in addition to running these 
lists)