MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2004

Re: copy source file keeping source mbr chg date



fixed

> And save/restore is a bad thing because...?

As a development team we have no authority to save/restore (as it should
be).
We are not even on same site as hardware, and hardware is managed by
3rd party. It takes a manager to approve a ticket to get a save or restore
done.
I just never understood why CRTDUPOBJ (to create an exact copy of
an object to another location and optionally name) would alter the last
change date of a source member...)
Regardless of the operational difficulty - it seems save/restore is the
answer.
thanks
jim

----- Original Message ----- 
From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, October 18, 2004 12:21 PM
Subject: Re: copy source file keeping source mbr chg date


> And save/restore is a bad thing because...?
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Jim Franz" <franz400@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/18/2004 11:09 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> <MIDRANGE-L@xxxxxxxxxxxx>
> cc
>
> Fax to
>
> 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
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact