|
You're a furniture company, not some silly bank that requires the source to be on the production system. Why haven't you transferred your tools license to your testing machine? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 07/17/2003 08:39 AM Please respond to Midrange Systems Technical Discussion To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: RE: Test Development System Survey We have had our development and production environments on the same system for quite some time and it is the pits. Testing modifications requires taking the time to ensure any program executed during the test does not update production data and that any output created does not get printed on a production printer. In my opinion, this decreases programmer productivity by a significant amount. Then there is the occasional mistake when a test job does update production data and the necessary correction thereof. That hasn't happened in quite some time, though. We do have a test system now, but it's on a separate machine from our development environment and has no development tools so it's use is limited. I can't say for certain if or how development activity impacts the overall performance of the system, but I doubt the impact is positive. And yes, I do wish I had a separate system for development and testing with all the necessary tools. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> We are currently using our AS400 production box for development as well (the test/production systems are separated by logins/environment variables). How many of you all also combine both on one machine, and has this caused performance problems for you? Or do you use a test machine for development specifically because of this (or wish you had one)? <clip> _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.