Re: create an archive of a source member each time changed

True, but I can’t tell you how many times in the last 30 years developers have been really happy we do that. Clear the journal reliever daily but write a program that scans it looking for new members (or what ever criteria you want) then take appropriate action.

This is in lieu of a true source control (IE: git) or other OEM product for source control.


Jim Oberholtzer
Agile Technology Architects

On Nov 7, 2024, at 1:12 PM, Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx> wrote:


Journaling source files will record each and every source line in every changed source member. :-o You could very quickly fill those journal receivers, if you have moderately "active" development going on in the journaled source files. :-o

Just saying.

On Thursday, November 7, 2024 at 02:06:32 PM EST, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> wrote:

I guess journaling the source file is too easy?

Jim Oberholtzer
Agile Technology Architects

On Nov 7, 2024, at 9:35 AM, eric bothes <iseriesstuff@xxxxxxxxx> wrote:

I'm looking for a way to create an archive of a source member each time it is changed using seu/etc.

basically want to keep a history of any changes.

is there an api/trigger or something where i can run an archive process prior to changes being saved to a source member?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.