<?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 Re: 4105A/4106A battery life in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541144#M49187</link>
    <description>Thank you for the reply.&lt;BR /&gt;I am monitoring mutliple remote system and recently it is so happened that due to some problem VMS crashed and while rebooting it stoped at time/date prompt. this I could see after going to the site, which slightly far away and it caused down time for the server.&lt;BR /&gt;&lt;BR /&gt;These are prety old systems and I do not think that the battery been replaced for the last 6-7 years.&lt;BR /&gt;&lt;BR /&gt;thank you</description>
    <pubDate>Wed, 11 May 2005 04:22:20 GMT</pubDate>
    <dc:creator>Sunil_uk</dc:creator>
    <dc:date>2005-05-11T04:22:20Z</dc:date>
    <item>
      <title>4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541142#M49185</link>
      <description>Can any one give a clue on &lt;BR /&gt;&lt;BR /&gt;What is the recommendation for replacing the RTC battery on VAX4105A/4106A servers.&lt;BR /&gt;What is the life time of a battery on a 24/7/365 days online working setup.?&lt;BR /&gt;</description>
      <pubDate>Tue, 10 May 2005 05:12:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541142#M49185</guid>
      <dc:creator>Sunil_uk</dc:creator>
      <dc:date>2005-05-10T05:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541143#M49186</link>
      <description>Sunil,&lt;BR /&gt;&lt;BR /&gt;  Difficult to say. Some last a few years, some last for decades.&lt;BR /&gt;&lt;BR /&gt;  If the system really is 24x7x365 then you don't really need a battery, as it's job is to keep the clock accurate when power is removed.&lt;BR /&gt;&lt;BR /&gt;  Apart from physical removal and testing, the only way to check that your battery is good is to power down the system for an hour or so and see if it asks for the time when it reboots.&lt;BR /&gt;&lt;BR /&gt;  If you have a mission critical system, I'd recommend you find the price and availability of batteries, so you can make a sensible decision balancing the cost with the cost of having a system boot with a bad or inaccurate clock. You may decide to change the battery regardless of its state during periodic maintenance (say) every 2 years.&lt;BR /&gt;&lt;BR /&gt;  Just remember that shelf life is probably similar to in-service life, so you can't just "stock up" and keep the spares in a cupboard.&lt;BR /&gt;&lt;BR /&gt;  FWIW, I have several very old VAX systems (&amp;gt;12 years), some of which still have the original batteries, still working. Others have dead batteries, but I haven't bothered to change them because they're clustered and any clock errors will always be corrected soon after a reboot.</description>
      <pubDate>Wed, 11 May 2005 00:20:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541143#M49186</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-05-11T00:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541144#M49187</link>
      <description>Thank you for the reply.&lt;BR /&gt;I am monitoring mutliple remote system and recently it is so happened that due to some problem VMS crashed and while rebooting it stoped at time/date prompt. this I could see after going to the site, which slightly far away and it caused down time for the server.&lt;BR /&gt;&lt;BR /&gt;These are prety old systems and I do not think that the battery been replaced for the last 6-7 years.&lt;BR /&gt;&lt;BR /&gt;thank you</description>
      <pubDate>Wed, 11 May 2005 04:22:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541144#M49187</guid>
      <dc:creator>Sunil_uk</dc:creator>
      <dc:date>2005-05-11T04:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541145#M49188</link>
      <description>Sunil,&lt;BR /&gt;&lt;BR /&gt;please also take into acount, that you need to do a SET TIME = "''F$TIME()'" on each OpenVMS VAX system ONCE each year between 1-JAN and 11-APR (will be automatically done on a shutdown) to correctly set the TOY clock and the date in the base image.&lt;BR /&gt;&lt;BR /&gt;See section&lt;BR /&gt;&lt;BR /&gt;4.1.1.3 Why does VAX need a SET TIME at least once a year?&lt;BR /&gt;&lt;BR /&gt;in the OpenVMS FAQ:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/faq/vmsfaq_004.html#faq_time" target="_blank"&gt;http://h71000.www7.hp.com/faq/vmsfaq_004.html#faq_time&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Missing this could be another reason for a prompt to set the time after a crash.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 11 May 2005 04:47:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541145#M49188</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-11T04:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541146#M49189</link>
      <description>Sunil,&lt;BR /&gt;&lt;BR /&gt;and while further thinking about this:&lt;BR /&gt;&lt;BR /&gt;- if the TOY batterie is really dead, wouldn't the BOOT settings also have been lost (BOOT, BFLG, HALT ) ?&lt;BR /&gt;&lt;BR /&gt;- and you didn't loose power, only the system crashed - right ?!&lt;BR /&gt;&lt;BR /&gt;So maybe your batteries are just fine, although you never know, without powering down the system ;-(&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 11 May 2005 05:02:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541146#M49189</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-11T05:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541147#M49190</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;I am not so sure about that...&lt;BR /&gt;&lt;BR /&gt;As far as I know, those values are stored in EPROM, and remain intact for quite some time without power.&lt;BR /&gt;&lt;BR /&gt;But the clock has to be updated every clock-tick interval, and THAT needs power!!&lt;BR /&gt;&lt;BR /&gt;I do remember (way back) several occasions where a Vax or VaxStation DID boot according to settings, but DID ask for date-time input, which seems to support this. &lt;BR /&gt;&lt;BR /&gt;I _MAY_ be wrong here, but my gut feeling says...&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 11 May 2005 05:33:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541147#M49190</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-05-11T05:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541148#M49191</link>
      <description>HI,&lt;BR /&gt;&lt;BR /&gt;Is there any sysgen parameter which enables the system to ask date and time whenever it boots up&lt;BR /&gt;&lt;BR /&gt;sunil</description>
      <pubDate>Thu, 12 May 2005 03:48:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541148#M49191</guid>
      <dc:creator>Sunil_uk</dc:creator>
      <dc:date>2005-05-12T03:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541149#M49192</link>
      <description>if you set the SETTIME system parameter to 1&lt;BR /&gt;then VMS will ask for the datetime every time it boots.</description>
      <pubDate>Thu, 12 May 2005 04:01:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541149#M49192</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-05-12T04:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: 4105A/4106A battery life</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541150#M49193</link>
      <description>... and there is TIMEPROMPTWAIT, which controls the behaviour of the system during boot, if the TOY clock does NOT contain a valid time.&lt;BR /&gt;&lt;BR /&gt;Before jumping to conclusions about the TOY battery being dead, please check, whether the system may not have seen a SET TIME command since 1-JAN-2005. &lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 12 May 2005 04:47:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/4105a-4106a-battery-life/m-p/3541150#M49193</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-12T04:47:08Z</dc:date>
    </item>
  </channel>
</rss>

