× 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.



You will need to lookup information for your printer model here:
http://www-01.ibm.com/support/docview.wss?uid=nas1b44a2cf4ba778d83862568
250053649f

So far, most of the newer printers we've purchased that come with a
built in network print server seem to support IPP, so you might want to
investigate that option. I typically use a browser to connect to the
printer device to determine which protocols the printer supports...
IBM's documentation is sometimes out of date, as printer manufacturers
may update printer firmware to support new features without IBM being
aware of the change.

We chose to avoid SNMP for printers, due to a security concern
(something about community strings?), but have found IPP to work
perfectly for devices that support it.

-Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Thursday, December 30, 2010 12:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: Printer device *INFO messages

HPPJLDRV

John McKee


-----Original message-----
From: "DeLong, Eric" EDeLong@xxxxxxxxxxxxxxx
Date: Thu, 30 Dec 2010 11:48:12 -0600
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: RE: Printer device *INFO messages

What protocol are you using to communicate with the printer?
HPPJLDRV,
IBMPJLDRV, IBMSNMPDRV, IBMIPPDRV? I have found SNMP and IPP drivers
much more robust when dealing with WAN connected devices, with PJL
being
the worst at handling network timeouts. The capabilities of your
network print server determines which protocol you can try.

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Thursday, December 30, 2010 9:15 AM
To: Midrange Systems Technical Discussion
Subject: Printer device *INFO messages

I have been changing the PRTERRMSG parameter on printer devices from
*INQ to *INFO. Stops a writer from backing up if the printer runs out
of paper. Users take care of the printer anyway, so it seems ideal.
However, A WRKWTR will show a writer status as MSGW, even though no
response was requested. Only way I have seen to have the status
change
is to ENDWTR, STRPRTWTR.

Is this what is supposed to happen at v5r4?

John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.