RE: Request for assistance

Booth
As Doug suggests LPAR is an excellent solution.
You still can retain box(System) autonomy and gain all the benies, which should get dramatical better in the not to distant future. Not that it is not good now.

Glenn
__________________________________
Glenn Ericson,
IBM Certified Specialist
Phoenix Consulting LLC
East Elmhurst, NY USA
Phone 718 898 9805 Fax 718 446 1150
mailto:Glenn-Ericson@att.net
___________________________________


At 12:31 AM 06/23/2000 GMT, booth@martinvt.com wrote:
>One should not discount the freedom a second box gives a programming team.
> Removing the fear that a program or a new experimental process could
>destroy real data or suck in the sides of the box has a great benefit of
>empowerment for the development team. If they want to put up their own
>website and try out FTP and perhaps try a few RPG-cgi pages, etc. they
>will do it without fear that the network administrator is going to go
>ballistic. It also allows dial-in or other remote log-in so they can have
>time to play on a rainy day if they so choose.
>_______________________
>Booth Martin
>Booth@MartinVT.com
>http://www.MartinVT.com
>_______________________
>
>
>
>
>"Dave Miller" <dlmiller@jquint.com>
>Sent by: owner-midrange-l@midrange.com
>06/22/2000 04:51 PM
>Please respond to MIDRANGE-L
>
>
> To: <MIDRANGE-L@midrange.com>
> cc:
> Subject: RE: Request for assistance
>
>It has been my experience in the past that having developers on a separate
>system removes the problems of development from impacting the production
>users.
>
>Most systems are not secured properly from the types of things that
>developers do. Simple things like on-line compiles to more complex things
>like I wonder what happens when I try this. Also, with separate systems
>(and separate test(QA) areas) it is easier to perform the kinds of testing
>needed to really verify that things like release upgrades go smoothly.
>
>Take the time to reflect on what it would cost your company to incur maybe
>5
>hours of downtime because a developer or software upgrade brought the
>system
>down.
>
>Could you go a day or two without order entry, or billing, or shipping, or
>customer inquiries? Maybe, but think of the negative impact on everyone
>not
>only customers but employees who loose faith in the systems they are
>supposed to use to do their jobs.
>
>Having 2 systems, 1 for production and 1 for development is like buying
>insurance, you hate like hell to send that check to the insurance company
>each month but you are really glad you did when your house burns down or
>you
>have and accident in your car.
>
>Dave Miller
>J. Quint & Associates
>Phone(310) 636-1163 Fax (310) 636-1162
>email: dlmiller@jquint.com
>
>
>> -----Original Message-----
>> From: owner-midrange-l@midrange.com
>> [mailto:owner-midrange-l@midrange.com]On Behalf Of alucas@us.ibm.com
>> Sent: Thursday, June 22, 2000 12:06 PM
>> To: MIDRANGE-L@midrange.com
>> Subject: Request for assistance
>>
>>
>>
>>
>> I am working with an AS/400 customer that has a 530 for production and a
>> 510 for development. They have 2500 employees, approx $600 million in
>> sals; 3 plant locations that access the production box directly; 900 PCs
>> accessing the AS/400; 500-600 signons; 10 sales offices connected and 5
>> shipping depots.
>>
>> Question: Are there companies of simliar size that are using a
>> development
>> box totally separate from the main AS/400 production system? If so
>why?
>> If not why?
>>
>> This customer would like to talk with customers on both sides of the
>> questions.
>>
>> If you have advice and someone we can talk with, please email me at
>> alucas@us.ibm.com. They must decide to go to the 700 or 800 series with
>> one or two boxes ASAP.
>>
>> Thanks!!
>>
>> ************
>> Have a great day!
>>
>>
>> Anne C. Lucas, Program Manager
>> AS/400 Worldwide Education/Services Strategy
>>
>> "Passion is the magic that makes impossible-to-meet goals possible."
>>
>> 205/823-4831 T/L 537-9968
>> 800/223-3907 Pager
>> alucas@us.ibm.com
>> +---
>> | This is the Midrange System Mailing List!
>> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>> | To unsubscribe from this list send email to
>> MIDRANGE-L-UNSUB@midrange.com.
>> | Questions should be directed to the list owner/operator:
>> david@midrange.com
>> +---
>>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
>david@midrange.com
>+---
>
>
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: david@midrange.com
>+---
> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---