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



I think I might be getting the CPD337C because I am behind my home office
firewall that has port 9100 opened.

I changed the printer to SNMP and opened the additional ports and the
printout is the same, however no errors in the joblog.

I changed back to PCL and opened additional ports for that and am no longer
received the CPD337C.

On Mon, Jul 4, 2016 at 12:55 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

OK, I'm trying to remember analyzing this stuff - years ago - see if there
are more than one job with the name of the writer - if so, look at each one
for issues.

Seems there were a couple jobs when I looked - one was pretty useless,
like this, another had more to say.

Good luck and may your Fourth be a bang-up day!
Vern


On 7/4/2016 10:52 AM, Jack Tucky wrote:

Hi, thanks for replying.

This is all that's in the joblog. The writer does not end.

5770SS1 V7R1M0 100423 Display Job Log SYSTEM 07/04/16 11:48:27 Page 1
Job name . . . . . . . . . . : JRLASER User . . . . . . : QSPLJOB Number .
. . . . . . . . . . : 302988
Job description . . . . . . : QSPLPRTW Library . . . . . : QGPL
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 07/04/16 11:47:25.045023 QWTPIIPP QSYS 04C0 *EXT *N
Message . . . . : Job 302988/QSPLJOB/JRLASER started on 07/04/16 at
11:47:25 in subsystem QSPL in QSYS. Job entered system on 07/04/16 at
11:47:25.
*NONE Request 07/04/16 11:47:25.045291 QWTSCSBJ *N QCMD QSYS 0195

From user . . . . . . . . . : JR
Message . . . . : -CALL QSYS/QSPWTRM1
CPD337C Diagnostic 40 07/04/16 11:47:52.705062 QWPPJLDR QSYS *STMT
QWPPJLDR
QSYS *STMT
From module . . . . . . . . : WPPJLDR
From procedure . . . . . . : Socket_Recv
Statement . . . . . . . . . : 27
To module . . . . . . . . . : WPPJLDR
To procedure . . . . . . . : _C_pep
Statement . . . . . . . . . : *N
Message . . . . : The session with device JRLASER ended abnormally.
Cause . . . . . : The session with the device at RMTLOCNAME JROFFICE ended
abnormally. Recovery . . . : Check for problems in the network or at the
remote device. Start the printer writer again. If the problem continues,
report it using the ANZPRB command.



On Sun, Jul 3, 2016 at 5:48 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Jack

What is the second-level text on that "ended abnormally" message? What
preceded that message?

Please do printed output of the joblog and publish that here, at least a
few messages before this one.

Vern


On 7/3/2016 4:14 PM, Jack Tucky wrote:

I changed the Jobd, I don't see any joblogs generated.

The writer job is still active, here it is, but the write still shows
active. the ended abnormally appears after the document printed.

Job . . : JRLASER User . . : QSPLJOB Number

>> CALL QSYS/QSPWTRM1
The session with device JRLASER ended abnormally.

Here is my configuration for a dell 2135CN color laser. I've tried it
with
out IMGCFG(*IMGA06)

CRTDEVPRT DEVD(JRLASER) DEVCLS(*LAN) TYPE(3812) MODEL(1) +
LANATTACH(*IP) PORT(9100) ATTACH(*DIRECT) ONLINE(*YES) +
FONT(11 *NONE) FORMFEED(*AUTOCUT) SEPDRAWER(*FILE) +
PRTERRMSG(*INQ) MSGQ(*CTLD) ACTTMR(170) INACTTMR(*SEC15) +
LINESPEED(19200) WORDLEN(8) PARITY(*NONE) STOPBITS(1) +
TRANSFORM(*YES) MFRTYPMDL(*LEXMARKC750) PPRSRC1(*LETTER) +
PPRSRC2(*LETTER) ENVELOPE(*NUMBER10) ASCII899(*NO) +
IMGCFG(*IMGA06) CHRID(*SYSVAL) RMTLOCNAME('JROFFICE') +
SYSDRVPGM(*HPPJLDRV) +
TEXT('Dell 2135CN printer') +
PUBLISHINF(*UNKNOWN *UNKNOWN *UNKNOWN *UNKNOWN *BLANK +
(*UNKNOWN))

The code and DDS for Printer file are below. Code.midrange was saying
capttcha code was being tested.

The Fedex label shows correctly when I email myself the spool file
with
Gumbo's spoolmail.

Thanks for any help.

FPRTIMAGE O E PRINTER
D pos_T DS Qualified
D elem 5I 0
D top 5P 3
D left 5P 3
D imgSize_T DS Qualified
D elem 5I 0
D width 5P 3
D height 5P 3
C MOVE *ON *INLR
/free
data = 'This is the Image Print Test program';
imgDown = 1;
imgAcross = 1;
imgWidth = 4;
imgHeight = 6;
imgFile = 'label.jpg';
imgPath = '/tmp';
write text;
write image;
return;
/end-free

PRINTER FILE PRTIMAGE
A R TEXT
A DATA 56A 2
A SPACEA(1)
A IMGWIDTH 5S 3 1EDTCDE(2)
A IMGHEIGHT 5S 3 +1EDTCDE(2)
A IMGDOWN 5S 3 +1EDTCDE(2)
A IMGACROSS 5S 3 +1EDTCDE(2)
A SPACEA(1)
A IMGFILE 125A 1
A SPACEA(1)
A IMGPATH 640A 1
A SPACEA(1)

