RE: Maintenance Windows

Our system is, usually, in use from 0630 until 1600. At 1600 I (or my boss) take over the system for an end-of-day close. I will usually push program maintenance at that point. But, if it's, say, a report program or something that the users aren't in, I may (if the mood strikes me) push it at any time.

If the maintenance includes any changes to the definition of tables, I'll usually wait until the 1600 window.

We occasionally have other maintenance "issues." For example, our pricing tables are calculated and rebuilt every night, but sometimes there will be changes that need to go in immediately. Fortunately all of our users are inside our four walls, except for retrieval of orders from the field. I can keep collecting the latter while asking the users to sign off; usually takes 3-5 minutes (after the last slacker signs off).

I only recall one [1] "emergency" program fix in the six [6] years I've been here. In that instance order entry (our bread and butter, as with most places) was taken down for about an hour. (Hey, nobody told me about any "special" promotions!).

In summary, our users are pretty happy (except for one ornery lady) to sign off and go home at 1600. If we're having a big day (like last night) I.T. (me and/or my boss) is happy to stay later. I've never worked at a 24x7 shop so I've never had to make plans for that situation.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Boettcher
Sent: Tuesday, March 17, 2009 11: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