Re: Using CPYTOIMPF to copy a source member to the IFS does not copy fields SRCSEQ and SRCDAT

That's why a Git repository is a good thing. It will allow you to see a source member diff side by side with missing lines that were deleted.

You can even compare today's version to something last year and then copy/paste lines you want from the source.

I can recall debates on the merits of commenting out code vs removing dead code and there's probably no single right answer.

Although as I continue to use Git more, I am starting to come around to the idea of removing dead code so I don't have to skip over a ton of old code and comments or track several source member copies. (Aaak...Many of them mine....)

I can always go look at the diffs.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 3
date: Wed, 28 Apr 2021 08:40:35 -0400
from: a4g atl <a4ginatl2@xxxxxxxxx>
subject: Re: Using CPYTOIMPF to copy a source member to the IFS does
not copy fields SRCSEQ and SRCDAT

The requirement is purely mine. If I need to compare then I would have the
source to do so. My problem is an unruly bunch who delete lines of code
rather than commenting lines out... so when something goes wrong, I can go
back and check. Source compare cannot handle the changes made and so is not
always helpful.

On Mon, Apr 26, 2021 at 4:33 PM Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Back to Darryl - what are you trying to accomplish with an IFS copy? Is
that meant to be the source for compiling? Or documentation? Just
curious!! If trying to compile from IFS source, I don't know, do source
sequence and source date show up? Developers are kind of expected to get
used to using something like GIT and diffs, right?

OK, back to regular source PFs!

Regards
Vern