Re: Development machine

[rob@xxxxxxxxx]

Suggest a change management package.

Failing that:
- Move, don't copy, all source from the production machine to the 
development machine.
- Remove all compilers from production machine
- Maybe even remove pdm from production machine.
Now, if you're a bank then some silly rules insist that you keep source on 
your production machine.

Even though it's a "development machine" do not give those developers 
*ALLOBJ.  It's amazing how many things work in test but not production 
when you do.

You can move your compiled objects into production by saving them into a 
save file and ftp'ing that over.  Be selective when you save.  For 
instance I used to do stupid things like name my trigger programs after 
the file they affected.  Now I add a T on the end of the object.  The 
first time you save a copy of the trigger program, (and accidentally used 
the *ALL instead of *PGM thus getting you the file also), and you replace 
the actual data file, you'll be slightly disappointed (big 
understatement).  Did I say get a change management package?



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
05/19/2003 04:27 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Development machine


We are looking at setting up a "spare" AS400 for our developers to tear up
instead of degrading performance on our production machine. 
Do you any of you all have guidelines or advice on how to transfer source 
&
database files back & forth between the two machines?
I realize this may be a broad question, which is why I'm not providing a 
lot
of details up front, until some of the discussion begins. 


Thanks in advance. 
_______________________________________________
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.