RE: copy source file keeping source mbr chg date

I use save/restore when replacing an entire source file(s).  I seem to
remember having a MAKEAMESS moment when I tried to restore a few members
into an existing source file, something like it wiped out all of the
existing members in the source file - I can't remember exactly, but it was
an "oh sh*t" moment!  It might have also been related to restoring a member
from a 112-byte length source file to a 92-byte length source file - in
fact, now that I think about it, I'm pretty sure that was it.  All of my dev
source files are 112-bytes.  All of the production source files that are not
QRPGLESRC are 92-bytes.  Trying to do a restore with that scenario requires
the target source file to be replaced.  I think.

I also have an MI utility that was written by Leif and modded by me that can
modify the member creation and changed timestamps.  Haven't used it in
awhile, but I think this is release-dependent code.  The way I could see
using it is creating a PDM option for WRKMBRPDM, say 'MM' for Move Member or
'CM' for Copy Member, that would use a CL pgm to CPYSRCF the member to the
new location, then retrieve the timestamp attributes of the "from" source
member, and use the MI program to apply the timestamp attributes to the new
source member.

db

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / Don Tully
> Sent: Monday, October 18, 2004 12:23 PM
>
> Save/restore is the only method.  I agree with you that it is important to
> keep the source date for comparing to object header containing the last
> change date of source member.  So I use Save/restore - by member
> if moving a
> single member.
>
> Don Tully
> Tully Consulting LLC
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Franz
> Sent: Monday, October 18, 2004 11:09 AM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: copy source file keeping source mbr chg date
>
>
> Is there a method (without save/restore) to copy a source
> file and all it's members to a new lib, where new source file keeps the
> original source member change date?
> We are copying development libs using CPYLIB, and always find our
> source member change date reset to current date.
> CRTDUPOBJ does the same.
> Each line of code is keeping it's change date, but the member itself
> has it's change date reset.
> jim franz