On Wed, 21 Dec 2016 09:50:18 -0500, Charles Mills wrote: > >> when you say "despatch", I think "mail room" or "loading bay". As plain as >> possible is fine with me. > >Perhaps not quite the official explanation but dispatch = your task getting >control/usage of a CPU: the last time your program "woke up." I would say that >if you are measuring the CPU time used in some large span of code including >I/O then the CPU time figure will be pretty good. If you are measuring how >long it took you to compute pi to ten digits, then you could conceivably end >up with zero, because it was all computed since you "got" the CPU most >recently. > I had pondered this issue in the past and decided that the most useful, though not the most simply usable, value to store in the CVT is CPU time used minus TOD clock value at time of dispatch. Then the programmer could STCK(F), add that magic value in the CVT, and get instantaneous CPU time used. Yes, I know there's a timing window and that it can be shut with more code.
>Perhaps others here have a strategy for forcing a new dispatch. Does the >TIMEUSED macro force a dispatch? > I mentioned, perhaps not in time for Bill to read, a colleague who used a neutral Change Priority SVC to force dispatch. --gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
