Monitoring the QSYSOPR message queue -- MIDRANGE-L

× 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.

Subject: Monitoring the QSYSOPR message queue
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 09 Aug 2010 17:05:47 -0700
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>

I just made an interesting discovery:

If I have a CL program monitoring QSYSOPR for messages (using a RCVMSG command), that message queue then behaves like the user message queue of a signed-on user, in that you can't delete QSYSOPR messages.

I don't suppose there's an easy way for a CL program running in a batch job to monitor the QSYSOPR message queue without actually tying it up?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Monitoring the QSYSOPR message queue , Dennis Lovelady

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.