×
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.
On 1/12/11 2:07 PM, Tom Deskevich wrote:
Ok, I cannot use a save file because I am at 7.1 and they are at 5.2,
you can only go back to 5.4.
I tried APPEND, I tried PUT since you said it implies replace.
In both cases I get this: (file is is at destination with no records,
built with DDS)
<<SNIP>>
Rather than using the generic data transport methods of FTP which are
limited to just text or binary, and since CPYF was noted as a recovery
attempt in a prior post, why not just use a TCP/IP DDM File to copy the
data using a *database* data transport method? That is, the data is
neither from a flat file nor a stream file of nondescript [beyond fixed
record length or EOL markers to describe] text data or binary data.
Since the data is apparently from an externally described database file
member per the target file member being created as a DDS\externally
described database file, then CPYF of a DDMF on the source system
/pointing/ to the database file [member] on the target system can
directly invoke the database I/O to send the data. No save\restore
required.
Regards, Chuck
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.
midrange.com
