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



A little more experimenting (since I obviously don't know what I'm doing I'm
kinda limited to experimentation-mode).

I deleted the device description which, apparently, also deleted the output
queue. Recreated the device description (using the CL below). After
starting the writer, WRKCFGSTS showed status of Active/Writer. Test print
did *not* print (Status = RDY).

Next, I tried to print a test page from both TextPad and NotePad. Both
failed to print. Canceled them from the PC's writer (or whatever it is).

However, WORD and Excel documents print. But the writer on the System i
goes to END status and WRKCFGSTS simply shows Varied On. Test pages from
TextPad and NotePad will now print.

Jerry C. Adams
IBM i Programmer/Analyst
Anyone can be elected governor. I'm proof of that. - Joe Frank Harris,
Georgia governor
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, June 30, 2011 9:34 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Printer Configuration Not Working

I don't know what it's telling me, but I see this error six [6] times in the
job logs, all with the same time stamp.

I double-checked the IP address (10.1.10.199) and port (9100) through the
Windows printer properties.

*NONE Request 06/30/11 08:04:56 QWTSCSBJ
*N QCMD QSYS 0173
Message . . . . : -CALL QSYS/QSPWTRM1

CPD337C Diagnostic 40 06/30/11 08:08:13 QWPPJLDR
QSYS *STMT QWPPJLDR QSYS *STMT
From module . . . . . . . . : WPPJLDR

From procedure . . . . . . :
Socket_Recv
Statement . . . . . . . . . : 25

To module . . . . . . . . . : WPPJLDR

To procedure . . . . . . . : _C_pep

Statement . . . . . . . . . : *N

Message . . . . : The session with
device CR ended abnormally.
Cause . . . . . : The session with
the device at RMTLOCNAME 10.1.10.199
ended abnormally. Recovery . . . :
Check for problems in the network or
at the remote device. Start the
printer writer again. If the problem


Jerry C. Adams
IBM i Programmer/Analyst
I don't see, Mr. Speaker, why we should put ourselves out of the way to
serve posterity. What has posterity ever done for us? - Sir Boyle Roche
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis
Sent: Thursday, June 30, 2011 8:28 AM
To: Midrange Systems Technical Discussion
Subject: Re: Printer Configuration Not Working

Nice documentation!

At that point, I would do WRKJOB (writername), and view the joblog for any
of the ended jobs. Something in there should stand out for you.
--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my
brevity.

"Jerry C. Adams" <midrange@xxxxxxxx> wrote:

I am having trouble getting a LAN printer configured and working as a
System
i printer. The information below may be overkill, but I'm at a loss as
to
how to proceed. We are on V5R1, and I can print to the printer (HP
LaserJet
4050) from PC programs. So I thought we could use it as a System i
(AS/400)
printer. Maybe I'm in error, but.



I created the outq:



CRTOUTQ OUTQ(QUSRSYS/CR) AUTOSTRWTR(1) MFRTYPMDL(*IBM3812)



I created the device description:



PGM



DLTDEVD DEVD(CR)

MONMSG MSGID(CPF2105)



CRTDEVPRT DEVD(CR) DEVCLS(*LAN) TYPE(3812) MODEL(1) +

LANATTACH(*IP) PORT(9100) ATTACH(*DIRECT) +

ONLINE(*YES) FONT(011 *NONE) +

FORMFEED(*AUTOCUT) SEPDRAWER(*FILE) +

PRTERRMSG(*INQ) MSGQ(QUSRSYS/AJERRY) +

ACTTMR(170) INACTTMR(*SEC15) +

LINESPEED(19200) WORDLEN(8) PARITY(*NONE) +

STOPBITS(1) TRANSFORM(*YES) +

MFRTYPMDL(*HP4000) PPRSRC1(*LETTER) +

PPRSRC2(*MFRTYPMDL) ENVELOPE(*MFRTYPMDL) +

