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

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

PDM:
Do you have your own custom MAKE or are you using option 14 to compile?
Do you have your own custom EDIT or are you using PDM's option to edit?
A custom method for either would be easy to add an archive step.
Or, you could add your own ARCHIVE option to PDM and try to remember to use
that.

Or, here you go, add a command exit point program on STRSEU to archive the
source prior to editing.  I've done command exit point programs and they're
relatively simple:
- SIGNOFF, if the user was QSECOFR create a pdf of the joblog and email it
to me.  (Hey boss, if you're mining this you might want to add that to your
to do list if ...  One reason to monitor my emails for at least through a
downtime.)
- SNDDST, if it was used for email then use whatever we're using for email
from IBM i at this time.

If they are using other editors (for the love of God I hope so) then
perhaps one of the database exit point programs might work?

On Fri, Nov 8, 2024 at 7:30 AM <paultherrien@xxxxxxxxxxxxxxxxxx> wrote:

> I should say, that this is my personal archive. Our company is using
> Implementer for change management.
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack
> Woehr via MIDRANGE-L
> Sent: Thursday, November 7, 2024 3:57 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Cc: Jack Woehr <jack.woehr@xxxxxxxxxxx>
> Subject: Re: create an archive of a source member each time changed
>
> And you're planning on explaining this to your next 26-year-old hire and
> act
> like you don't notice when they put their hand in front of their mouth to
> hide their laughter?
>
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Paul
> Therrien via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 7, 2024 13:50
> Subject: RE: create an archive of a source member each time changed
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the
> content is safe.
>
> I have a source file called '@ARCHIVE'.
> When I want to save a current copy of a source member, I call a simple CL
> program that copies the source  member to an @ARCHIVE member.  The member
> name of the archived source is '@YYMMDDnnn' (where nnn is a
> programmatically
> generated sequential number), and the source type is the original source
> member.  In this way I can use PDM or RSE and see all copies of 'PGMA' by
> selecting Source Type 'PGMA'.  I see all archived copies in date sequence.
> I have tied this CL program to a PDM option, and an RSE User command.
> It is not source control, it is simply archiving on demand.
>
> --
> 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.
>
> --
> 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.