<?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: Reboot Using Changes From MODPARAMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238905#M90554</link>
    <description>If you don't want to save the system feedback data during shutdown then, well, don't save feedback during shutdown.  It's an option during shutdown. &lt;BR /&gt;</description>
    <pubDate>Wed, 23 Jul 2008 12:40:46 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2008-07-23T12:40:46Z</dc:date>
    <item>
      <title>Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238897#M90546</link>
      <description>I guess this is really a question I should know the answer to, but can anyone tell me the sequence of steps used to reboot a system using the current AutoGen settings, but also read the settings in MODPARAMS.DAT.&lt;BR /&gt;&lt;BR /&gt;I.E. I've changed MIN_GBLSECTIONS in MODPARAMS, and need to reboot, but don't want to use SAVE_FEEDBACK as the system has only been up a few hours.&lt;BR /&gt;&lt;BR /&gt;Thanks, Rob.&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jul 2008 08:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238897#M90546</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2008-07-23T08:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238898#M90547</link>
      <description>autogen help&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 23 Jul 2008 08:50:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238898#M90547</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-23T08:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238899#M90548</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;I agree with Wim. While it is obviously possible to reproduce it here, the best answer (by definition) is to use the HELP within AUTOGEN.&lt;BR /&gt;&lt;BR /&gt;AUTOGEN allows the beginning and ending phase to be specified.&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>Wed, 23 Jul 2008 09:11:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238899#M90548</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2008-07-23T09:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238900#M90549</link>
      <description>Read it top to bottom about a hundred times over the last 20 years, but it's still not obvious exactly what parameters would give me what I need, and I simply don't have the time to sit and test.&lt;BR /&gt;&lt;BR /&gt;Guess this ones beaten you guys then?&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Wed, 23 Jul 2008 09:29:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238900#M90549</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2008-07-23T09:29:29Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238901#M90550</link>
      <description>If you use GENPARAMS you can generate the last generated settings again (in case of lost settings).&lt;BR /&gt;&lt;BR /&gt;If you use GETDATA GENPARAMS it will re-use the last feedback and mix it with the new MODPARAMS settings. This is what you need I think. If the last feedback was valid.&lt;BR /&gt;&lt;BR /&gt;AUTOGEN can IMO not be used to apply only the modparams settings.&lt;BR /&gt;&lt;BR /&gt;I normally apply them by hand if I don't want a feedback.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 23 Jul 2008 11:11:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238901#M90550</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-23T11:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238902#M90551</link>
      <description>You can also specify NOFEEDBACK which I do all the time.&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jul 2008 11:16:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238902#M90551</guid>
      <dc:creator>EdgarZamora_1</dc:creator>
      <dc:date>2008-07-23T11:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238903#M90552</link>
      <description>I'm not sure if NOFEEDBACK is always safe. It will recalculate parameters without feedback. Could that reverse a previous autogen done with feedback ?&lt;BR /&gt;&lt;BR /&gt;I tested it and found ACP_DIRCACHE decreased from 352 to 196. Nothing about it in the modparams file.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 23 Jul 2008 11:33:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238903#M90552</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-23T11:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238904#M90553</link>
      <description>@SYS$UPDATE:AUTOGEN GETDATA SETPARAMS CHECK_FEEDBACK&lt;BR /&gt;&lt;BR /&gt;should do the right thing as it it will use the current feedback file if it is valid and not make a new one.&lt;BR /&gt;&lt;BR /&gt;Do check the report file and then reboot.</description>
      <pubDate>Wed, 23 Jul 2008 12:24:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238904#M90553</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2008-07-23T12:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238905#M90554</link>
      <description>If you don't want to save the system feedback data during shutdown then, well, don't save feedback during shutdown.  It's an option during shutdown. &lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jul 2008 12:40:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238905#M90554</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-07-23T12:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238906#M90555</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;I agree with Wim, at least if my understanding of what you are asking is correct, GETDATA would seem to be the place to start.&lt;BR /&gt;&lt;BR /&gt;If you want to be cautious, you may want to stop short of the actual REBOOT and check the new parameters against the prior ones to guard against surprises.&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>Wed, 23 Jul 2008 12:54:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238906#M90555</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2008-07-23T12:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238907#M90556</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;"if feedback is suspect, autogen does not use feedack" (help).&lt;BR /&gt;&lt;BR /&gt;How does autogen detect a suspect feedback ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 23 Jul 2008 13:08:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238907#M90556</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-23T13:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238908#M90557</link>
      <description>I checked autogen.com.&lt;BR /&gt;&lt;BR /&gt;CHECK_FEEDBACK checks :&lt;BR /&gt;uptime must be &amp;gt; 24h&lt;BR /&gt;must have been taken &amp;lt; 30 days ago&lt;BR /&gt;&lt;BR /&gt;That's all.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 23 Jul 2008 13:45:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238908#M90557</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-23T13:45:11Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238909#M90558</link>
      <description>Hoff, not saving FEEDBACK during shutdown (assuming SYS$SYSTEM:SHUTDOWN here) is fine, except that it won't bring in changes to MODPARAMS.&lt;BR /&gt;&lt;BR /&gt;That's what I need AUTOGEN for.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Wed, 23 Jul 2008 14:03:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238909#M90558</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2008-07-23T14:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238910#M90559</link>
      <description>@SYS$UPDATE:AUTOGEN GETDATA SETPARAMS CHECK_FEEDBACK&lt;BR /&gt;&lt;BR /&gt;check the report file here and then&lt;BR /&gt;&lt;BR /&gt;@SYS$SYSTEM:SHUTDOWN 0 SHUTDOWN NO YES LATER YES NONE&lt;BR /&gt;&lt;BR /&gt;If you want to skip the check of report file (not recommended)&lt;BR /&gt;@SYS$UPDATE:AUTOGEN GETDATA REBOOT CHECK_FEEDBACK</description>
      <pubDate>Wed, 23 Jul 2008 15:00:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238910#M90559</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2008-07-23T15:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Using Changes From MODPARAMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238911#M90560</link>
      <description>A slight difference from Ian's method.&lt;BR /&gt;&lt;BR /&gt;@SYS$UPDATE:AUTOGEN GETDATA TESTFILES CHECK_FEEDBACK&lt;BR /&gt;&lt;BR /&gt;Review AGEN$PARAMS.REPORT for warnings and changes.&lt;BR /&gt;&lt;BR /&gt;@SYS$UPDATE:AUTOGEN SETPARAMS&lt;BR /&gt;&lt;BR /&gt;Reboot when convenient.&lt;BR /&gt;&lt;BR /&gt;I prefer not to run the SETPARAMS phase until I've seen the report file since I've been known to make typos once in a while.&lt;BR /&gt;&lt;BR /&gt;Andy Bustamante&lt;BR /&gt;&lt;BR /&gt;"There are nine and sixty ways . . . "&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jul 2008 16:39:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reboot-using-changes-from-modparams/m-p/4238911#M90560</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2008-07-23T16:39:53Z</dc:date>
    </item>
  </channel>
</rss>

