|
Well... if you think about it, when you're creating a printout with a program-described file, you're opening the file and writing records of data to it. The records end up getting printed to the spool. Why is this? because OS/400 knows its a printer file, and that the expected behavior on a Print File is to write the data to a spool. So, likewise when the FTP server program is receiving data from your PC (or another AS/400 or whatever) it'll open up the printer file, write the data to it, and close it... just like any other file on the system. OS/400 knows that data written to a print file should go to the spool, so thats what it does. Make sense? On Thu, 29 Jun 2000, Vini Kolathur wrote: > Scott, > It works great , but what happens when we do that?????I mean how are > we able to FTP something to a non-db file? > > Vini > > This will work for printing a file from a PC via FTP: > > ftp as400 > Name (as400:klemscot): klemscot > 331 Enter password. > Password: > 230 KLEMSCOT logged on. > ftp> cd qsys > 250 Current library changed to QSYS. > ftp> ascii > 200 Representation type is ASCII nonprint. > ftp> put myfile.txt qsysprt > local: myfile.txt remote: qsysprt > 200 PORT subcommand request successful. > 150 Sending file to member QSYSPRT in library QSYS. > 250 File transfer completed successfully. > 4240 bytes sent in 0.49 seconds (8.49 KB/s) > ftp> quit > 221 QUIT subcommand received. > > I just tried it, and it worked for me :) > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.