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)start with performance investigation of batch jobs...
shows up job start, job completion and cpu time, tht's what I use to
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact