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