<?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: delay startup in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088960#M90809</link>
    <description>I've never had a PWS600; does it do a full memory test on power up?  If so you could buy more memory :-)</description>
    <pubDate>Tue, 22 Jan 2008 09:30:21 GMT</pubDate>
    <dc:creator>Jon Pinkley</dc:creator>
    <dc:date>2008-01-22T09:30:21Z</dc:date>
    <item>
      <title>delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088958#M90807</link>
      <description>Environment: Alpha PWS600, system disk via HSZ50 in BA356 shelf, but it might apply to other environmenst as well. &lt;BR /&gt;The Alpha system is set up to boot on power-on (AUTOSTART=BOOT).&lt;BR /&gt;&lt;BR /&gt;After power loss on both Alpha and storage fails the Alpha does not boot, but when storage is kept on power, it will. My impression is that initialization of the Alpha is simply too fast - it will try to access the HSZ50 before that finishes it's initialization sequence (including spinning up the disks).&lt;BR /&gt;&lt;BR /&gt;I have no output or logging - this usually happens when I'm not around :(&lt;BR /&gt;&lt;BR /&gt;My idea is to have the Alpha wait a while (say: 1 minute) to allow the HSZ50 to do it'sjob and get up, before the Alpha starts to start the boot sequence.  Is this possible, and if so, how?&lt;BR /&gt;&lt;BR /&gt;SRM is up-to-date (latest release)</description>
      <pubDate>Tue, 22 Jan 2008 08:21:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088958#M90807</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-01-22T08:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088959#M90808</link>
      <description>Perhaps you can use the 'nvram' startup script feature to setup a delay, there is the sleep function available.&lt;BR /&gt;You edit the script with 'edit nvram', but be careful.&lt;BR /&gt;Note: I have not used this feature by myself and I don't know, if the PWS600 firmare supports this.)&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Tue, 22 Jan 2008 08:52:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088959#M90808</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2008-01-22T08:52:44Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088960#M90809</link>
      <description>I've never had a PWS600; does it do a full memory test on power up?  If so you could buy more memory :-)</description>
      <pubDate>Tue, 22 Jan 2008 09:30:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088960#M90809</guid>
      <dc:creator>Jon Pinkley</dc:creator>
      <dc:date>2008-01-22T09:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088961#M90810</link>
      <description>Kalle:&lt;BR /&gt;I don't know if it's possible but it's worth a try. I'll dig the docs on this&lt;BR /&gt;&lt;BR /&gt;Jon:&lt;BR /&gt;No full memory test, and if enabled, it would be slow enough. Though more memory is useful for other reasons.</description>
      <pubDate>Tue, 22 Jan 2008 09:58:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088961#M90810</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-01-22T09:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088962#M90811</link>
      <description>I booted my AS500 from cd and disk. It tried a few seconds (invain because no cd) with the cd before switching to the disk. May be try that to delay the boot. Or specify the same device multiple times (can't test it because it finds the disk directly in my case).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 22 Jan 2008 10:36:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088962#M90811</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-01-22T10:36:31Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088963#M90812</link>
      <description>It is my impression that you are running only into HSZ50 init, not actual disk delays.  Once the HSZ's are "awake" they will accept the I/O request but just stall you.  Maybe you need to look at SYSGEN parameters such as MVTIMEOUT.  If that is too low, you would "give up" too soon.&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Jan 2008 18:01:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088963#M90812</guid>
      <dc:creator>Richard W Hunt</dc:creator>
      <dc:date>2008-01-28T18:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: delay startup</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088964#M90813</link>
      <description>Thanks for the suggestions, I'll look into each of them and pick the one most useful.</description>
      <pubDate>Fri, 15 Aug 2008 08:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/delay-startup/m-p/5088964#M90813</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-08-15T08:11:07Z</dc:date>
    </item>
  </channel>
</rss>

