RE: More Severe DSTQ in RTY-FAIL Notification needed

I am unaware of any SNADS APIs, so I would create a program that would loop
every several seconds/minutes/hours, doing the following:


WRKDSTQ QUEUE(*ALL) OUTPUT(*PRINT) /* You may want a specific name */
CPYSPLF /* Copy spooled file to a PF */
Interrogate this PF with your favorite tool/language. If condition found,
send *INQ message or similar.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Some folks are born fools, but the majority of us become so through
practice.

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