CPF1164 shows up the CPU used for the complete job at job end time, it's
presenting the same as dspjob for a still running job. CPU used does not
contain lock waits, dasd i/0 (swapping included). But there might be parts
not related directly to your programm instructions. There is system workload
done for your job, most of this could be neglected (moving your job between
the diffrent queues etc.) in case of using SQL this might be diffrent, but
this could be neglected. The query optimizer might choose diffrent access
plans in diffrent situations and building a temporary index would be part of
the job.
For your situation: if your programms of this job are using SQL, you can't
be sure from one run, if the change to the programm was appropriate or not,
but if you have some runs to compare, you could.
CPF1124 (Job start) and CPF1164 (Job end) could be retrieved by dsplog
msgid(cpf100) output(*print) and are giving a big picture wether a job is
cpu bound or i/o bound and might be a good starting point for performance
analysis to find critical jobs.
Dieter
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.
midrange.com
