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

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I second the motion to use an actual source control app.

If you're not going to do that...then you should take a cue from the
various IBM i CM products.

Do not allow folks to edit your "production" source directly.
The production source should be in its own set of files.
Developers should edit / test from their own set of files, a CM process
should be responsible for moving source from the DEV file to the production
environment; at which point you can archive the existing production source
before replacing it with the newly promoted version.

HTH,
Charles

On Thu, Nov 7, 2024 at 8: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.