A R IMAGE AFPRSC(&IMGFILE *JFIF +
A &IMGDOWN &IMGACROSS
A (*PATH &IMGPATH) +
A (*MAPOPT *PT) +
A (*SIZE &IMGWIDTH &IMGHEIGHT))
A IMGWIDTH 5S 3P
A IMGHEIGHT 5S 3P
A IMGDOWN 5S 3P
A IMGACROSS 5S 3P
A IMGFILE 125A P
A IMGPATH 640A P

On Sat, Jul 2, 2016 at 9:50 PM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:

Thanks Jim.

Both similar dell printers configured the same. I was struggling that
there was no info in the writer job log. Since no printers are
working I
was focusing on the code. Going to change that Jobd now.

On Jul 2, 2016, at 8:52 PM, midrange <franz9000@xxxxxxxxx> wrote:

Jack,
In previous posts it was all about a Dell network printer.
We know nothing about your home printer to even begin discussing this.
Type of printer
Exact config
OS Version
Are you up to date with printing ptfs

Also, check printing joblogs WRKSPLF SELECT(QSPLJOB *ALL *ALL PE)
where

PE

is the printer name
If log not showing details, then change jobd QSPLPRTW (this is jobd
I

get

for a host print transform network printer) to log more detail
Message logging:
Level . . . . . . . . . . . . . . . . . . . . : 4
Severity . . . . . . . . . . . . . . . . . . . : 0
Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL
Log CL program commands . . . . . . . . . . . . : *YES

Btw - I would start with the joblogs - they may indicate exactly why
not
printing..

Jim Franz

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of

Jack

Tucky
Sent: Thursday, June 30, 2016 11:42 AM
To: Midrange Systems Technical Discussion
Subject: Re: Printing JPG's again

So something happened. Originally I was in my home office printing
the
JPEG's on my dell laser fine. I went to the office, tried to print on

their

printer and it would not work. I struggled a few days trying to get it

to

work.

I came home and it's not working on my printer either. Either I've
lost

my

mind or I changed something that broke it.

If I email the spoolfile to myself as a PDF it looks fine.

I noticed now that I'm back home my laser print starts printing

immediately

when I release the spool file. previously it would take 10-20 seconds
to
start printing, almost like it took awhile to send the data. Is there
something on the Printer device or setting on the IBM i that would
make

it

not send that data down?

Any help or ideas would be appreciated

On Thu, Jun 23, 2016 at 8:47 PM, midrange <franz9000@xxxxxxxxx>
wrote:

Try changing the printers job timeout (on the printer) to the max 300
seconds)
You may have such a tiny bit of memory in there the spool not
processed before timeout I've had to do that for many printers Jim

-----Original Message-----
From: midrange [mailto:franz9000@xxxxxxxxx]
Sent: Thursday, June 23, 2016 8:38 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Printing JPG's again

https://www-304.ibm.com/support/docview.wss?uid=nas8N1019652
Go down to "Error Messages for *LAN PJL Device Descriptions" and
click
to expand (I this web feature... IE sometimes hangs) Look for the
CPD337C - many possibilities

Good Luck
Jim

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of
Jack Tucky
Sent: Thursday, June 23, 2016 12:14 PM
To: Midrange Systems Technical Discussion
Subject: Re: Printing JPG's again

As soon as the page comes out, this error pops up in the writer
joblog

Message ID . . . . . . : CPD337C Severity . . . . . . . :
40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 06/23/16 Time sent . . . . . . :
12:13:45

Message . . . . : The session with device MIS240 ended abnormally.
Cause . . . . . : The session with the device at RMTLOCNAME

192.168.1.240

ended abnormally.

On Thu, Jun 23, 2016 at 11:54 AM, Buck Calabro <kc2hiz@xxxxxxxxx>
wrote:

On 6/23/2016 11:28 AM, Jack Tucky wrote:

Thanks for that link Jim. My printer that works (2135cn) and the
one

here

(5100cn) both have the same properties in the list.

Here is my printer configuration. I'm lost right now.

CRTDEVPRT DEVD(MIS240) DEVCLS(*LAN) TYPE(3812) MODEL(1) +
LANATTACH(*IP) PORT(9100) ATTACH(*DIRECT) ONLINE(*YES) +
FONT(11 *NONE) FORMFEED(*AUTOCUT) SEPDRAWER(*FILE) +
PRTERRMSG(*INQ) MSGQ(*CTLD) 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.1.240')
+
SYSDRVPGM(*HPPJLDRV) +
TEXT('Testing Dell printer') +
PUBLISHINF(*UNKNOWN *UNKNOWN *UNKNOWN *UNKNOWN *BLANK +
(*UNKNOWN))

WRKWTR, then F17 to see the writer job, then option 10 to look at
the job log. If IBM i is diagnosing something, it should be in
there.
Otherwise, it's probably on the printer's side.

To that end, I see that the 5100cn allows Postscript - is the
printer somehow stuck in that mode as opposed to PCL mode?

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page
that helps you, and because it's public, you'll help someone else,
too!

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
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.
Please contact support@xxxxxxxxxxxx for any subscription related

questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related

questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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.