Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
I'm about to release 3 new CL commands and want feedback on them.
All three use the FTPFILE command under the covers to send the content to the remote location. The first two automatically create save files and then FTP those save files, the SENDSAVF command (obviously) sends an existing save file. Up to 300 generic-enabled save file names may be specified.
I had others in the pipe line and prototyped, but these three seemed to be all that's really needed in day-to-day operations.
What do you people think?
By the title, I thought you were going to start sending us porn...
Better?
We had been FTP'ing SAVLIBs from our production box to our development/backup box and found FTP to be very unreliable. Of course these SAVLIBs are large and more than occasionally the FTPs would fail and we would end up with partial SAVLIBs. We have switched to SNADS to send the SAVLIBS. Much more reliable. Needless to say, we aren't very sold on FTP, at least for large files.
Of course SNADS would be better. Its a well architect protocol vs something that depends on SOCKETS to work. But... it does require that people "enrolled" to use it. If IBM would just let you send things using it without having to enroll the sender it would be perfect.