QSYSOPR message queue security -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: QSYSOPR message queue security
From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
Date: Tue, 12 Mar 2013 09:37:35 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSYSOPR message queue security , Michael Schutte
RE: QSYSOPR message queue security , Willie J. Moore

This mailing list archive is Copyright 1997-2026 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.