[Info-vax] CPU/Core temp reporting anomaly

[IanMiller]

On Feb 14, 7:36 pm, Rich Jordan <jor... at ccs4vms.com> wrote:
> Has anyone had issues using the "TEMPERATURE_VECTOR" argument to F
> $GETSYI()?  I've got a polling monitor running on a DS10 (VMS V7.3-2)
> that reports 41 - 43C steadily for hours to days, then suddenly
> reports a temp of 254C for one poll, then drops back to normal.  We're
> using this as an stopgap environmental monitor until the facility
> fixes the A/C and temp alerts that failed late last week.
>
> The line extracting the temperature is:
>
> $ TEMP = F$INTEGER("%X''F$EXTRACT(30,2,F
> $GETSYI("TEMPERATURE_VECTOR"))'")
>
> This has been running fine on a home DS10-L for years; I just built a
> procedure around it to alert via email if limits were exceeded.  The
> DS10-L never had this occur (but was running V8.2 or later).  Its
> certainly possible this is a V7.3-2 issue (and the box cannot be
> upgraded at this time).  I do know it is responsive since the code
> also ran on the work DS10-L when it had its rear fan failure
> (discussed here some weeks ago) and it clearly followed the rising and
> falling temps as the fans were switched in and out  (the rebuilt fan
> is still working great BTW).
>
> Thanks for any thoughts.


IIRC F$GETSYI("TEMPERATURE_VECTOR") is not documented. Perhaps this is
because it is not 100% reliable.