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


  1.  Home
  2. MIDRANGE-L
  3. August 2019

RE: *HPPJLDRV vs. *IBMSNMPDRV

< What does USRDFNOPT(*IBMSHRCNN) do?>
From https://www-01.ibm.com/support/docview.wss?uid=nas8N1019572
Configuring a *LAN 3812 SNMP Device Description

I included all 3 paragraphs because " it depends..". I use it when the
printer is shared with a local Win network.

User-Defined Options (USRDFNOPT)
This specifies, for spooled output only, one or more user-defined options to
be used by user applications, user-specified programs or the writer. A
maximum of four user-defined options can be specified. However, *IBMSHRCNN
is the only user-defined option that is supported by the SNMP print driver
code at this time.

Setting the User-defined options (USRDFNOPT) parameter to include *IBMSHRCNN
causes the print driver to open and close the connection to the data port on
the printer for every copy of every spooled file. This allows multiple
writers and systems to access the printer while the print driver is active
and there are files in ready status. However, you might not want to specify
*IBMSHRCNN if you want the printer to be dedicated or if you do not wish to
incur additional connection charges for each additional socket connection
that would be established. When this option is specified, the printer is
capable of being shared, and the value that is specified for the Inactivity
Timer is ignored.

It is recommended that the User-defined options (USRDFNOPT) parameter be set
to *IBMSHRCNN whenever configuring a *LAN 3812 SNMP device description.
However, it is required for an IBM InfoPrint 21 printer because this printer
will not operate properly if the USRDFNOPT parameter is not set to
*IBMSHRCNN. Also, it is strongly recommended that the USRDFNOPT parameter be
set to *IBMSHRCNN when printing to an IBM 4247, IBM 6400, or IBM Infoprint
6500 line matrix printer.

Jim

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of
mlazarus
Sent: Tuesday, August 13, 2019 9:02 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: *HPPJLDRV vs. *IBMSNMPDRV

Hi Jim,

Thanks. You're correct, it's an M404DN.

Are able to share the source for WSCST(QGPL/HP5SI)?

What does USRDFNOPT(*IBMSHRCNN) do? Do you have a spool utility that does
something with it?

-mark

On 8/12/2019 7:49 PM, midrange wrote:
The data sheet for HP LaserJet Pro M404 series (since you did not
mention the "M" I am guessing...
Google says this is the only "HP404" ) Standard print languages are HP
PCL 6, HP PCL 5c

IBMs doc http://www-01.ibm.com/support/docview.wss?uid=nas8N1019534
has HP M401 and M402 and as long as the print languages the same it
has always been good to be close. It lists both *HP5SI and *HP4000.

I did not see (or missed) what MFRTYPMDL you used.
The *HP5SI has been very stable. I do prefer SNMP over the older PJL I
do use a WSCST with a slight mod to print closer to the edges.

I've used (several) HP M402N printers which have the same print
languages - most of this is default CRTDEVPRT DEVD(P6) DEVCLS(*LAN)
TYPE(3812) MODEL(1) LANATTACH(*IP) +
PORT(9100) ATTACH(*DIRECT) ONLINE(*YES) FONT(011 *NONE) +
FORMFEED(*AUTOCUT) SEPDRAWER(*FILE) PRTERRMSG(*INQ) +
MSGQ(*CTLD) ACTTMR(170) INACTTMR(*SEC15) LINESPEED(19200) +
WORDLEN(8) PARITY(*NONE) STOPBITS(1) TRANSFORM(*YES) +
MFRTYPMDL(*HP5SI) PPRSRC1(*LETTER) PPRSRC2(*NONE) +
ENVELOPE(*NONE) ASCII899(*NO) IMGCFG(*NONE) +
CHRID(*SYSVAL) RMTLOCNAME('xxx.xx.xx.xxx') WSCST(QGPL/HP5SI) +
USRDFNOPT(*IBMSHRCNN) SYSDRVPGM(*IBMSNMPDRV) +
TEXT('XXX printer HP M402N') Jim Franz


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Krill, Coy
Sent: Monday, August 12, 2019 12:49 PM
To: Midrange Systems Technical
Discussion<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: *HPPJLDRV vs. *IBMSNMPDRV

They function differently at the communication level but the printing
functionality is the same. When you were trying the HPPJLDRV driver
you did set the port to 9100? That's the most common issue I see with
newly configured printers using HPPJLDRV is that someone forgets to set
the port.

Coy Krill
Core Processing Team Lead
Washington Trust Bank


-----Original Message-----
From: MIDRANGE-L<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
mlazarus
Sent: Monday, August 12, 2019 09:25
To: Midrange Systems Technical
Discussion<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: *HPPJLDRV vs. *IBMSNMPDRV
Importance: Low

Is there any difference functionally between the *HPPJLDRV and
*IBMSNMPDRV drivers? A client would like to set up an HP 404DN
printer. Using *HPPJLDRV did not work at all. The writer ended
immediately when attempting to print any spool. IBM support recommended
trying *IBMSNMPDRV.

Why would the driver designed for HP printers not work but the IBM
one would? Is there any reduction of functionality using that driver?

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

This electronic mail message and any attachments may contain
confidential or privileged information and is intended for use solely
by the above-referenced recipient. Any review, copying, printing,
disclosure, distribution, or other use by any other person or entity
is strictly prohibited under applicable law. If you are not the named
recipient, or believe you have received this message in error, please
immediately notify the sender by replying to this message and delete
the copy you received

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com


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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


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.