It might be said that the notion of monotonicity with respect to clock values is not "valid" unless you are a single-threaded application or all your references are serialized across all the threads (such as by a step- or system- or systems-level ENQ depending on the characteristics).
Otherwise you cannot possibly tell what is what because thread one might have captured clock value "n" and then gotten interrupted, and then thread two captured clock value "n+1" and then continued to completion, after which thread one was re-dispatched (with what is now an older time stamp than the one already captured). If these two threads were serialized by an ENQ against each other the above scenario would not happen because thread two would not have been able to get to the point of capturing its clock value. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
