<?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: v7.3-2 Upgrade Problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912986#M69524</link>
    <description>p.s. Veli, Where did you find that?  Being able to find those kind of things would be great, if I could!&lt;BR /&gt;&lt;BR /&gt;This kind of stuff used to be in the DSN system, but that has gone away.  I tried searching all of ITRC, but could never find a match to anything I tried.&lt;BR /&gt;&lt;BR /&gt;rick</description>
    <pubDate>Sun, 17 Jul 2005 15:47:58 GMT</pubDate>
    <dc:creator>Rick Dyson</dc:creator>
    <dc:date>2005-07-17T15:47:58Z</dc:date>
    <item>
      <title>v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912982#M69520</link>
      <description>I tried to upgrade a stand-alone box from v7.3-1 to v7.3-2.  It currently has some problem with the DECWindows that HP has no idea how to fix except to upgrade and see if that fixes it.&lt;BR /&gt;&lt;BR /&gt;The upgrade started and stopped at:&lt;BR /&gt;&lt;BR /&gt;[SYSLIB]sys$starlet_c.tlb not installed or is present but out of scope: module update skipped.&lt;BR /&gt;&lt;BR /&gt;It then recommened terminating, which I did.  It had already removed all the Product recovery patches.&lt;BR /&gt;&lt;BR /&gt;I am still able to boot the old system disk and I have access to the Sys$Library:Sys$Starlet_C.tlb file.&lt;BR /&gt;&lt;BR /&gt;I can't find any reference to this kind of error on this ITRC (DSN is dead now, right?)&lt;BR /&gt;&lt;BR /&gt;On a previous upgrade from 7.2 -&amp;gt; v7.3-1 a couple years back, I had a similar sounding problem that required HP to analyze my TLB and give me a list of modules to delete from the library BEFORE upgrading.  I believe they blamed it on bugs in PCSI...&lt;BR /&gt;&lt;BR /&gt;Has anyone else seen this problem or something like it?&lt;BR /&gt;&lt;BR /&gt;I have attached a full directory listing of the TLB file and a library listing of my Starlet_C text library for reference.&lt;BR /&gt;&lt;BR /&gt;rick&lt;BR /&gt;</description>
      <pubDate>Sun, 17 Jul 2005 09:00:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912982#M69520</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2005-07-17T09:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912983#M69521</link>
      <description>I know there is an issue with this upgrade, but that had to do with another patch, yhis has been coverd in this forum. I guess you  should at leat install ALL the PCSI patches. It might be you'll need to do all DECWindows patches as well (and probably some more, the C compiler might be another one)&lt;BR /&gt;&lt;BR /&gt;If you have a spare disk you can use to create a backup system disk on (before upgrading) you could try the continue. If the system is not used for developing programs (in C or C++) this libary is likely to be non-critical and could be missed - unless some product would require it duirng install (it would require a C/C++ compiler as well, plus it;s PAK)&lt;BR /&gt;</description>
      <pubDate>Sun, 17 Jul 2005 10:39:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912983#M69521</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2005-07-17T10:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912984#M69522</link>
      <description>I found the following:&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;The problem (for both upgrade paths) is triggered by the installation of the&lt;BR /&gt;VMS731_PTHREAD V4.0 remedial kit.  It is possible that a version of the&lt;BR /&gt;VMS731_UPGRADE kit (that includes this PTHREAD kit) could trigger the problem.&lt;BR /&gt;&lt;BR /&gt;The good news is that [SYSLIB]SYS$STARLET_C.TLB is upgraded correctly when&lt;BR /&gt;upgrading to V7.3-2 if the user answers NO to the "Do you want to terminate?&lt;BR /&gt;[YES]" question.  The step being "skipped" is not necessary to perform since&lt;BR /&gt;the whole library file will be replaced anyway.  The error message, in this&lt;BR /&gt;case, simply should not have been displayed.&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;For customers who upgrade from V7.3-1 to V7.3-2 and have VMS731_PTHREAD V4.0&lt;BR /&gt;installed, the workaround is to answer NO to the terminate question.  Anyone&lt;BR /&gt;who really wants to verify that [SYSLIB]SYS$STARLET_C.TLB is ok can compare&lt;BR /&gt;the file from the bootable CD with the one on the target (upgraded) system&lt;BR /&gt;disk.&lt;BR /&gt;&lt;BR /&gt;----&lt;BR /&gt;&lt;BR /&gt;That being it apparently, you could check &lt;BR /&gt;&lt;BR /&gt;$ product show history vms731*&lt;BR /&gt;&lt;BR /&gt;whether VMS731_PTHREAD or VMS731_UPDATE has been been applied to system. And anyway, just continue the upgrade.&lt;BR /&gt;&lt;BR /&gt;_veli</description>
      <pubDate>Sun, 17 Jul 2005 12:56:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912984#M69522</guid>
      <dc:creator>Veli Körkkö</dc:creator>
      <dc:date>2005-07-17T12:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912985#M69523</link>
      <description>EXCELLENT!  Both of you!&lt;BR /&gt;&lt;BR /&gt;I always keep things patched. :)  So I guess I brought this on myself!&lt;BR /&gt;&lt;BR /&gt;PRODUCT                             KIT TYPE    OPERATION   DATE AND TIME&lt;BR /&gt;----------------------------------- ----------- ----------- --------------------&lt;BR /&gt;DEC AXPVMS VMS731_PTHREAD V4.0      Patch       Install     26-JUL-2004 22:18:39&lt;BR /&gt;DEC AXPVMS VMS731_PTHREAD V3.0      Patch       Install     05-JUN-2004 15:18:10&lt;BR /&gt;DEC AXPVMS VMS731_PTHREAD V2.0      Patch       Install     10-SEP-2003 09:54:46&lt;BR /&gt;&lt;BR /&gt;I will try again (I don't have a spare disk on this box big enough to make an image copy of the system disk (I tried!) but I did make a backup tape first. :)&lt;BR /&gt;&lt;BR /&gt;I will try again and Just Say NO. &lt;BR /&gt;&lt;BR /&gt;rick</description>
      <pubDate>Sun, 17 Jul 2005 15:45:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912985#M69523</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2005-07-17T15:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912986#M69524</link>
      <description>p.s. Veli, Where did you find that?  Being able to find those kind of things would be great, if I could!&lt;BR /&gt;&lt;BR /&gt;This kind of stuff used to be in the DSN system, but that has gone away.  I tried searching all of ITRC, but could never find a match to anything I tried.&lt;BR /&gt;&lt;BR /&gt;rick</description>
      <pubDate>Sun, 17 Jul 2005 15:47:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912986#M69524</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2005-07-17T15:47:58Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912987#M69525</link>
      <description>Rick,&lt;BR /&gt;&lt;BR /&gt;the same thing happened to me during installation of the E8.2 fieldtest upgrade (from a V7.3-1 system with VMS731_PTRHEAD-V0400 installed). Raised as PTR 75-107-39 and included in the V8.2 Release Notes chapter 1.9.3 Error on Upgrade from Version V7.3-1&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Sun, 17 Jul 2005 23:19:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912987#M69525</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-07-17T23:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: v7.3-2 Upgrade Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912988#M69526</link>
      <description>I have found that indeed, the suggestion to carry on through the warning worked just fine.  I have finished and gotten the intial reboots finished.&lt;BR /&gt;&lt;BR /&gt;Of course, the driving force was to fix a DECWindows problem and I am still stuck at an all white screen with a "X11" mouse and nothing else.  :(  I will have to run through all the patches now and see if one of them fixes it.&lt;BR /&gt;&lt;BR /&gt;Thanks to all of you who helped!&lt;BR /&gt;&lt;BR /&gt;rick</description>
      <pubDate>Mon, 18 Jul 2005 13:26:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/v7-3-2-upgrade-problem/m-p/4912988#M69526</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2005-07-18T13:26:41Z</dc:date>
    </item>
  </channel>
</rss>

