Re: CPYSRCF SRCCHGDATE

David FOXWELL wrote:

Funny, we found new source members on the production lpar with a
date inferior to the date they were installed, i.e. they didn't
exist at that date! After searching it was discovered there is
a new CPYSRCPF parameter in V6R1. It has the default value of
FROMMBR. Strange that it wasn't *NEW so as not to change
anything.

From what I recall some prior releases had some PTFs to enable /correcting/ the default behavior to the feature, so the CPYSRCF would maintain the source-changed-date of the from-member just as on v6r1. Also such a behavior change should be documented in the MTU, the Memo To Users, for the release on which the change was made. The parameter name is SRCCHGDATE. A web search on that token or CPYSRCF easily confirms its inclusion in the v6r1 [aka 6.1] MTU at:
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/rzaq9/rzaq9.pdf

From that document:
"In earlier releases (V5R3M0 SI25796 and V5R4M0 SI25844), the Copy File (CPYF) and Copy Source File (CPYSRCF) commands set the Last source update date/time for the target source member to the date and
time the command was run.
Starting in V6R1, the Last source update date/time of the target source member will retain the value of the source member being copied, unless MBROPT(*ADD) was used. If you want the Last source update date/time for the target source member to be the date and time the copy command was run, you will need to use the CPYSRCF command and specify SRCCHGDATE(*NEW)."
http://www-01.ibm.com/support/docview.wss?uid=nas31771728b9db07549862572490052682b
http://www-01.ibm.com/support/docview.wss?uid=nas35b10ec81a38e2f118625724900526873

FWiW: Web searches on those PTF numbers or on various incantations of discussion related to the source change date and the copy source physical file command should also find several discussions from this list.

Regards, Chuck