×
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.
We created a CL (MSGQCL). It is called by entering a command (MSGQ) on the message line.
You could add it to her menu also.
William...
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Tuesday, March 12, 2013 6:38 AM
To: Midrange Systems Technical Discussion
Subject: QSYSOPR message queue security
Every day our billing clerk serves as the de facto system operator. When
she comes in she does a CHGMSGQ QSYSOPR *BREAK SEV(30) so that any QSYSOPR
messages break to her.
Today she accidentally cleared QSYSOPR. Not a catastrophe but we don't
want repeats.
A google search indicated that removing the *DLT authority would prevent
her from deleting messages or clearing the queue. Great, except she then
was not allowed to do the CHGMSGQ QSYSOPR *BREAK SEV(30). Catch 22!
Anyone know a Q&D way around this?
Thanks.
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.
midrange.com
