The line in the joblog states



Job 999999/UUUUUUUUUU/JJJJJJJJJJ ended on 06/12/15 at02:36:42; 430.362
seconds used; end code 0



I have always thought this was CPU seconds used to execute the job but some
questions have come up to make me wonder if it is more than that.



For example,

1) If the system is really bogged down and doing a lot of swapping,
does the CPU time spent swapping get added to this?

2) If the DASD is really bogged down, does that have any effect on this
number?

3) If there is a lock of a record and the program is in a LCKW state,
does that add any CPU overhead to my job (not sure if my program goes to
sleep and the OS wakes it up when the lock frees or if my program is
checking the lock status behind the scenes)?



Can someone provide a good explanation of this number and what else if
anything other than my program instructions are included in it?








As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.