<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic getting the temperature of a DS10 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766110#M75462</link>
    <description>I use the procedure &lt;A href="http://dcl.openvms.org/stories.php?story=03/07/10/8132100" target="_blank"&gt;http://dcl.openvms.org/stories.php?story=03/07/10/8132100&lt;/A&gt; to get the temperature on a good number of DS10. They have all the same level of patches, with Vms 7.2-1 or Vms 7.3-2&lt;BR /&gt;&lt;BR /&gt;It works fine, except on 2, which first worked fine&lt;BR /&gt;&lt;BR /&gt;1) a Alphaserver DS10 466 Mhz with 7.2-1, which gave yesterday 39 Celsius, and then since this night, always gives&lt;BR /&gt;$ wr sys$output f$getsyi("temperature_vector")&lt;BR /&gt;FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE, so 254 Celsius&lt;BR /&gt;&lt;BR /&gt;2) a AlphaServer DS10 617 MHz with 7.3-2, which has given once only the same 254, and before and since gives the reasonable %X26, so 38 Celsius&lt;BR /&gt;&lt;BR /&gt;I wonder if I should check something after getting this value, but $status is the same on the 2 nodes&lt;BR /&gt;a=f$getsyi("temperature_vector")&lt;BR /&gt;$STATUS == "%X00030001"&lt;BR /&gt;&lt;BR /&gt;May be I should just discard the value FE, which means "unable to get the temerature" ?&lt;BR /&gt;&lt;BR /&gt;I have seen in comp.os.vms this test&lt;BR /&gt;If ((F$GETSYI("CRD_CONTROL") .AND. %X20) .NE. 0) Then   Write Sys&lt;BR /&gt;$Output "Good" &lt;BR /&gt;But the DS10 giving 254 says good too :-(&lt;BR /&gt;&lt;BR /&gt;May be this is patch related, but all the DS10 have the same level of patches, so there is something else.&lt;BR /&gt;&lt;BR /&gt;Thanks for any tip&lt;BR /&gt;&lt;BR /&gt;Gerard</description>
    <pubDate>Wed, 05 Apr 2006 04:33:13 GMT</pubDate>
    <dc:creator>labadie_1</dc:creator>
    <dc:date>2006-04-05T04:33:13Z</dc:date>
    <item>
      <title>getting the temperature of a DS10</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766110#M75462</link>
      <description>I use the procedure &lt;A href="http://dcl.openvms.org/stories.php?story=03/07/10/8132100" target="_blank"&gt;http://dcl.openvms.org/stories.php?story=03/07/10/8132100&lt;/A&gt; to get the temperature on a good number of DS10. They have all the same level of patches, with Vms 7.2-1 or Vms 7.3-2&lt;BR /&gt;&lt;BR /&gt;It works fine, except on 2, which first worked fine&lt;BR /&gt;&lt;BR /&gt;1) a Alphaserver DS10 466 Mhz with 7.2-1, which gave yesterday 39 Celsius, and then since this night, always gives&lt;BR /&gt;$ wr sys$output f$getsyi("temperature_vector")&lt;BR /&gt;FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE, so 254 Celsius&lt;BR /&gt;&lt;BR /&gt;2) a AlphaServer DS10 617 MHz with 7.3-2, which has given once only the same 254, and before and since gives the reasonable %X26, so 38 Celsius&lt;BR /&gt;&lt;BR /&gt;I wonder if I should check something after getting this value, but $status is the same on the 2 nodes&lt;BR /&gt;a=f$getsyi("temperature_vector")&lt;BR /&gt;$STATUS == "%X00030001"&lt;BR /&gt;&lt;BR /&gt;May be I should just discard the value FE, which means "unable to get the temerature" ?&lt;BR /&gt;&lt;BR /&gt;I have seen in comp.os.vms this test&lt;BR /&gt;If ((F$GETSYI("CRD_CONTROL") .AND. %X20) .NE. 0) Then   Write Sys&lt;BR /&gt;$Output "Good" &lt;BR /&gt;But the DS10 giving 254 says good too :-(&lt;BR /&gt;&lt;BR /&gt;May be this is patch related, but all the DS10 have the same level of patches, so there is something else.&lt;BR /&gt;&lt;BR /&gt;Thanks for any tip&lt;BR /&gt;&lt;BR /&gt;Gerard</description>
      <pubDate>Wed, 05 Apr 2006 04:33:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766110#M75462</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2006-04-05T04:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: getting the temperature of a DS10</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766111#M75463</link>
      <description>I have found&lt;BR /&gt;&lt;A href="http://www.mail-archive.com/vmsperl@perl.org/msg03180.html" target="_blank"&gt;http://www.mail-archive.com/vmsperl@perl.org/msg03180.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;which says, among other things, for a DS10&lt;BR /&gt;&lt;BR /&gt;$ temp_c = %X'F$Extract(30,2,temp_vec)'&lt;BR /&gt;$ If (temp_c .LE. 1) .OR. (temp_c .GE. %xFE)&lt;BR /&gt;$ Then&lt;BR /&gt;$  If temp_c .EQ. 0 Then $ say "Temperature status = failed"&lt;BR /&gt;$  If temp_c .EQ. 1 Then $ say -&lt;BR /&gt;                "Temperature stats = OK (the meaning of which is not clear) "&lt;BR /&gt;$  If temp_c .EQ. %xFE Then $ say "Temperature unknown"&lt;BR /&gt;$  If temp_c .EQ. %xFF Then $ say "Temperature data not present"&lt;BR /&gt;&lt;BR /&gt;But I still do not understand why a node no longer gives the temperature since yesterday.</description>
      <pubDate>Wed, 05 Apr 2006 06:02:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766111#M75463</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2006-04-05T06:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: getting the temperature of a DS10</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766112#M75464</link>
      <description>parhaps the temprature sensor is having a holiday? :-)&lt;BR /&gt;&lt;BR /&gt;Parhaps its broken. As this getting environmental information stuff is undocumented I wonder if it is not always reliable.</description>
      <pubDate>Wed, 05 Apr 2006 06:41:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766112#M75464</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-04-05T06:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: getting the temperature of a DS10</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766113#M75465</link>
      <description>Gerard,&lt;BR /&gt;&lt;BR /&gt;this is just software, isn't it ?&lt;BR /&gt;&lt;BR /&gt;The temperature vector is read with an IO$_ACPCONTROL QIOW from the IIA0: device in CPU specific code.&lt;BR /&gt;&lt;BR /&gt;If there is any error returned from this QIOW, the first element in the vector is set to SYI$K_ENV_STATUS_UNKNOWN (=254) and the rest is set to SYI$K_ENV_STATUS_NOT_PRESENT (=255)&lt;BR /&gt;&lt;BR /&gt;The status and IO status are kept on the local stack, so there is no way to find out lateron.&lt;BR /&gt;&lt;BR /&gt;On the V7.3-2 system, you could use the IO$SDA extension to trace buffered IOs and thus find the failing IO status code...&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 05 Apr 2006 06:42:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766113#M75465</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-04-05T06:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: getting the temperature of a DS10</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766114#M75466</link>
      <description>May be I should not expect much from something undocumented/unsupported :-)&lt;BR /&gt;&lt;BR /&gt;thanks for the answers</description>
      <pubDate>Wed, 05 Apr 2006 10:20:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/getting-the-temperature-of-a-ds10/m-p/3766114#M75466</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2006-04-05T10:20:24Z</dc:date>
    </item>
  </channel>
</rss>

