I don't know, but if you have a job log print file for that job, look at start and end times -
a little math should answer your question and, if memory serves, the job log shows net
cpu seconds.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John R. Smith, Jr.
Sent: Friday, June 19, 2015 12:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Seconds used question
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?
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
