× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.