×
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.
sign on then CHGMSGQ QSYSOPR DLVRY(*BREAK) this allocates the QSYSOPR
message queue to that session and sets it to send the break messages to
that screen.
Thanks,
Tommy Holden
From:
Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
08/12/2008 12:48 PM
Subject:
Re: How do you manage your QSECOFR profile and other Q profiles?
On Mon, 11 Aug 2008 12:52:09 -0700, "Chris Bipes"
<chris.bipes@xxxxxxxxxxxxxxx> wrote:
I don't think we have ever
signed on as QSYSOPR,
Several people have mentioned this. Our Operators do sign on as QSYSOPR
and
I've been trying to change this. The argument they always come up with is
that it is easier to monitor the QSYSOPR message queue. If they sign on
as
QSYSOPR and a break message is sent, they see it. If they were signed on
as
something else, they would not see the messages unless and until they did
a
DSPMSG.
For those shops that don't use the QSYSOPR userid, how do you handle
monitoring the message queue?
Gord
midrange.com
