I think what the OP meant was that TIMEUSED was giving back a value greater than the end-time STCK minus start-time STCK recorded in his code. I would guess this might be possible in a multi-CPU environment where more than one unit of work in the address space is running on more than one CPU, simultaneously. (yucky phrasing) But I could be wrong about that interpretation of his original message, of course.
On Wed, 2011-02-02 at 14:46 -0800, Edward Jaffe wrote: > On 2/2/2011 2:35 PM, Micheal Butz wrote: > > Using STCK as Wall time and TIMEUSED as CPU time without any Parms > > (TIMEUSED) > > defaults to TOD > > Format I am finding TIMEUSED > STCK. ???? I have before and after pair for > > each > > TIMEUSED cannot be greater than current TOD returned by STCK. Think about it. > TOD clock (STCK) has been counting since Jan 1, 1900 at 0 AM. TIMEUSED has > been > counting only since your unit of work started. > -- John McKown Maranatha! <>< ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
