<?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: patch update in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868149#M79270</link>
    <description>&lt;BR /&gt;Dependencies can be confusing at first when HP state that one particular patch needs for example UPDATE V3 but the latest is Update V5. &lt;BR /&gt;&lt;BR /&gt;However always install the latest patch as UPDATE V5 will include V4 and V3 etc...&lt;BR /&gt;&lt;BR /&gt;The dependancies will then recognise that you&lt;BR /&gt;are on a higher patch and update ok.&lt;BR /&gt;&lt;BR /&gt;An example of this is SYSTEM V5 which states&lt;BR /&gt;that it needs UPDATE V3 first. This really&lt;BR /&gt;means UPDATE V3 or HIGHER.&lt;BR /&gt;&lt;BR /&gt;I hope this helps&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 04 Oct 2006 12:18:12 GMT</pubDate>
    <dc:creator>james_a_wells</dc:creator>
    <dc:date>2006-10-04T12:18:12Z</dc:date>
    <item>
      <title>patch update</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868147#M79268</link>
      <description>Please let me know if it is necessary for OPEN VMS V8.2A,in order to instal update patch v4.0,is is mandatory to instal patch 3.0.Current patch installed is update V2.0.</description>
      <pubDate>Fri, 22 Sep 2006 10:52:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868147#M79268</guid>
      <dc:creator>FOX MULDER_2</dc:creator>
      <dc:date>2006-09-22T10:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: patch update</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868148#M79269</link>
      <description>&lt;BR /&gt;OpenVMS patches are cumulative, UPDATE 4.00 includes UPDATE 3.0.  You can review the release notes for patches at &lt;A href="http://www2.itrc.hp.com/service/patch/search.do?BC=main" target="_blank"&gt;http://www2.itrc.hp.com/service/patch/search.do?BC=main&lt;/A&gt;|&amp;amp;pageOsid=openvms here on the ITRC site.  &lt;BR /&gt;&lt;BR /&gt;Some patches have dependencies on other patches, for example UPDATE 4.0 requires VMS82I_PCSI-V0100.  &lt;BR /&gt;&lt;BR /&gt;Andy&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2006 11:14:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868148#M79269</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2006-09-22T11:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: patch update</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868149#M79270</link>
      <description>&lt;BR /&gt;Dependencies can be confusing at first when HP state that one particular patch needs for example UPDATE V3 but the latest is Update V5. &lt;BR /&gt;&lt;BR /&gt;However always install the latest patch as UPDATE V5 will include V4 and V3 etc...&lt;BR /&gt;&lt;BR /&gt;The dependancies will then recognise that you&lt;BR /&gt;are on a higher patch and update ok.&lt;BR /&gt;&lt;BR /&gt;An example of this is SYSTEM V5 which states&lt;BR /&gt;that it needs UPDATE V3 first. This really&lt;BR /&gt;means UPDATE V3 or HIGHER.&lt;BR /&gt;&lt;BR /&gt;I hope this helps&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Oct 2006 12:18:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-update/m-p/3868149#M79270</guid>
      <dc:creator>james_a_wells</dc:creator>
      <dc:date>2006-10-04T12:18:12Z</dc:date>
    </item>
  </channel>
</rss>

