RE: One Box vs Two

Hi Debbie,
        copying production data is of course very convenient, but here in
the uk (I don't know what country you are in) there are data protection laws
that would make this activity illegal for many types of data.  The
co-existence of developers and production systems can work if you have
security under control, and the inevitable performance issues - a typical
developer will use many times more system resources that a typical
production/application user, a figure I heard quoted once was 10x though
this sounds a low estimate in my experience.

Kind regards,
Jeff Bull.
Senior AS/400 Support Consultant (AS/400)
Midas Kapiti International Ltd

Tel:    44 (0) 175 370 8224
Fax:    44 (0) 175 357 0233
Mailto:Jeff.Bull@Midas-Kapiti.Com  << == Replies to 
The views and opinions expressed in this e-mail are the senders own and
do not necessarily represent the views and opinions of Misys Plc.

This email message is intended for the named recipient only.  It may be
privileged and/or confidential.  If you are not the intended named
recipient of this email then you should not copy it or use it for any
purpose, nor disclose its contents to any other person.  You should
contact Midas-Kapiti International as shown below so that we can take
appropriate action at no cost to yourself.

Midas-Kapiti International Ltd, Key West, 53-61 Windsor Road, Slough,
Berkshire, SL1 2DW, England
Email: Postmaster@midas-kapiti.com Tel: (44) 1753 573244 Fax: (44) 1753
570233
Midas-Kapiti International Ltd is registered in England and Wales under
company no. 971479




-----Original Message-----
From: Debbie Panco [mailto:dpanco43@ix.netcom.com]
Sent: Monday, June 19, 2000 2:51 PM
To: MIDRANGE-L@midrange.com
Subject: RE: One Box vs Two



We only have 1 machine and we don't have it partitioned.  Our solution is
simple and seems to work for us.  Each programmer has their own test library
and they do not have update access over the production libraries.  Testing
is done on the same machine and getting test data is just a matter of
copying it over from the production files.  This helps immensely when trying
to duplicate an error condition in the test enviroment.  Of course we don't
have Payroll or other sensitive information on our machine that management
feels the programmers shouldn't have read access to.

Debbie



> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Dennis Munro
> Sent: Friday, June 16, 2000 6:41 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: One Box vs Two
>
>
> We have an S20 as a production machine & a 720 as a Test/Dev machine.
> Running V4R4M0 on both machines.
>
> If you can afford it, I'd go for the two machine state.  Test box
> is not as
> powerful as production machine so things run slower but I at least have it
> on a separate machine.  Maybe I just don't trust the user to get
> to the test
> area & really end up in the production data.
>
> Testing is a whole lot less stressful (do I have my library list set up
> correctly, etc.) on the second machine.  I have a different set
> of user ID's
> for the second box so people really have to be aware of which machine they
> are on - at least that was the intent.
>
> With BPCS as our ERP package, I have two environments set up on my test
> machine.  I used to have three on my production machine but really didn't
> like the real possibility of getting to the wrong environment with the way
> that BPCS logs you in & the user has to choose.  Now I have only one
> environment on my production machine.
>
> I can figure on an hour to restore the BPCS data library using
> the 8mm tape.
> If I use the 3570 tape, it is really quick but more work is
> involved.  I can
> afford to wait an hour.
>
> My vote is for two machines.  Our partial reasoning was to have a "backup"
> machine in case my production machine would melt for some reason.  Things
> would run slower but at least it would run.
>
> Dennis
>
> "One never notices what has been done; one can only see what remains to be
> done." -- Marie Curie
> "I love deadlines.  I especially like the whooshing sound they
> make as they
> go flying by."  Dilbert's Words Of Wisdom:
>
> Dennis Munro
> Badger Mining Corporation
> dmunro@badgerminingcorp.com <mailto:dmunro@badgerminingcorp.com>
> (920) 361-2388
>
>
>       -----Original Message-----
>       From:   Salter, James [SMTP:JSalter@acipco.com]
>       Sent:   Friday, June 16, 2000 9:48 AM
>       To:     'MIDRANGE-L@midrange.com'
>       Subject:        One Box vs Two
>
>       We have a model 530 box as well as a model 510 box at our company.
>       We will be moving to a model 700 series or model 800 series box
> sometime
>       this year.
>       For development work by our programmers, would you recommend having
> 1 box
>       and use partitioning or else
>       having 2 boxes using 1 for development work?
>       I tend to have the opinion that we only need 1 box for our company.
>       There is a big push in splitting our development process away from
> our
>       production environment.
>       I would like your feedback on this.
>       We are a manufacturing company with about 10 programmers on our
> AS/400.
>
>       Also, what type boxes or systems would you recommend for e-commerce
> type
>       applications?
>
>       Maybe a Model 270 system?
>
>       Thanks for your feedback.
>
>
>       +---
>       | 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
+---