RE: Test Development System Survey

At both my current and a former employer, we started with everything on
the same system but migrated to having dev on a separate box than prod.

What we currently do is run dev on our business continuity system.
Which means we've an 830 that rarely sees more than 5 concurrent users.
^_^  In a BC situation, we can have the developers work odd hours or
just halt development work temporarily if what they're doing would
impact production.

If you don't maintain your own BC environment and you think the
developer workload is impacting production, I'd recommend LPARing your
main system to give the developers a slice of the system that won't
interfere with production workloads.

It should also be pointed out that many times developers have a fair
number of priviledges on the system and that without a pretty tight
security model, they could have access to production data.  Which could
be a problem during an audit.  Our developers have *USER/nothing special
on the production box since they use an app for time entry but otherwise
they cannot do anything on the production system.

- John

-----Original Message-----
From: Condon, Mike [mailto:M1C@xxxxxxxxxxxxxxxxx] 
Sent: Thursday, July 17, 2003 8:28 AM
To: 'Midrange Systems Technical Discussion'
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.

This e-mail is for the use of the intended recipient(s) only.  If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not use, disclose 
or distribute this e-mail without the author's prior permission.  We have taken 
precautions to minimize the risk of transmitting software viruses, but we 
advise you to carry out your own virus checks on any attachment to this 
message.  We cannot accept liability for any loss or damage caused by software 
viruses.