× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Not sure if I might have misunderstood your needs:
PC has to print some info, that you want it to be copied onto a iSeries DB file with CPYSPLF.
I assume you are not sending to printer fancy print out , but just plain text data...
Then why not tell the PC so?
Googling for "pc windows print to a flat file" gives quite a number of answers.
One of them is in this page:
http://www.windowsitpro.com/article/john-savills-windows-faqs/how-can-i-print-to-an-ascii-text-file-.aspx

Just tried it, and created a new printer on my PC, which I called "Text only" printer, not to be the default printer...
Then called EXCEL and printed a report of an .xls sheet of mine, plain data only, to that printer.
Asked me path and name of output file.
Output shows data in ASCII plain text file. It could be set to a shared drive
I guess, though have not tried it, it could then be copied to whereever you need.

Or have I totally missed your point?
HTH
Antonio
-------------------------------------------------------------------------------------------------
El 17/05/2010 22:49, Mike Cunningham escribió:
Success! (almost). Thanks to a few replies to my post I have setup NetServer to share a printer that I have configure in Windows as a printer and I can print to that printer from Windows and the file shows up in the iSeries output queue. I can move the spool file and send it to the printer. What I can't do is a CPYSPLF to a database file :( which is what I need to do next. If I setup the NetServer printer share with auto I get an ASCII spool file that I can't display or copy. If I change the printer share and specify SNA (aka SCS) I get a spool file I can display but it is all garbage (probably ascii characters displayed as ebcdic). There is one setting on NetServer printer share that I can't figure out what to enter. The Printer Driver. All documentation I can find points me to a directory in the IFS that I do not have. Qca400\Win32\Install\Printer I have Qca400 but not Win32 and below.

Anyone have any thoughts on where I might look next?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Monday, May 17, 2010 10:36 AM
To: Midrange Systems Technical Discussion
Subject: RE: Print from a PC to iSeries output queue

Mike,

Just go into navigator and define a print share. This lets you install
printer drivers on your PC that use your midrange as a windows print
server.

-Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Sunday, May 16, 2010 7:42 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Print from a PC to iSeries output queue

Is it possible to setup a Windows PC so it has a printer that would
print to an iSeries output queue? And then use whatever iSeries
utilities there are to manage that spool file? Might be move it to a
queue attached to a remote laser printer and print it, might be copy the
spool file to a database file and process it with my own application,
might be print it to a local attached printer. Would this be something
IPP printing would handle? If so I think I can figure out the server
side for setup of IPP but what would I need to do on the PC side to
setup a Windows printer that points to the IPP device?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.