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

[fiona.fitzgerald@xxxxxxxxxxxxxxxxxx]

Another quick solution would be to make your message q the one to receive
any
inquiry messages for that job.
(Just check that the operators know to monitor your msgq when you are
on holiday.)

To do this, when Submitting the job, include the parameter MSGQ;
SBMJOB  QBLOCKER      MSGQ("PRYCEJ")

Then keep your own msgq in break mode.

OK ?
Fiona





"Pryce Jones" <jonesp@quinn-group.com>@midrange.com> on 05/02/2001 16:57:43

Please respond to <MIDRANGE-L@midrange.com>

Sent by:  <owner-midrange-l@midrange.com>


To:   <MIDRANGE-L@midrange.com>
cc:
Subject:  Checking a JOBQ to see if there are jobs waiting


"THIS MESSAGE ORIGINATED ON THE INTERNET - Please read the detailed
disclaimer below"

----------------------------------------------------------------------

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.



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



----------------------------------------------------------------------
The following message has been automatically added by the mail gateway
to comply with a Royal & Sun Alliance IT Security requirement:

"As this email arrived via the Internet you should be cautious about
its origin and content. Replies which contain sensitive
information or legal/contractual obligations are particularly
vulnerable. In these cases you should not reply unless you are
authorised to do so, and adequate encryption is employed.

If you have any questions, please speak to your local desktop
support team or IT security contact".
----------------------------------------------------------------------



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---