RE:

Rachel,

A better approach is to change your production source files to be
"read-only".  Then you would need some sort of "change management" program
to move development/testing source members to the production source files.
This ways accidents can't happen.

There are a number of 3rd-party packages that do a LOT of good things for
"change management".  If the costs aren't acceptable, it is not too
difficult to write a simple CLP that would allow source members to move to
production, but with auditing and security.  Hope this helps.

William K. Reger
Senior Project Manager
Levitz Furniture Corporation
Phone:  (561) 994-5114
E-mail:  breger@levitz.com <mailto:breger@levitz.com> 


-----Original Message-----
From:   Gething, Rachel [mailto:gething@MARYWOOD1.MARYWOOD.EDU]
Sent:   Friday, September 24, 1999 6:09 AM
To:     RPG400-L@midrange.com
Subject:        


> Rachel Gething 
> Programmer Analyst
> Marywood University 
> 2300 Adams Ave
> Scranton,  PA 18509
> 
> Be Gentle Boys and Girls, I'm a rookie.  I would like to know what the
> best way to journal source members would be.  We have had a few instances
> of changing live source, as opposed to changing copied source in a test
> library.  I would like some input on journaling source members on a daily
> basis for restoring it more easily if an instance like this should occur
> again.
> 
> Thanks in Advance
> Rachel Gething
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---