Re: Repeitive device messages

Sorry, canot help you here, but have encountered the same problem and
thought of the same solution.

Till the system crashed, because system was full.

Messages are written to the system log. So the HSTLOG files will multply
rapidly.

Just a warning.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 5-8-2010 at 15:39 jmmckee wrote:

A printer was set up some time ago as a remote output queue. User

complained that output was not being printed. Best guess is because this

printer is a Lexmark and receives data from other sources. My thought was

that the printer was just ignoring data if it was busy printing from

another system. So seemed like a printer device would be the answer.

First issue was adding a reply list entry to handle the forms change

message. I thought that was it.

Yesterday, user called again with the same complaint. I checked QSYSOPR

for unanswered messages. And, there was a "Device requires attention (C

R)" message. After entering R, the queue emptied almost immediately.
Best guess is that the Lexmark ran out of paper. More paper was added,

but that unanswered message let things get backed up. The user does not

keep a session active all the time, so that is why Isent the messages to

QSYSOPR. But, the operator does want to deal with beginner mode. Must

better to just ignore all errors. Really ticks me off. User requested

returning to a remote output queue.

I had one other idea - a reply list entry for that printer to answer with

R. Kind of works. Problem is that message is sent perhaps every fifteen

seconds until the issue is resolved.

Best approach would be to get the operators to care. But, that seems

unlikely. So, now this question: Is there a way to suppress a duplicate

error message from being sent to QSYSOPR?