<?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: VAX7000-710 and 2GB Memory in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027391#M24057</link>
    <description>The following is from the OpenVMS FAQ ( master site &lt;A href="http://www.hoffmanlabs.com/vmsfaq" target="_blank"&gt;www.hoffmanlabs.com/vmsfaq&lt;/A&gt;        ) and I'm guessing this case is probably what you have encountered here:&lt;BR /&gt;__________________________________________________________&lt;BR /&gt;          5.8  Why doesn't OpenVMS see the new memory I just added?&lt;BR /&gt;&lt;BR /&gt;                   When adding memory to an OpenVMS system, you should&lt;BR /&gt;                   check for an existing definition of the PHYSICALPAGES&lt;BR /&gt;                   (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMS Alpha)&lt;BR /&gt;                   parameter in the SYS$SYSTEM:MODPARAMS.DAT parameter&lt;BR /&gt;                   database, use a text editor to reset the value in the&lt;BR /&gt;                   file to the new correct value as required, and then&lt;BR /&gt;                   perform the following command:&lt;BR /&gt;&lt;BR /&gt;                   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK&lt;BR /&gt;&lt;BR /&gt;                   This AUTOGEN command will reset various system&lt;BR /&gt;                   parameters based on recent system usage (FEEDBACK),&lt;BR /&gt;                   and it will reset the value for the PHYSICALPAGES&lt;BR /&gt;                   parameter to the new value. It will also reboot the&lt;BR /&gt;                   OpenVMS system.&lt;BR /&gt;&lt;BR /&gt;                   PHYSICALPAGES and PHYSICAL_MEMORY can also be used to&lt;BR /&gt;                   deliberately lower the amount of memory available for&lt;BR /&gt;                   use by OpenVMS. This ability can be useful in a few&lt;BR /&gt;                   specific circumstances, such as testing the behaviour&lt;BR /&gt;                   of an application in a system environment with a&lt;BR /&gt;                   particular (lower) amount of system memory available.&lt;BR /&gt;&lt;BR /&gt;                   PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on&lt;BR /&gt;                   OpenVMS Alpha) or (better and simpler) the entry can be&lt;BR /&gt;                   removed from the MODPARAMS.DAT file, to indicate that&lt;BR /&gt;                   all available memory should be used.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;---&lt;BR /&gt;&lt;BR /&gt;You're also up into the Extended Physical Addressing (XPA) range with this system, and there is some related information here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/DOC/731FINAL/5841/5841pro_041.html" target="_blank"&gt;http://h71000.www7.hp.com/DOC/731FINAL/5841/5841pro_041.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_VAX_SUP_GD.pdf" target="_blank"&gt;http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_VAX_SUP_GD.pdf&lt;/A&gt; -&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs&lt;BR /&gt;</description>
    <pubDate>Thu, 08 Feb 2007 12:17:46 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-02-08T12:17:46Z</dc:date>
    <item>
      <title>VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027388#M24054</link>
      <description>Customer just replaced a 512mb memory board in a VAX7000-710 running OpenVMS VAX 6.2.  At the boot prompt the system sees the 2GB board.  After booting a "show memory" command shows main memory (512.0Mb).  With the 512mb board the same command showed 511.5Mb.&lt;BR /&gt;&lt;BR /&gt;Is the system using 2GB?  If not, what has to be done for the system to utilize 2GB?</description>
      <pubDate>Thu, 08 Feb 2007 12:06:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027388#M24054</guid>
      <dc:creator>Russ Carraro</dc:creator>
      <dc:date>2007-02-08T12:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027389#M24055</link>
      <description>Russ,&lt;BR /&gt;&lt;BR /&gt;did you run @AUTOGEN after adding the memory ? What is the PHYSCIALPAGES system parameter set to ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 08 Feb 2007 12:11:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027389#M24055</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2007-02-08T12:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027390#M24056</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;Autogen has not been run. SYSGEN parameter PHYSICALPAGES is 1048576.  No PYHSICALPAGES in MODPARAMS.DAT.&lt;BR /&gt;&lt;BR /&gt;Russ</description>
      <pubDate>Thu, 08 Feb 2007 12:16:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027390#M24056</guid>
      <dc:creator>Russ Carraro</dc:creator>
      <dc:date>2007-02-08T12:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027391#M24057</link>
      <description>The following is from the OpenVMS FAQ ( master site &lt;A href="http://www.hoffmanlabs.com/vmsfaq" target="_blank"&gt;www.hoffmanlabs.com/vmsfaq&lt;/A&gt;        ) and I'm guessing this case is probably what you have encountered here:&lt;BR /&gt;__________________________________________________________&lt;BR /&gt;          5.8  Why doesn't OpenVMS see the new memory I just added?&lt;BR /&gt;&lt;BR /&gt;                   When adding memory to an OpenVMS system, you should&lt;BR /&gt;                   check for an existing definition of the PHYSICALPAGES&lt;BR /&gt;                   (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMS Alpha)&lt;BR /&gt;                   parameter in the SYS$SYSTEM:MODPARAMS.DAT parameter&lt;BR /&gt;                   database, use a text editor to reset the value in the&lt;BR /&gt;                   file to the new correct value as required, and then&lt;BR /&gt;                   perform the following command:&lt;BR /&gt;&lt;BR /&gt;                   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK&lt;BR /&gt;&lt;BR /&gt;                   This AUTOGEN command will reset various system&lt;BR /&gt;                   parameters based on recent system usage (FEEDBACK),&lt;BR /&gt;                   and it will reset the value for the PHYSICALPAGES&lt;BR /&gt;                   parameter to the new value. It will also reboot the&lt;BR /&gt;                   OpenVMS system.&lt;BR /&gt;&lt;BR /&gt;                   PHYSICALPAGES and PHYSICAL_MEMORY can also be used to&lt;BR /&gt;                   deliberately lower the amount of memory available for&lt;BR /&gt;                   use by OpenVMS. This ability can be useful in a few&lt;BR /&gt;                   specific circumstances, such as testing the behaviour&lt;BR /&gt;                   of an application in a system environment with a&lt;BR /&gt;                   particular (lower) amount of system memory available.&lt;BR /&gt;&lt;BR /&gt;                   PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on&lt;BR /&gt;                   OpenVMS Alpha) or (better and simpler) the entry can be&lt;BR /&gt;                   removed from the MODPARAMS.DAT file, to indicate that&lt;BR /&gt;                   all available memory should be used.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;---&lt;BR /&gt;&lt;BR /&gt;You're also up into the Extended Physical Addressing (XPA) range with this system, and there is some related information here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/DOC/731FINAL/5841/5841pro_041.html" target="_blank"&gt;http://h71000.www7.hp.com/DOC/731FINAL/5841/5841pro_041.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_VAX_SUP_GD.pdf" target="_blank"&gt;http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_VAX_SUP_GD.pdf&lt;/A&gt; -&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Feb 2007 12:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027391#M24057</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-02-08T12:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027392#M24058</link>
      <description>Do &lt;BR /&gt;$ mc sysgen sh physicalpages&lt;BR /&gt;Does it show the value for 512M or 2G ?&lt;BR /&gt;&lt;BR /&gt;Eventually put the right value for 2G and reboot.&lt;BR /&gt;&lt;BR /&gt;the wild:&lt;BR /&gt;$ mc sysgen&lt;BR /&gt;sh physicalpages&lt;BR /&gt;set . correct_value&lt;BR /&gt;w c&lt;BR /&gt;CTRL Z&lt;BR /&gt;and reboot&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Feb 2007 12:19:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027392#M24058</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2007-02-08T12:19:39Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027393#M24059</link>
      <description>Russ,&lt;BR /&gt;&lt;BR /&gt;Hoff has already delivered the 'full answer' ;-)&lt;BR /&gt;&lt;BR /&gt;On VAX, you need to run @AUTOGEN so that it can update the PHYSICALPAGES system parameter based on the current memory size.&lt;BR /&gt;&lt;BR /&gt;1048576 pages is about 512 MB.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 08 Feb 2007 12:24:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027393#M24059</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2007-02-08T12:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027394#M24060</link>
      <description>Russ,&lt;BR /&gt;&lt;BR /&gt;from your Forum Profile:&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;I have assigned points to 23 of 40 responses to my questions.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;7 of those are prior issues, some dating more than a year back.&lt;BR /&gt;&lt;BR /&gt;Maybe you can find some time to do some assigning?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.&lt;BR /&gt;Consider, that every poster took at least the trouble of posting for you!&lt;BR /&gt;&lt;BR /&gt;To easily find your streams with unassigned points, click your own name somewhere.&lt;BR /&gt;This will bring up your profile.&lt;BR /&gt;Near the bottom of that page, under the caption "My Question(s)" you will find "questions or topics with unassigned points " Clicking that will give all, and only, your questions that still have unassigned postings.&lt;BR /&gt;&lt;BR /&gt;Thanks on behalf of your Forum colleagues.&lt;BR /&gt;&lt;BR /&gt;PS. - nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before - please do not take offence - none is intended!&lt;BR /&gt;&lt;BR /&gt;PPS. - Zero points for this.&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>Thu, 08 Feb 2007 12:44:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027394#M24060</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2007-02-08T12:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027395#M24061</link>
      <description>Russ,&lt;BR /&gt;&lt;BR /&gt;Tnx!&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>Thu, 08 Feb 2007 16:05:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027395#M24061</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2007-02-08T16:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027396#M24062</link>
      <description>While too late now to adjust the number of points awarded, surely the answer given by Hoff was one of those 'magic solutions', and as such should be worth more than a measly six points :-) &lt;BR /&gt;JT:</description>
      <pubDate>Fri, 09 Feb 2007 11:34:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027396#M24062</guid>
      <dc:creator>John Travell</dc:creator>
      <dc:date>2007-02-09T11:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027397#M24063</link>
      <description>Adjusted parameters and ran autogen.</description>
      <pubDate>Fri, 09 Feb 2007 12:24:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027397#M24063</guid>
      <dc:creator>Russ Carraro</dc:creator>
      <dc:date>2007-02-09T12:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027398#M24064</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;You're right, I mistyped and closed the thread without realizing it.  I meant for it to be a 9.  I apologize.&lt;BR /&gt;&lt;BR /&gt;Russ</description>
      <pubDate>Fri, 09 Feb 2007 12:30:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027398#M24064</guid>
      <dc:creator>Russ Carraro</dc:creator>
      <dc:date>2007-02-09T12:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: VAX7000-710 and 2GB Memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027399#M24065</link>
      <description>Adjusted parameters and ran autogen.</description>
      <pubDate>Fri, 09 Feb 2007 12:31:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax7000-710-and-2gb-memory/m-p/5027399#M24065</guid>
      <dc:creator>Russ Carraro</dc:creator>
      <dc:date>2007-02-09T12:31:18Z</dc:date>
    </item>
  </channel>
</rss>

