Your's was the case when I first arrived here, and I changed it because;
1) Too many message on QSYSOPR to find the really important messages, even
though they may not need an answer.
2) We auto answer operator message on some printers/writers. For paper out
and jams, the auto answer keeps retrying until the operator fixes the
problem, then they don't have to find the correct message and answer it.
Had too many answering wrong or answering for the wrong printer.
One thing we found is that the message queue would fill up and halt some
jobs. We have a job that runs 45 times a day that, in part, clears
answered messages from message que ALLWTRMSG.
Western Power Sports
On Tue, Mar 25, 2014 at 5:41 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>wrote:
I had a brainstorm last night and cannot believe I didn't do this years
The message queue for all our printers is QSYSOPR. All the paper out,
change labels, etc, go there. Why don't I set up a message queue
specifically for these messages, say PRTMSGS. Someone can monitor this
queue and it takes the print messages out of QSYSOPR.
Does anyone else already do this? Is there a downside I'm not thinking of?
Years ago we had a printer at the far end of the office away from the
system operator and I had it's messages go to a users message queue without
issue. Never thought of a message queue dedicated to printer messages
VP Information Systems
P.O. Box 13369
Ft. Wayne, IN 46868-3369
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives