Re: FTP of Source Members Without Losing Information

Ken,

If you can build DDM files between the systems, I have a utility where
I create a DDM file on the destination source file in qtemp, and do a
CPYSRCF command to that file, then delete the DDM file.

It does not ask for confirmation replacing the member, but It does
move the member description and source type.

if you're interested i can post the source.  it's not long.

On 12/9/05, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:
> I haven't tried it, but this might work:
>
> SAVRST RMTLOCNAME(SOMEMACHINE)
> OBJ(('/QSYS.LIB/SOMELIB.LIB/SOMEFILE.FILE/SOMEMBR.MBR'))
>
>
>
> --
> John A. Jones, CISSP
> Americas Information Security Officer
> Jones Lang LaSalle, Inc.
> V: +1-630-455-2787  F: +1-312-601-1782
> john.jones@xxxxxxxxxx
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Slaugh
> Sent: Friday, December 09, 2005 12:35 PM
> To: Midrange Systems Technical Discussion
> Subject: FTP of Source Members Without Losing Information
>
>
> Has anyone discovered a solution which retain created/changed date on a
> source member record when the member is transferred via FTP?
>
> I know that there are ways to send a savefile instead without loss but,
> of course, this savefile process takes additional steps. For
> clarification, here's the example of the FTP commands:
>
> CD TargetLIB
> LCD SourceLIB
> PUT QRPGSRCLE.TESTMBR
>
> There actually is two issues resulting from this method of transfer. The
> first is, if the source member is a new member, the member type and text
> is blank and must be reset manually. The second is that ALL the source
> record modification dates have been removed. Resetting the member type
> and text is easy to overcome but recovering modification dates is
> impossible.
>
> Anyone else discovered a solution or is this problem resolved in newer
> OS/400 release?
>
> Just thought I'd ask. Thanks,
>
> Ken Slaugh (707) 795-1512 x118
> Chouinard & Myhre, Inc.
> http://www.cm-inc.com/
>
> DISCLAIMER: The information contained in this e-mail may be confidential
> and is intended solely for the use of the addressee.  Access, copying or
> re-use of the e-mail or any information contained therein by any other
> person is not authorized.  If you are not the intended recipient, please
> notify us immediately by returning the e-mail to the originator and
> destroying all unauthorized copies.
>
>
> --
> 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 email is for the use of the intended recipient(s) only.  If you have 
> received this email in error, please notify the sender immediately and then 
> delete it.  If you are not the intended recipient, you must not keep, use, 
> disclose, copy or distribute this email without the author's prior 
> permission.  We have taken precautions to minimize the risk of transmitting 
> software viruses, but we advise you to carry out your own virus checks on any 
> attachment to this message.  We cannot accept liability for any loss or 
> damage caused by software viruses.  The information contained in this 
> communication may be confidential and may be subject to the attorney-client 
> privilege. If you are the intended recipient and you do not wish to receive 
> similar electronic messages from us in future then please respond to the 
> sender to this effect.
>
> --
> 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.
>
>