For the archives, this is the device description being used for an HP
M652dn attached to IBM i at 7.3. Everything seems to be working properly,
so far.

CRTDEVPRT DEVD(HP1) +
DEVCLS(*LAN) +
TYPE(3812) +
MODEL(1) +
LANATTACH(*IP) +
PORT(9100) +
ATTACH(*DIRECT) +
ONLINE(*YES) +
FONT(011 *NONE) +
FORMFEED(*AUTOCUT) +
SEPDRAWER(*FILE) +
PRTERRMSG(*INFO) +
MSGQ(*LIBL/PRTMSGS) +
ACTTMR(170) +
INACTTMR(*SEC15) +
LINESPEED(19200) +
WORDLEN(8) +
PARITY(*NONE) +
STOPBITS(1) +
TRANSFORM(*YES) +
MFRTYPMDL(*HPCOLORLJ) +
PPRSRC1(*LETTER) +
PPRSRC2(*LETTER) +
ENVELOPE(*NUMBER10) +
ASCII899(*NO) +
IMGCFG(*NONE) +
CHRID(*SYSVAL) +
RMTLOCNAME('192.168.0.181') +
USRDFNOPT(*IBMSHRCNN) +
SYSDRVPGM(*HPPJLDRV) +
TEXT('HP M652dn (HP1)') +
PUBLISHINF(*UNKNOWN *UNKNOWN *UNKNOWN *UNKNOWN *BLANK +
(*UNKNOWN))




On Fri, Oct 12, 2018 at 7:30 AM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

Someone else yesterday (not on midrange-l) questioned about the buffer,
which I haven't had a chance to look into.

However -

I change the device description from SYSDRVPGM(*IBMSNMPDRV)
to SYSDRVPGM(*HPPJLDRV), reran the job and lo and behold, it ran to
completion!

The MFRTYPMDL is *HPCOLORLJ.



On Thu, Oct 11, 2018 at 5:38 PM Don Brown <DBrown@xxxxxxxxxx> wrote:


I have seen a similar problem with less expensive printers in the past.

The problem was how the printer handled a spool stream that was bigger
than
the printers buffer.

In our case the printer just dropped any data sent once the buffer was
full
- not ideal!

Check the configuration settings on the printer and see if any thing
stands
out as an option for buffer size.

You may need to open a case with HP as this is not a cheap base level
printer.



Don Brown






From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 11/10/2018 11:40 PM
Subject: Re: HP M652dn printer - not printing entire spool file
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I forgot we do a special invoice run on Thursday morning. Today it
consisted of 74 invoices. It ended during the 66th invoice, which, at 2
copies per invoice, was 132 pages. So far no joy.

I changed from *HPCOLORLJ to *LEXMARKC750, what it was on the old printer,
to see what happens the next run.



On Thu, Oct 11, 2018 at 6:44 AM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

That being said, I changed it to *HPCOLORLJ and we'll see what happens
late this afternoon.


On Wed, Oct 10, 2018 at 8:42 PM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

All 3 recommended mfrtypmdl for the m603 are for b&w printers.

On Wed, Oct 10, 2018, 8:40 PM midrange <franz9000@xxxxxxxxx> wrote:

I would suggest your choice for the mfrtypmdl is not good for this
reason:

M652dn Enterprise is a color printer , as was the previous printer it
replaced.

M605 which you saw as "close to the same number" is black and white,
but
is
Enterprise.
I've never had success using a b&w mfrtypmdl for a color printer, or
visa
versa.

This is more like the M553dn Enterprise and the M750dn Enterprise

I would use the *LEXMARKC750 or *HPCOLORLJ - I had someone from IBM
tell
me years ago at Common that if they recommend multiple mfrtypmdls in
the
online doc, the 1st one is the "most recommended..." - try them out.

Btw - the only time I've seen spooling where the printer did not
complete
the printing, but the system spool was in SAV status (which indicates
the
printer buffer accepted the whole spool) was if an operator, changing
paper,
hit a "clear" button...

Jim Franz


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of
Jeff
Crosby
Sent: Wednesday, October 10, 2018 9:29 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: HP M652dn printer - not printing entire spool file

All,

Background
==========

IBM i 7.3, current on PTFs. We use FormSprint to generate color
invoices.

We recently replaced an HP CP4025dn printer with an HP M652dn because
the
old printer has had it.

For the new printer, I literally varied off the device, made 2 changes
to
the device description, and varied it on. The 2 changes were to the
TEXT
and MFRTYPMDL parms. A RTVCFGSRC of the new device description looks
like
this:

CRTDEVPRT DEVD(HP1) +
DEVCLS(*LAN) +
TYPE(3812) +
MODEL(1) +
LANATTACH(*IP) +
PORT(9100) +
ATTACH(*DIRECT) +
ONLINE(*YES) +
FONT(011 *NONE) +
FORMFEED(*AUTOCUT) +
SEPDRAWER(*FILE) +
PRTERRMSG(*INFO) +
MSGQ(*LIBL/PRTMSGS) +
ACTTMR(170) +
INACTTMR(*SEC15) +
LINESPEED(19200) +
WORDLEN(8) +
PARITY(*NONE) +
STOPBITS(1) +
TRANSFORM(*YES) +
MFRTYPMDL(*HP5SI) +
PPRSRC1(*LETTER) +
PPRSRC2(*LETTER) +
ENVELOPE(*NUMBER10) +
ASCII899(*NO) +
IMGCFG(*NONE) +
CHRID(*SYSVAL) +
RMTLOCNAME('192.168.0.181') +
USRDFNOPT(*IBMSHRCNN) +
SYSDRVPGM(*IBMSNMPDRV) +
TEXT('HP M652dn (HP1)') +
PUBLISHINF(*UNKNOWN *UNKNOWN *UNKNOWN *UNKNOWN *BLANK +
(*UNKNOWN))

The MFRTYPMDL of the old CP4025 printer was *LEXMARKC750 because
that's
what
this page:

http://www-01.ibm.com/support/docview.wss?uid=nas8N1019534

recommended. The new printer, M652dn, is not listed. The closest I
could
find was M603dn which suggested a MFRTYPMDL of *RICOHAP3200 or *HP5SI
or
*HP4000.
I picked *HP5SI just because.

The Issue
========
We're having no issues with most everything printed except invoices.

We use the printer to print invoices from the IBM i. A daily batch
will
be
150-300 pages. Both days we have done this, it printed 120-150 pages
of
the
spool file and skipped the rest. Went on to the next spool file as if
the
remaining pages did not exist. The spool file automatically goes to
SAV
status, so I changed the PAGERANGE parm, released it, and got the rest
of
the pages. There is nothing in the printer message queue. There is
nothing
in the printer event log.

This is the only IBM i spool file of this size as most reports are
made
into
PDFs and emailed, so I don't have another to try. I have done 1
Windows
printout of 160 pages (the operator's guide for this printer) and it
completed fine.

Anyone got an M652dn attached to IBM i? Would changing the MFRTYPMDL
do
anything? I don't want to just start making guesses.

Thanks.

--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of
my
company. Unless I say so.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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:
http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD



--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.



--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD



--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.




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.