×
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.
Y'all
The job completion messages (CPF1164) in the history log files have a
lot more information than you see in the job log. Lots of statistics.
The printed output of DSPLOG gives you the basics, and that might be
enough for the OP.
To see the rest, one has to look at the records in a QHST* file - it
actually extends across more than one record. The layout is in Work
Management documentation and CL Programming, chapter 8. It is part of
processing messages. Here is a hint of what is available -
Job accounting provides more information than CPF1124 and CPF1164. For
simple
job accounting functions, use the CPF1164 message.
Performance information is not displayed as text on message CPF1164.
Because the
message is in the QHST log, users can write application programs to
retrieve this
data. The format of this performance information is as follows.
The performance information is passed as a variable length replacement
text value.
I've done some work with this several years ago - getting the QHST files
in order is one challenge. The other is putting the data together from
multiple records per message. All doable.
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
midrange.com
