<?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: TIMEPROMPTWAIT in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968655#M82975</link>
    <description>TIMEPROMPTWAIT and SETTIME are the two system parameters.&lt;BR /&gt;&lt;BR /&gt;By "AXP500/400", did you intend "AlphaStation 500/400"?  (Some of these system model names are unfortunately really close; I've learned to be cautious about system marketing model identification.)&lt;BR /&gt;&lt;BR /&gt;Many of these boxes used a Dallas or similar chip, and the chip contains an internal lithium battery.  When these lithium cells fail (and that usually happens somewhere between five and usually closer to ten years), the box forgets what console to use and generally selects AlphaBIOS/ARC and not SRM, forgets the system time, and forgets the environment variable settings.&lt;BR /&gt;&lt;BR /&gt;Field identification for the Dallas chip:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.futurlec.com/Dallas/DS12887.shtml" target="_blank"&gt;http://www.futurlec.com/Dallas/DS12887.shtml&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Or dig up the service manual and go looking.&lt;BR /&gt;&lt;BR /&gt;If you find you have a Dalla chip in this box, it's socketed on every box I've encountered.&lt;BR /&gt;&lt;BR /&gt;Some of the oldest boxes used a NiCd battery pack or a lithium coin cell, and these too could drain.  Check the module(s) in the box, or find the service manual and have a look.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs</description>
    <pubDate>Mon, 26 Mar 2007 10:21:54 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-03-26T10:21:54Z</dc:date>
    <item>
      <title>TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968651#M82971</link>
      <description>I have very old AXP500/400.&lt;BR /&gt;When they boot after a weekend power off, they prompt for the date. Probably due to bad battery.&lt;BR /&gt;&lt;BR /&gt;If I set TIMEPROMPTWAIT to 0, will it continue without prompting ? Will it take the very-old date (17xx ?) as default ? Even when the battery is bad ?&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 26 Mar 2007 02:44:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968651#M82971</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-26T02:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968652#M82972</link>
      <description>I think it always waits if the battery is bad.</description>
      <pubDate>Mon, 26 Mar 2007 05:35:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968652#M82972</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2007-03-26T05:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968653#M82973</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;According to the help text for TIMEPROMPTWAIT in SYSGEN, the following is the behavior (the text is still the same in 8.2) [paraphrased for berevity]:&lt;BR /&gt;&lt;BR /&gt;== 0 - No prompt or wait occurs; use last book as system time&lt;BR /&gt;0 &amp;gt; TIMEPROMPTWAIT &amp;gt; 32768 - One prompt is issued; the system waits TIMEPROMPTWAIT seconds; then proceeds using the last boot time as the time&lt;BR /&gt;32768 &amp;lt;= TIMEPROMPTWAIT &amp;lt; 65535 - Time waits for 2 seconds; then doubles until 256 seconds; and then the sequence is repeated indefinitely&lt;BR /&gt;&lt;BR /&gt;WADU, I recommend checking the HELP text directly and not rely on my paraphrase.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 26 Mar 2007 05:39:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968653#M82973</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2007-03-26T05:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968654#M82974</link>
      <description>During lunch break, I shut 1 node that had the problem after putting TIMEP on 30. Then power off for 1 minute and reboot. No prompt at all. Tried it 2 times&lt;BR /&gt;&lt;BR /&gt;The strange thing is that none of the stations had it before and now 3 out 4 stations had it.&lt;BR /&gt;&lt;BR /&gt;Could it be related to the fact that the station was power off during the time change ? I use DTSS.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 26 Mar 2007 06:22:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968654#M82974</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-26T06:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968655#M82975</link>
      <description>TIMEPROMPTWAIT and SETTIME are the two system parameters.&lt;BR /&gt;&lt;BR /&gt;By "AXP500/400", did you intend "AlphaStation 500/400"?  (Some of these system model names are unfortunately really close; I've learned to be cautious about system marketing model identification.)&lt;BR /&gt;&lt;BR /&gt;Many of these boxes used a Dallas or similar chip, and the chip contains an internal lithium battery.  When these lithium cells fail (and that usually happens somewhere between five and usually closer to ten years), the box forgets what console to use and generally selects AlphaBIOS/ARC and not SRM, forgets the system time, and forgets the environment variable settings.&lt;BR /&gt;&lt;BR /&gt;Field identification for the Dallas chip:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.futurlec.com/Dallas/DS12887.shtml" target="_blank"&gt;http://www.futurlec.com/Dallas/DS12887.shtml&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Or dig up the service manual and go looking.&lt;BR /&gt;&lt;BR /&gt;If you find you have a Dalla chip in this box, it's socketed on every box I've encountered.&lt;BR /&gt;&lt;BR /&gt;Some of the oldest boxes used a NiCd battery pack or a lithium coin cell, and these too could drain.  Check the module(s) in the box, or find the service manual and have a look.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs</description>
      <pubDate>Mon, 26 Mar 2007 10:21:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968655#M82975</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-03-26T10:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968656#M82976</link>
      <description>DTSS doesn't get involved until rather further along in the boot process -- the saved time and such -- and there are some sanity checks -- involves the BB_WATCH chip and the saved system image time.  (And AFAIK, both DTSS and NTP distribute UTC.  Not local time.)&lt;BR /&gt;&lt;BR /&gt;I haven't looked at the delta for declaring the saved time value and the BB_WATCH value too "extreme" in some time, but it's conceivable that the year might have changed in the saved system image.  We're also in the window when the saved values get rewritten.  &lt;BR /&gt;&lt;BR /&gt;(VAX systems are notorious for various operational burbles within the first several months of the year, given the 497 day maximum resolution of the VAX TOY.  Alpha BB_WATCH handling is rather better than the VAX TOY handling, however.  The FAQ has details.)&lt;BR /&gt;&lt;BR /&gt;But if you can't duplicate it, it may well be a stale rechargeable battery that got recharged, or a weak battery that got warmed up.  Close it out as a PotM dependency (phase of the moon), err, as not being reproducible?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 26 Mar 2007 11:16:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968656#M82976</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-03-26T11:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968657#M82977</link>
      <description>Yes it's an AS500/400. I most of the time prefer AXP because Alpha means development in the bank.&lt;BR /&gt;&lt;BR /&gt;I'll be in holiday next week and power off my station to see how it reacts.&lt;BR /&gt;&lt;BR /&gt;Didn't know that the battery was recharable.&lt;BR /&gt;And yes, they are over 10 years old.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 27 Mar 2007 00:56:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968657#M82977</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-27T00:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968658#M82978</link>
      <description>I'm also aware that bad battery causes console variable loss. May be it's not the same battery because this was not the case. And the really bad battery problem occurs very rarely, so it seems almost impossible that it is the battery because 3 out 4 stations had the problem.&lt;BR /&gt;So, the BB_WATCH bad battery seems most reasonable to me. May be it is that bad that it has just power for a few hours. And when I redid the test it was charged enough for the test.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 27 Mar 2007 01:11:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968658#M82978</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-03-27T01:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: TIMEPROMPTWAIT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968659#M82979</link>
      <description>I left the station power off during my (sunny) skiing holiday (10 days).&lt;BR /&gt;It booted without date prompt. &lt;BR /&gt;&lt;BR /&gt;I will test it again during the next time change (28 oct). &lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 10 Apr 2007 04:29:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/timepromptwait/m-p/3968659#M82979</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-04-10T04:29:03Z</dc:date>
    </item>
  </channel>
</rss>

