×
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.
On 18/08/2008, at 5:04 AM, vhamberg@xxxxxxxxxxx wrote:
All the more reason to abandon remote outq's as much as possible
and use *LAN devices - those WILL report the pages, I believe.
I thought that was implied by my response but it's always better to
be explicit. I think you're correct on page reporting for *LAN
devices but it's been a while since I needed both *LAN and job
accounting so I can't be sure.
Of course, some printers don't work with devices, but that is
relatively few, I hope.
Yes, remote output queues should be the choice of last resort, used
only when stuck with a printer that isn't (or can't be) properly
recognised as a *LAN device. Ideal of course is to CHOOSE a *LAN
supported printer before purchasing.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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.
midrange.com
