So here is the latest, and strangest development

We replaced the cables, moved where it was plugged into the network
CHANGED THE PHYSICAL PRINTER & NETWORK CARD!!!

Still the same problem

I compared the printer setup to other printers at the same site (that work OK) and it was all exactly the same.

I deleted the printer from the system and recreated it as a Wrtier (rather than an output queue).RESULT!!
Prints send OK and print immediately.

The problem, at the moment, is that the users now need to answer a ‘is the correct paper in’ message each time they print – and as we all know – they don’t like that sort of thing

I have an automatic reply entry set up, but I am assuming the program (invoice printing) is ignoring this list, due to it’s set up

Does anyone know how to get a program to point to the reply list?

Thanks

Kas

No need to use the system reply list.

When you create the writer, specify *INFO for the Printer error message parameter.
PRTERRMSG(*INFO)
(The default is *INQ).
Specifying *INFO will not send messages that need a reply.

The upside is that you only have to respond to ONE message when you first start the writer. It should be a “load form type” message and you respond with “G”.
The downside is that if the printer has an issue (out of paper, out of toner, paper jam, etc) they only way you know is by physically checking the printer.

Of course, I have had users report they didn’t get thier reports, and it turned out the printer was out of paper. Go figure…

And, remote outqueues do tend to go to sleep. We have somewhere arount 250 printers around the country and all are defined as writers. No problems.

Regards
Mike

Well, I’ve decided I’m going to ritually burn this printer as it is now driving me nuts.

After changing the messages tp *INFO, the printer still is sititng with MSGW at the first print, BUT

When you answer G (to go), the printer ends with message ID CPD337C – The session ended abnormally.

I’ve chanegd the message back to *INQ

The device set up is :

Device description . . . . . . . . : PROPRT03
Option . . . . . . . . . . . . . . : *BASIC
Category of device . . . . . . . . : *PRT

Device class . . . . . . . . . . . : *LAN
Device type . . . . . . . . . . . : 3812
Device model . . . . . . . . . . . : 1
LAN attachment . . . . . . . . . . : *IP
Port number . . . . . . . . . . . : 9100
Physical attachment . . . . . . . : *DIRECT
Online at IPL . . . . . . . . . . : *YES
Font:
Identifier . . . . . . . . . . . : 11
Point size . . . . . . . . . . . : *NONE
Form feed . . . . . . . . . . . . : *CONT
Separator drawer . . . . . . . . . : *FILE
Separator program . . . . . . . . : *NONE
Printer error message . . . . . . : *INQ
Message queue . . . . . . . . . . : *CTLD
Current message queue . . . . . . : QSYSOPR
Library . . . . . . . . . . . . : QSYS
Activation timer . . . . . . . . . : 300
Inactivity timer . . . . . . . . . : *NOMAX
Line speed . . . . . . . . . . . . : 19200
Word length . . . . . . . . . . . : 8
Type of parity . . . . . . . . . . : *NONE
Stop bits . . . . . . . . . . . . : 1
Host print transform . . . . . . . : *YES
Manufacturer type and model . . . : *IBM2391
Paper source 1 . . . . . . . . . . : *NONE
Paper source 2 . . . . . . . . . . : *NONE
Envelope source . . . . . . . . . : *NONE
ASCII code page 899 support . . . : *NO
Image configuration . . . . . . . : *NONE
Character identifier . . . . . . . : *SYSVAL
Remote location:
Name or address . . . . . . . . : 10.44.14.10

It is an Espon DLQ3500, with continuous paper, with an internal Espon Network card.
Network card timeouts are all set to 3600 seconds

This is the same setup as other machines on the system, which is why I just cant figure out what it does not behave on the same way.

Thanks for all your help so far

Kas

Hello KasMcc – we have a very similar setup where we use an output queue with no device description. We also setup system reply entries as shown below. To the best of my knowledge, nothing special needs to be coded in the output queue to use the system reply list.

                      Work with System Reply List Entries                   
 Type options, press Enter.                                                 
   2=Change   4=Delete                                                      
                                                                            
      Sequence  Message                                              Compare
 Opt   Number   ID       Reply       Compare Value                    Start 
        4008    CPA3394  G           'SACHP4'                            1  
        4009    CPA3394  G           'RKSCHPT'                           1  
        4010    CPA3394  G           'COADPR2'                           1  
        4011    CPA3394  G           'COSLSPR1'                          1  

We had the same troubles you describe when using a device description with an HP 4250 laser jet. When we re-configured with just a remote output queue, it stopped stopping in the middle of a print job.

Hi friend’ i think this may help you little
8983237, Configuring a Remote Output Queue (RMTOUTQ): Database ‘Rochester Support Line KnowledgeBase’, View ‘All DocumentsAll Software’, Document ‘ Configuring a Remote Output Queue (RMTOUTQ)’
24291009, Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer: Database ‘Rochester Support Line KnowledgeBase’, View ‘Personal ViewsDocuments Needing Your Attention’, Document ‘Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer’
438924552, Configuring a Remote Output Queue (RMTOUTQ) to a Windows Print Queue: Rochester Support Center KnowledgeBase
24305723, Configuring a Remote Output Queue (RMTOUTQ) to Another IBM System i System Using TCP/IP: Database ‘Rochester Support Line KnowledgeBase’, View ‘Personal ViewsDocuments Needing Your Attention’, Document ‘Configuring a Remote Output Queue (RMTOUTQ) to Another iSeries or AS/400 System Using TCP/IP’
————————————-
Harris of USA ,<a href=”http://www.cwnacertification.net”>cwna</a>

If memory serves . . . IBM has released some PTFs with cover letters which mention the problem you are experiencing. Might be worth installing the latest PTF groups for printing and TCP/IP.

Strprtwtr might be started with default message *INQ

I’d suggest checking the manufacture website to confirm if you can reload/upgrade the firmware for the printer.

I’ve had moments like this with brand new equipment out of the box and usually I find that once they know you’re printing to an IBM i they’ll pause and then ask you what version of software/firmware is running on the printer.

Even printer don’t come with a 100% success rate out of the box.

I have an Epson DLQ3500 printer set as a remote OUTQ.

And later:

I’ve checked the addresses, recreated the device,…

First thing I’d have wondered was if it was being used as a “remote OUTQ” or as a “device”.

I don’t think I’ve ever seen a printer accessed both ways, at least not concurrently. I suspect that there might have been some general confusion of terms or concepts.

Tom

Thanks for all the help on this one.
The latest news is that the site in question has moves, on Thursday, from AS400 to an IFS system running on managed servers – So no more printer.

We are also moving from AS400 (Bah) in November to managed servers running MS Dynamics. So no more need for any remote writers or outq’s

Thanks again for all your help

I am also have the same above problem, can someone give us a solution
Thanks
AVI