<?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: CPU Migration in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cpu-migration/m-p/4467702#M95697</link>
    <description>What are your licensed units for each instance?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2.4 OpenVMS Galaxy License Enforcement&lt;BR /&gt;&lt;BR /&gt;In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs. &lt;BR /&gt;&lt;BR /&gt;If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY license units to support it, the CPU will remain in the instance's configured set but it will be stopped. You can subsequently load the appropriate license units and start the stopped CPU while the system is running. This is true of one or more CPUs. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steps are in here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf" target="_blank"&gt;http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 28 Jul 2009 15:36:44 GMT</pubDate>
    <dc:creator>cnb</dc:creator>
    <dc:date>2009-07-28T15:36:44Z</dc:date>
    <item>
      <title>CPU Migration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-migration/m-p/4467701#M95696</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a ES47 server with Openvms 7.3-2 it has 1 hard partion and 2 soft partitions. I tried to migrate a cpu from 1 partion to another partion using SET CPU/MIGRATE command and the cpu leaves from the soruce to destn but it goes to "Timeout" state in the dstn system hence its is not usable. Later when I power off both partions followed by a reboot it comes to RUN state in original partition without any issues. Is there any way to overcome this situvation or is there any way to migrate the CPU from 1 soft partion to another soft partion from MBM if yes please let me know the steps.</description>
      <pubDate>Tue, 28 Jul 2009 03:32:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-migration/m-p/4467701#M95696</guid>
      <dc:creator>Accullise</dc:creator>
      <dc:date>2009-07-28T03:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Migration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-migration/m-p/4467702#M95697</link>
      <description>What are your licensed units for each instance?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2.4 OpenVMS Galaxy License Enforcement&lt;BR /&gt;&lt;BR /&gt;In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs. &lt;BR /&gt;&lt;BR /&gt;If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY license units to support it, the CPU will remain in the instance's configured set but it will be stopped. You can subsequently load the appropriate license units and start the stopped CPU while the system is running. This is true of one or more CPUs. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steps are in here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf" target="_blank"&gt;http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Jul 2009 15:36:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-migration/m-p/4467702#M95697</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-07-28T15:36:44Z</dc:date>
    </item>
  </channel>
</rss>

