MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2004

RE: copy source file keeping source mbr chg date



fixed

And creates a new source mbr chg date, wouldn't accomplish desired result.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Elvis Budimlic
Sent: Monday, October 18, 2004 11:37 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: copy source file keeping source mbr chg date


Not sure why you don't want to use save/restore.  Seems like the best
option.

Kludgy workaround may be to use SQL like:

CREATE ALIAS newMember .....
CREATE ALIAS oldMember ....
INSERT INTO newMember SELECT * FROM oldMember
DELETE ALIAS ...
DELETE ALIAS ...

But that could be a lot of aliases, a lot of inserts and a new program to
maintain.

Elvis




"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.




--
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