|
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Friday, July 30, 2010 9:11 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: More Severe DSTQ in RTY-FAIL Notification needed
We have an important DSTQ that sometimes goes into RTY-FAIL without me
(QSYSOPR) knowing about it. It seems that at most, there will be one
message to QSYSOPR and it's easy to overlook because it's not a break
message and it'll be intermixed with other messages.
Thus, the queue can sometimes be in RTY-FAIL for days without me
knowing
about it. I know that to fix it I need to put the queue on hold and
then release it, but how do I get more frequent messages that it's in
RTY-FAIL in the first place? Is this something that needs to be done
in
the individual programs calling for a SNDDSTQ?
Bryan Burns
ECHO I.T. Department
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.