Re: Sending a SAVF using Operations Navigator

FTP<F4> Tab to Port, <F1>
*DFT
The value 00021 is used.

So, yes, unless you're really into that kind of configuration, port 21
should be it.
Another thing that we used to do here is restrict ftp to only certain
addresses. Originally if a customer wanted to ftp something to us it was
a big pain in the a$$ because we had to find out their IP address (or
whatever their network NATted it to). Then talk to the firewall
consultant and have him open it up. When our customers started getting
more mobile we stopped doing that. And now any IP address can get in. We
do block a few ChiComms and what not that keep banging away on it.

Want to test ftp on the i locally? Try this.
telnet to the i (or open a 5250 session)
once there try this:
ftp '127.0.0.1'
that's the loop back port and should work just fine.
Might try a simple put like this:
CRTSAVF MYLIB/MYSAVF1
CRTSAVF MYLIB/MYSAVF2
SAVOBJ OBJ(MYSAVF2)
LIB(MYLIB)
DEV(*SAVF)
OBJTYPE(*FILE)
SAVF(MYLIB/MYSAVF1)
FTP '127.0.0.1'
bin
put mylib/mysavf1 mylib/mysavf2
quit
DSPSAVF FILE(MYLIB/MYSAVF2)

Because if you've verified the port. And you verified that it's not
blocking by IP address. Then you might have to check for the existence of
"Exit Point" programs:
WRKREGINF
Exit
Exit Point
Point Format Registered Text
QIBM_QTMF_SERVER_REQ VLRQ0100 *YES FTP Server Request Validation
QIBM_QTMF_SVR_LOGON TCPL0100 *YES FTP Server Logon
QIBM_QTMF_SVR_LOGON TCPL0200 *YES FTP Server Logon
QIBM_QTMF_SVR_LOGON TCPL0300 *YES FTP Server Logon
8=Work with exit programs
If you have something in there, let us know. We can spot certain vendors.

Rob Berendt