Well, I got the TFTP to work, but I don't understand the reason. <p>If I create the destination file using the CRTPF command and specify a record length (no DDS), then the TFTP is successful. <p>If I create the destination file using the CRTPF command and specify DDS, then the TFTP fails (errno = 3440, operation not supported) <p>If I create the destination file using a CREATE TABLE sql statement, then the TFTP fails (write access to file denied). <p>Can anyone shed some light on what is happening?

I am attempting to use TFTP to PUT a file from a Windows-based PC into a physical file on my iSeries. (I am restricted to using TFTP, since an FTP client is not available for the device on which my application will ultimately run.) <p>I have been able to TFTP-PUT files to the /QDLS folders, but am at a loss as to how to use TFTP to write to a physical file. I have tried every permutation of syntaxes that I can think of (to no avail) - all attempts result in "Inaccessible path specified" or "Error Opening <destination path>, errno = 3021." I believe that I have set up the iSeries' TFTP server to allow writing to the desired physycal file (i.e. QTFTP has the appropriate permissions, and TFTP has been configured to allow creation). Can anyone tell me if TFTP can do what I'm asking, and how I would go about doing this? Thanks! <p>Syntax that results in the "Error Opening... errno = 3021" error: <BR>
TFTP x.x.x.x PUT sourcefile /QSYS.LIB/library.lib/file.file/member.mbr <BR>
all other syntaxes result in "Inaccessible path" error.

jwluttrell wrote:<BR>
> Well, I got the TFTP to work, but I don't understand the reason.<BR>
><BR>
> If I create the destination file using the CRTPF command and specify<BR>
> a record length (no DDS), then the TFTP is successful.<BR>
><BR>
> If I create the destination file using the CRTPF command and specify<BR>
> DDS, then the TFTP fails (errno = 3440, operation not supported)<BR>
><BR>
> If I create the destination file using a CREATE TABLE sql statement,<BR>
> then the TFTP fails (write access to file denied).<BR>
><BR>
> Can anyone shed some light on what is happening?<BR>
<P>
The problem s that the 400 doesn't know how to map the data in the file you<BR>
are FTP'ng . That's why a file defined with only one field (record length<BR>
only) is the only one that works. You have a couple of options:<BR>
<P>
1) Do as you are doing and then write a program to process the one field<BR>
file into the file you really want the data to reside in.<BR>
2) FTP to the IFS file system and then use one of the IFS processing<BR>
commands to bring the data in to your end file.<BR>
<P>
Option 1 is probably the easier option if all of this is new to you.<BR>
<P>
Bill<BR>
<P>
<P>