At 02:11 AM 12/25/97 EST, you wrote:
>Mark,
>
>In a message dated 97-12-24 04:33:12 EST, you write:
>
>> >>   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).
>
>OK, I'll bite.  Just how does one lose the external definition to a file that
>didn't exist in the first place?  Sure, the definition doesn't transfer, but
>then that was my point...

 You may have posted that comment tongue-in-cheek, but I see no good reason
that the /400 doesn't have an option to retain attributes when sending
between /400s.  

 -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
+---


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].