Re: Test Development System Survey

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

We have 2 main boxes-- one is all live, the other split live/test.

First, you need to have separate libraries for data, programs, and 
source code.  If you haven't done it, do it!   (:

The next biggest thing is setting up security so that production 
libraries are not usable by programmers!  We feel that authority 
should allow programmers to -read- live data, -use- live programs, 
and -read- live source.  This means that all a programmer needs to 
test is a library where copies of the production files can live.  A 
little juggling of the library list gives complete isolation from 
production:

LIVE ENVIRONMENT:

        DATALIVE
        PROGRAMLIVE
        ...

TEST ENVIRONMENT:

        DATATEST
        PROGRAMTEST
        PROGRAMLIVE
        ...

This means that the PROGRAMTEST library only needs the new objects 
being developed or changed.  Existing objects in PROGRAMLIVE are used 
just as if it were a production environment.

This also works for library lists in job descriptions.  Means you can 
test batch jobs without affecting production data!

We include output queues in our DATALIVE/DATATEST libraries (well, 
not all of them-- QUSRSYS has a bunch of output queues).  Including 
them in the DATAxxx libraries means we can use production names, and 
not have test orders going to the warehouse for picking.  (:

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx




> 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)?