|
You could check the users interactive log to see what it might provide. You can also look at the job completion message (CPF1164 I believe). It will give amount of CPU time taken. For example, if you submit a job that does nothing it will 'use' 1 second of CPU time. This at least should give you some comfort level as to how much it was doing. If you have job accounting on you get get more job statistics (io counts, etc.). We had an occurrence this morning in which over 200 instances of the same job were submitted to QBATCH and completed in a 10 minute time frame by one user. All jobs had the same job name (not a typical job name for our environment either) and produced no output or joblogs. The information in QHST is minimal and does not tell me what these jobs could have been. +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@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.