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

In the words of the immortal - well, almost immortal - Mark Twain, "The report of my death was...".


On Thu, 7 Nov, 2024 at 2:57 PM, Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:


To: midrange systems technical discussion
Cc: jack.woehr@xxxxxxxxxxx
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<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of Paul Therrien via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto: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.