Re: Network Printing Issue

["Paul Tykodi" <p.tykodi@xxxxxxxxxxxxxxx>]

Hi Tom,

>From your description, it sounds like the print servers that you use cannot
keep a TCP socket connection open to more than one host at a time.

You can therefore go to the IBM iSeries Support Web Site and view the
knowledgebase regarding Print. There are articles in the knowledgebase
covering both the OS/400 PJL and SNMP driver setup on the web site. The
articles explain which timer you can enable on the OS/400 side of the
connection that will close the socket connection towards the printer, when
no files are in the OS/400 queue in Ready status, but still leave the print
writer running.

This change should let your OS/400 and NDPS printing requirements co-exist
peacefully.

If you need further suggestions, please feel free to contact me directly off
list.

Best Regards,

/Paul
--
Paul Tykodi
National Product Manager
Print4sight Inc.

p: 603-431-0606 x115
f: 603-436-6432
E-mail: p.tykodi@xxxxxxxxxxxxxxx
www.print4sight.com


>date: Thu, 04 Sep 2003 09:24:13 -0700
>from: "Tom Jedrzejewicz @ San Pedro" <TJedrzejewicz@xxxxxxxxxxxx>
>subject: Network Printing Issue
>
>Folks --
>
>We have an interesting issue with respect to network printing and the
>iSeries printing co-existing.
>
>We recently upgraded from NetWare 5 to NetWare 6.  In the process we
>converted our printing from IPX queue-based printing to NDPS IP-based
>printing.  Since then, the iSeries remote device printing has not worked
>properly.
>
>When the iSeries printer is started, it prints properly.  However, once
>printing happens through NDPS, the iSeries printer is ended.
>
>I don't know if this is an iSeries issue or not.  I read Mr. Tykodi's
>suggestion to use remote output queues through NDPS
>(http://archive.midrange.com/midrange-l/200003/msg01200.html), but
>that is not preferred as our users need the page control and partial
>printing capabilities that remote output queues don't have.
>
>Any thoughts our advice would be helpful!
>
>Thanks.