RE: Checking a JOBQ to see if there are jobs waiting

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Title: RE: Checking a JOBQ to see if there are jobs waiting

There is an old TAATOOL, RTVJOBQA with a parm NBRJOBS.  This will return the number of jobs on a job queue.  If you have it or the source, it could be a place to start.  There are also API's, QSPRJOBQ is retrieve job queue information.

HTH,

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.  Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Pryce Jones [mailto:jonesp@quinn-group.com]
Sent: Monday, February 05, 2001 8:58 AM
To: MIDRANGE-L@midrange.com
Subject: Checking a JOBQ to see if there are jobs waiting

Hi People,
After searching through the archives and not getting anywhere I wonder if I
can throw a problem passed you to see what we can come up with.
Problem: We have one jobq where loads of jobs are sent to and normally this
is fine for what we require. However, on occasion, the job that is running
from the jobq (we only allow one as there are dependencies) has either
stopped because of a msg (and the operations team have not spotted it) or
the job is running very slow and taking up all resources (perhaps a monster
query is running), etc, etc .... you get the idea - it is not something that
we can normally forsee and program around. What I am looking to do is
something like throwing a "wrkjobq qbatch" to spool, doing a cpysplf to a
temp file and then retrieving the number of records. If over 2 then there
could be a problem so send msg to Me (not ops!). This is a "dirty" option
and there are a couple of prblems even with this solution. Has any one done
similar. :)
Thanx,
Pryce.