On 12/06/2008, at 2:39 AM, vhamberg@xxxxxxxxxxx wrote:
I prefer this, as well, except you have assumed the iSeries is
using path naming NAMEFMT 1 = one can't assume that. Also, I think
it should be using the extension .savf on the iSeries side,
not .file - it will work for a GET but will not for a PUT.
When the first "real" (for want of a better word) instruction
involves a path name the iSeries FTP server will automatically switch
to namefmt 1. However, many (most) people find that too confusing so
it's simpler to just get them to specify it although that too has
issues depending on which FTP client you use. On iSeries a simple
"namefmt 1" will suffice, on WinDOS you have to run "quote site
namefmt 1" and in the past I've used clients that required "quote
namefmt 1" or "site namefmt 1" before it would be accepted.
Although a GET will work without a .savf extension you run the risk
of "losing" the savf "attribute" on a subsequent PUT and you may
inadvertently get EBCDIC-ASCII conversion if you forgot bin. Much
better to always specify .savf when transferring save file objects.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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.