On Mon, 19 Feb 2024 21:54:56 -0600, Charles Mills <[email protected]> wrote:
> has recently issued an STCK and your program must spin, consuming CPU cycles, > until a unique STCK value is available. This is being made far more difficult than needed. The vast majority use nano seconds for monotonic code rather than serving a real purpose. System z is already at 1,000 instructions per nano second (200 cores times 5 Ghz) and sysplex apps can boost that up to 32,000 instructions per nano second. Anyone using this strategy is not Quantum ready where nano seconds become irrelevant. Why bother with the clock at all? Why bother with spin? The simple solution is a counter that is incremented. Using PLO, CS, CSD, CSDG or ENQ to serialize updates to the counter, you can easily handle a counter larger than the TOD. E.g. CSDG serializes 128 bytes. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
