Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Newsgroups: comp.os.vms
Subject: Re: Timer resolution for sys$setimr() ?
Date: Thu, 5 Dec 2024 13:05:00 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <vis8ds$1k8d9$1@dont-email.me>
References: <viplvd$ssu1$3@dont-email.me> <67506eb6$0$712$14726298@news.sunsite.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 05 Dec 2024 14:05:01 +0100 (CET)
Injection-Info: dont-email.me; posting-host="cdb7058d214566366f84edd6bbc3df71";
	logging-data="1712553"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+nfd2udKsNM/DsHBvuOgzICnN/3ZIGSuc="
User-Agent: slrn/0.9.8.1 (VMS/Multinet)
Cancel-Lock: sha1:xtPbWfGUFD0Kaq3h1DBNy2b/YEI=
Bytes: 1916

On 2024-12-04, Arne Vajhøj <arne@vajhoej.dk> wrote:
> On 12/4/2024 8:37 AM, Simon Clubley wrote:
>> What is the actual resolution of timer events queued using the
>> sys$setimr() system service ?
>> 
>> NOTE: this is about when the timer becomes eligible to fire, not when
>> it actually does, given that VMS is not a hard RTOS.
>> 
>> The base VMS time format is in 100ns units, but I couldn't see anything
>> about the units actually used when firing timer events. Is it the same
>> as the hopeless terminal driver timeouts, or is it 100ns, or is it
>> something in between ?
>
> IDS VMS Alpha 1.5 (30 years old!) says:
>

[snip]

Thanks Arne. I never even thought to check the I&DS as this was something
I was expecting to find in the normal user documentation.

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.