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