Re: Maintenance Windows

[John Jones <chianime@xxxxxxxxx>]

Agreed.  The timing of a change depends on the nature of the change.  As a
rule, after the change management request has been approved, the change is
implemented at the time specified in the change request.  That time will
have been set with an understanding of the impact of the change.

Some changes are made during the production day; these are mostly
enhancements like new reports.

Some are made in "quiet" processing periods when minimal numbers of users
are online.  We're 24x5 but there are quiet times without waiting for the
weekend.

Some require a scheduled outage with user notification.  Even a 5 minute
implementation requires an outage window and notification.  This not only
ensures the users are aware, which heads off calls from that guy who just
happens to be working Saturday at 7AM, but also passes the auditor sniff
test should that particular change record be examined in detail.  These
outages are done during the week for emergencies but are generally saved for
weekends.


On Wed, Mar 18, 2009 at 7:06 AM, Norm Dennis <nhdennis@xxxxxxxxxxx> wrote:

> It really does depend on the types of maintenance.
>
> Some minor changes may be implemented on the fly.
> Some business logic changes may require a Month End or Year End process.
>
> Not to mention a very significant amount of unit testing/integration
> testing/nightmare testing/etc.
>
> A good topic to clear some cobwebs.
>
>
> Norm Dennis
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Boettcher
> Sent: Wednesday, 18 March 2009 1:57 AM
> To: Midrange-L
> Subject: Maintenance Windows
>
> Just a curiosity question,
>
> 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?
>
> Thanks for your response.
>
> Dave B
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.