The only requirement is that it be unique within the task, and that is all
that we would ever consider documenting.
If we ever needed to worry about the 4G wrap, or a hot cache line updating the
current system wide count,
the solution would be to go to an address space count in the ASSB or a task
count in the STCB.
If Peter Relson were still at IBM, he would likely have already admonished me
for mentioning the current implementation,
instead of just saying that the answer to the question of "is it unique with a
task" is "yes".
Jim Mulder
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Paul Gilmartin
Sent: Monday, January 27, 2025 2:49 PM
To: [email protected]
Subject: Re: Is the STIMERM ID= guaranteed to be unique within the task?
On Mon, 27 Jan 2025 18:14:43 +0000, James Mulder wrote:
> Other than 4G wrap, STIMERM ID= is unique within the z/OS image.
>
This implies that from any starting point the sequence of IDs returned by
STIMERM is strictly periodic with a period or 4G
Should this guarantee be documented in:
<https://www.ibm.com/docs/en/zos/3.1.0?topic=timer-description>
...
ID=stor addr
Specifies the address of a 4-byte area containing the identifier
assigned to a particular timer request by the timer service routine.
...
to anticipate the answer to the original question?
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
