|
I remember, years ago, on the AS/400 when a controller really got down on
one of our developers because his compile was bringing the system to it's
knees.
Nowadays we have a separate development box. While lpar might be a valid
solution, the risk of (using a single non lpared box) not having
everything set up just right and accidentally updating production data is
scary. Also, testing new versions of the OS, ptf's, etc. Yeah, I like
the separate box. When we had 21 400's the development box had more disk
than the two largest combined. It was easier/faster to get the job done
that way than to show off our testosterone by creating questionable data
subsets for testing.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
"Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/17/2003 08:27 AM
Please respond to Midrange Systems Technical Discussion
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
cc:
Fax to:
Subject: Test Development System Survey
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)?
_______________________________________________
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.