<?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: How can I learn patch details in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628265#M7856</link>
    <description>The problem descriptions and problem analysys sections in the patch documents take the contents of the case reports (PTR, CFS, etc) and syntehsize them down to what the customers need to know about the problems fixed.  Because these case reports are  customer specific, there is often a good deal of proprietary or customer specific information that we need to remove.&lt;BR /&gt;     If you need more information you can try asking your field representative if there is more information available.  They have access to the case reports.&lt;BR /&gt;&lt;BR /&gt;George Pagliarulo&lt;BR /&gt;OpenVMS ECO Release Process</description>
    <pubDate>Mon, 19 Sep 2005 06:07:22 GMT</pubDate>
    <dc:creator>George_145</dc:creator>
    <dc:date>2005-09-19T06:07:22Z</dc:date>
    <item>
      <title>How can I learn patch details</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628262#M7853</link>
      <description>When examining the individual patch enhancments, some have a ptr, cfs, req id or bug node id as you can see below link. Is it possible to find the related complete problem for which the patch is required by using these information. What are ptr, cfs, req id, bud no?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www4.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main" target="_blank"&gt;http://www4.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main&lt;/A&gt;|patch.breadcrumb.search|&amp;amp;patchid=DEC-AXPVMS-TCPIP_ECO-V0504-155-4&amp;amp;context=openvms:alpha:7.3-2&lt;BR /&gt;&lt;BR /&gt;....&lt;BR /&gt;....&lt;BR /&gt;ECO A   Alpha and VAX&lt;BR /&gt;&lt;BR /&gt; Problem:&lt;BR /&gt;&lt;BR /&gt; TCPIP$INTERNET_SERVICES INVEXCEPTN crash during shutdown caused&lt;BR /&gt; by $ TCPIP DISCONNECT DEVICE command.&lt;BR /&gt;&lt;BR /&gt; Deliverables:&lt;BR /&gt;&lt;BR /&gt; TCPIP$INTERNET_SERVICES.EXE   V5.4-15A&lt;BR /&gt;&lt;BR /&gt; Reference:&lt;BR /&gt;&lt;BR /&gt; PTR 70-5-2380 / CFS.102586 / Req Id: GB_G08063&lt;BR /&gt; TCPIP_BUGS Note 2986&lt;BR /&gt;....&lt;BR /&gt;....</description>
      <pubDate>Sat, 17 Sep 2005 02:36:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628262#M7853</guid>
      <dc:creator>mustafa_12</dc:creator>
      <dc:date>2005-09-17T02:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: How can I learn patch details</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628263#M7854</link>
      <description>Mustafa,&lt;BR /&gt;&lt;BR /&gt;the additional reference information numbers in patch descriptions are pointers to HP (previously Digital) internal problem escalation and management tools. TCPIP_BUGS is a notes conference internal to TCPIP engineering.&lt;BR /&gt;&lt;BR /&gt;This additional information from those systems is only available inside HP.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Sat, 17 Sep 2005 07:09:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628263#M7854</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-09-17T07:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: How can I learn patch details</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628264#M7855</link>
      <description>In the patch tree, read the .txt file.&lt;BR /&gt;&lt;BR /&gt;For example.&lt;BR /&gt;&lt;BR /&gt;At &lt;BR /&gt;&lt;A href="ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/" target="_blank"&gt;ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You'll see a both the patch and a txt file.&lt;BR /&gt;The .txt file has the description of the ECO&lt;BR /&gt;&lt;BR /&gt;VMS732_FIBRE_SCSI-V0700.PCSI-DCX_AXPEXE&lt;BR /&gt;is the patch, while&lt;BR /&gt;VMS732_FIBRE_SCSI-V0700.txt&lt;BR /&gt;&lt;BR /&gt;is a description of the ECO.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;</description>
      <pubDate>Sun, 18 Sep 2005 12:54:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628264#M7855</guid>
      <dc:creator>comarow</dc:creator>
      <dc:date>2005-09-18T12:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: How can I learn patch details</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628265#M7856</link>
      <description>The problem descriptions and problem analysys sections in the patch documents take the contents of the case reports (PTR, CFS, etc) and syntehsize them down to what the customers need to know about the problems fixed.  Because these case reports are  customer specific, there is often a good deal of proprietary or customer specific information that we need to remove.&lt;BR /&gt;     If you need more information you can try asking your field representative if there is more information available.  They have access to the case reports.&lt;BR /&gt;&lt;BR /&gt;George Pagliarulo&lt;BR /&gt;OpenVMS ECO Release Process</description>
      <pubDate>Mon, 19 Sep 2005 06:07:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-can-i-learn-patch-details/m-p/3628265#M7856</guid>
      <dc:creator>George_145</dc:creator>
      <dc:date>2005-09-19T06:07:22Z</dc:date>
    </item>
  </channel>
</rss>

