Re: Copying Source Members

On Wed, Aug 2, 2017 at 12:01 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

I'd write a quick CMD + CLP combination to do the rename / copy (aka
promote to production?) Once that is debugged, add it to RDi as a User
Action. These function exactly like User Commands do in PDM.

This is what I would do also. (It *is* what I did for myself, except I
*do* use PDM, so I used iSeriesPython instead of CL, and dispensed
with a separate command, opting instead for a PDM option that directly
invokes Python.)

One thing that comes up with this approach is what to do when your
program name is too long to tack anything onto it. (This is really an
issue with keeping your source in physical files more than anything
else.) Not only is there the immediate case of 10-character member
names, but also how do you ensure that a 9-character name with a
suffix tacked on won't happen to be the same as another member that
already exists?

So, I realize this is quite a whopper of a tangent, but if you really
want to be safe (in the sense that you never, ever automatically
clobber the existing member), you could keep the archived copy in an
IFS stream file, where you're free to come up with a naming convention
that is much, much more resistant to collisions (in case you want to
keep more than one archived version).

I've been thinking it would be kind of fun to implement this myself,
though I start to wonder when I've crossed the line into "why not just
use Git already".

John Y.