|
In the case below the from library is BDIETZ and the target is BDTEST. the source file in BDtest existed before the FTP. I did a LCD(local change directory) on the source system and a CD(change directory) on the target system. The mput then sends from source to the target. As for the last question on replacing members I quote from the help: <help> You can use an asterisk to send all the members in a file or all the documents in a folder. For example, MPUT MYLIB/MYFILE.* transfers all the members of file MYFILE in library MYLIB. Note: If the remote file already exists, the contents are replaced by the contents of localfile unless SUNIQUE is on. </help> ---------------------------- Bryan Dietz > > Thanks, Bryan and Buck, for suggesting mput. > > Also I am a bit vague on mput usage as per example. > Is BDTEST the from-library on the source system ? > Is BDIETZ the to-library on the target system ? > & does mput replace an existing target object ? > > tia, Fiona > __________________________________________________________ > cd bdtest > 250 "BDTEST" is current library. > > lcd bdietz > Local working directory is BDIETZ > > mput qclsrc.* > 250 Now using naming format "0". > 257 "BDTEST" is current library. > 227 Entering Passive Mode (127,0,0,1,4,60). > 150 Sending file to member #PROC in file QCLSRC in library BDTEST. > 250 File transfer completed successfully. > 161 bytes transferred in 0.261 seconds. Transfer rate 0.617 KB/sec. > 227 Entering Passive Mode (127,0,0,1,72,46). > 150 Sending file to member #QWCRJBST in file QCLSRC in library BDTEST. > 250 File transfer completed successfully. > 2552 bytes transferred in 0.106 seconds. Transfer rate 23.975 KB/sec. > > > you do however lose the source member type and text. > > ---------------------------- > Bryan Dietz > > > > __________________________________ > > Notice of Confidentiality > > This transmission contains information that may be confidential and > that may also be privileged. Unless you are the intended recipient > of the message (or authorised to receive it for the intended > recipient) you may not copy, forward, or otherwise use it, or > disclose it or its contents to anyone else. If you have received > this transmission in error please notify us immediately and delete > it from your system. > > Email: internet.mail@xxxxxxxxxxxxxxxx > > _______________________________________________ > 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 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.