|
This is somewhat of a kludge, but you might try: ftp> quote rcmd CRTPRTF FILE(JEFTST/TEMPOUTQ) OUTQ(JEFTST/JEF) 250 Command CRTPRTF FILE(JEFTST/TEMPOUTQ) OUTQ(JEFTST/JEF) successful. ftp> put myfile.txt TEMPOUTQ ...etc.etc... ftp> quote rcmd dltf TEMPOUTQ 250 Command dltf tempoutq successful. Or perhaps a better alternative is to have a "permanent" print file thats pointing to your output queue that you can always send to... :) Have fun. On Thu, 29 Jun 2000, Joel Fritz wrote: > That's pretty cool, and considerably less complicated than I thought any one > step solution would be. Borderline elegant. > > Any thoughts on controlling the outq? > > I just tried: > > ftp> quote rcmd ovrprtf file(qsysprt) outq(jeftst/jef) > 250 Command ovrprtf file(qsysprt) outq(jeftst/jef) successful. > > and the print file still went to outq qsysprt. > > -----Original Message----- > From: Scott Klement [mailto:klemscot@klements.com] > Sent: Thursday, June 29, 2000 11:26 AM > To: 'RPG400-L@midrange.com' > Subject: RE: File PC to a AS/400 spool file???? > > > > 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 :) > > > > > On Thu, 29 Jun 2000, Joel Fritz wrote: > > > The simple minded way (the direction I usually choose) is to upload the > file > > to a data base file using ftp, client access, or whatever's available, and > > then doing a CPYF FROMFILE(XXX) TOFILE(*PRINT). You can also substitute > the > > name of a print file in the tofile parm. There's probably something a > > little more sophisticated that will do it in one step. > > > > +--- > | 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 > +--- > > +--- | 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.