ASCII899(*NO) IMGCFG(*NONE) +

CHRID(*SYSVAL) RMTLOCNAME('10.1.10.199') +

SYSDRVPGM(*HPPJLDRV) PUBLISHINF(*UNKNOWN +

*UNKNOWN *UNKNOWN *UNKNOWN *BLANK) +

TEXT('Conference Room')



GRTOBJAUT OBJ(CR) OBJTYPE(*DEVD) USER(QTCP) AUT(*EXCLUDE)

CHGOBJOWN OBJ(CR) OBJTYPE(*DEVD) NEWOWN(AJERRY)



ENDPGM



iNav's Work Management for outqueue CR shows 1 writer started.



WRKWTR shows writer CR with a status of STR and the test print is
visible
when I use option 8 (Work with output queue). Option 5 (Work with)
shows:



Writer . . . . . . . : CR User . . . . . . . . :
QSPLJOB

Number . . . . . . . : 025610




Started by user . . . . . . . . . . . : AJERRY


Status:


Writing . . . . . . . . . . . . . . : N

Waiting on message . . . . . . . . . : N

Held . . . . . . . . . . . . . . . . : N

End pending . . . . . . . . . . . . : N

Hold pending . . . . . . . . . . . . : N

Between files . . . . . . . . . . . : Y

Between copies . . . . . . . . . . . : N

Waiting for data . . . . . . . . . . : N

Waiting for device . . . . . . . . . : N

On job queue . . . . . . . . . . . . : N

File being written . . . . . . . . . . :

File number . . . . . . . . . . . . :

Job that created file . . . . . . . . :

User . . . . . . . . . . . . . . . :

Number . . . . . . . . . . . . . . :

Page being written . . . . . . . . . :

Total pages . . . . . . . . . . . . . :

Copies left to produce . . . . . . . :

Total copies . . . . . . . . . . . . :

Device . . . . . . . . . . . . . . . . : CR

Printer device type . . . . . . . . . : *SCS

Number of separators . . . . . . . . . : *FILE

Drawer for separators . . . . . . . . : *DEVD

Allow direct print . . . . . . . . . . : *NO

Align page . . . . . . . . . . . . . . : *WTR

Initialize Printer . . . . . . . . . . : *WTR

Output queue . . . . . . . . . . . . . : CR

Library . . . . . . . . . . . . . . : QUSRSYS

Output queue status . . . . . . . . . : RELEASED

Form type . . . . . . . . . . . . . . : *ALL

Message option . . . . . . . . . . . : *INQMSG

Automatically end writer . . . . . . . : *NO

Message queue . . . . . . . . . . . . : AJERRY

Library . . . . . . . . . . . . . . : QUSRSYS

Changes pending:

Next output queue . . . . . . . . . :

Library . . . . . . . . . . . . . . :

Next form type . . . . . . . . . . . :

Message option . . . . . . . . . . :

Next file separators . . . . . . . . :

Next separator drawer . . . . . . . :

Changes take effect . . . . . . . . :





WRKOUTQ shows:



Queue Library Files Writer Status

CR QUSRSYS 1 CR RLS



Option 5 (Work with) shows:



File User User Data Sts Pages Copies Form Type
Pty

QPSUPRTF AJERRY RDY 1 1 *STD
5



Option 9 (Work with printing status) shows:



Status Description

This file is not associated with a started printer.

When I then use WRKWTR CR's status is END, whereas earlier it was STR.
So I
started it.

Then the Work with printing status shows (Status is pending).

While typing parts of this message, the writer's status went to END.



In the past all I have ever had to do was create a device description.
The
output queue mysteriously (to me, anyway) gets created and everything
(usually) works fine (with a little fine tuning on some rare
occasions).



Thanks.



Jerry C. Adams

IBM i Programmer/Analyst

--

A&K Wholesale

Murfreesboro, TN

615-867-5070



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

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.