|
Dean, At 06:56 PM 12/21/97 EST, you wrote: >> The major problem I've found w/ FTP is that the file must already have >> been created on the target system is you want to keep is externally >> described. Is there an easy way around this problem? > >I wouldn't consider it a problem, myself. If you are interfacing to other >systems, _YOU_ should be the one controlling the data format. A way around >would be to receive the file into a flat version on the /400, and perform a >CPYF from the received file to your target file with a FMTOPT(*NOCHK). No good. If the file already exists on the target system, it works fine. If not, the external description is lost. Even when sending a *SAVF, the attribute is messed up; it just says *FILE, not *SAVF (even though the system does still treat it as a *SAVF when doing a RSTOBJ). -mark +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.