×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
To add to my previous post - the information on QHST is also in Work
Management manual, chapter 5 - there's a specific section on using the
CPF1164 message in the history log when you don't have a job log.
I have said in this thread that finding hanging jobs isn't easy to
determine. I'm thinking that the history logs might give a hint - find
jobs for which there is a CPF1124 and NOT a CPF1164 - these would be
candidates for hung jobs of some kinds, I think.
HTH
Vern
On 1/28/2013 11:21 PM, D*B wrote:
dsplog msgid(cpf1100) output(*print)
shows up job start, job completion and cpu time, tht's what I use to start with performance investigation of batch jobs...
D*B
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.
midrange.com
