>then it moves to my application development system (again for a month) and >then into production systems.
I guess it depends on your mainenance philosphy. Baking maintenance for a month can cause issues of currency of software. At the last shop I worked at, I got them down to two weeks per system, because the service provider was notorious for being late on delivery. Then, a month would stretch into two or three, so we'd end up with a SYSPLEX completed just in time for the software to go out of support. Also, they would take 15+ months to put the new release into (and tested on) their 'floor' system. Part of this was because of retrofitting their billing mods into OCO code. They stated that being out of support was not an issue. We, the customer, disagreed. To make a longh story short (too late?), in myu opinion a month per system is too long. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
