Frankly I have no use for nor desire to use any “functional” languages
whatsoever. Let those with the interest and need make their case, but my
current wish does not include such languages, nor many other extant or historic
languages.
Peter
From: IBM Mainframe Discussion List On Behalf Of
On Sun, 18 Feb 2024 21:50:07 -0600, Peter Farley wrote:
>
>There is an entire sub-section in the PoOps in the Control chapter
>(SA22-7832-13, pp. 4-51 et al., starting most of the way down the second
>column of that page) about the monotonicity guarantees for STCK{E/F}, even on
>multiple CPU's.
> Have you looked at the FORMATTED-TIME function?
Thanks Paul, I did look at the FORMATTED-TIME function, but the finest
resolution offered by that function is tenths of milliseconds (four fractional
decimal digits), not even micro-seconds (which would require six fractional
decimal digits).
>What guarantees uniqueness other than STCT(E)? Does the Sysplex Timer/ETR
>guarantee
>uniqueness across the plex?
>
>And monotonicity is a harsher constraint. In the Bad Old Days when each CPU
>had its own
>TOD and uniqueness was achieved by putting the CPU ID in the TOD programmable
>field
Peter, I'll start up saying I don't have access to a system that I can try this
on.
Have you looked at the FORMATTED-TIME function? This looks to be part of COBOL
6.3. My concern would be that you still might not get the uniqueness you are
looking for.
FORMATTED-TIME: The FORMATTED-TIME
On 2/18/2024 6:34 PM, Paul Gilmartin wrote:
What guarantees uniqueness other than STCT(E)?
I assume you mean STCK{E}?
Does the Sysplex Timer/ETR guarantee uniqueness across the plex?
No. The unique TOD fields for each system in the sysplex are set by the
SCKPF instruction as documented in
On Sun, 18 Feb 2024 18:22:53 -0600, Peter Farley wrote:
>
>The only HLL-callable function already provided in z/OS that I can find that
>provides anything near that resolution is the LE Callable Services function
>CEEGMT, but two calls to that service from a COBOL program in a row separated
>by
I have been reviewing all the documentation I can find to provide nano-second
resolution timestamps from a calling HLL batch program. STCK and STCKE
instructions of course provide this (and more) resolution, but using them from
any HLL besides C/C++ requires an assembler subroutine (however
