<?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: Problem installing PathWorks on Alpha 8.3. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072926#M86699</link>
    <description>Hi Dean,&lt;BR /&gt;       Only a couple of comments.&lt;BR /&gt;&lt;BR /&gt;1.   I pulled the Advanced Server compressed PCSI file, and the associated manifest file (*.pcsi$compressed_esw), however when I ran "product install" I got some strange messages.  (basically saying that the install process couldn't validate the product because the name supplied was different from the name in the manifest file.)    I tried doing a "product list" and got the same result.    To try to move forward, I renamed the manifest file to *.temp, and reran the "product list".   This time it reported that "...there is supposed to be a manifest file, however I cant find it.   Do you want to continue...?"&lt;BR /&gt;I answered "Yes" to this and it went ahead and displayed the contents of the pcsi file.&lt;BR /&gt;&lt;BR /&gt;    This being the case, (and since I was working on a TEST system with a good backup), I went ahead and ran the "product install" command.   I got the "missing manifest file" message, but told it to continue.     It then went ahead and installed the product without any obvious issues.    &lt;BR /&gt;&lt;BR /&gt;2.    In the process of installing, it sets up the initial parameters.    The only one you might want to keep an eye on is the "Transports".   It defaults to IP, however the implication is that the IP option is for TCPWARE (this may not be true, however I didn't follow up).   I discovered the problem when I tried to start pathworks, I got a message saying that the PWIPDriver needed to be loaded.   Googling for the solution, I only found a reference to TCPWARE (which provides a com file to do this).     In my case, I just ran an "admin/config" command, and changed the transport to DECNet.&lt;BR /&gt;&lt;BR /&gt;Pathworks then started up OK.   &lt;BR /&gt;&lt;BR /&gt;I haven't got fully around to testing yet.&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
    <pubDate>Tue, 09 Oct 2007 06:07:39 GMT</pubDate>
    <dc:creator>The Brit</dc:creator>
    <dc:date>2007-10-09T06:07:39Z</dc:date>
    <item>
      <title>Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072921#M86694</link>
      <description>I have just upgraded one of my test machines to OpenVMS Alpha Version 8.3.    I now need to install and test PathWorks (my production systems use it).&lt;BR /&gt;    The installation (of PathWorks V6.1) appears to be successful, vis, from vmsinstal.history,&lt;BR /&gt;&lt;BR /&gt;------------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Product Information                                         | Installation Information                                  &lt;BR /&gt;------------------------------------------------------------|-----------------------------------------------------------&lt;BR /&gt;Name                           | Mnemonic         | Version | Date        | Status| IVP   | Node   | Installer          &lt;BR /&gt;------------------------------------------------------------|-----------------------------------------------------------                               | PWRK             |  6.1    |  8-OCT-2007 | S     | S     | XXXXXX | SYSTEM  &lt;BR /&gt;&lt;BR /&gt;However, when I carry out the next step, i.e. run Sys$Update:PWRK$CONFIG.COM, I get;&lt;BR /&gt;&lt;BR /&gt;%SYSMAN-I-NODERR, error returned from node XXXXXX&lt;BR /&gt;-SYSTEM-W-SYSVERDIF, system version mismatch; please relink&lt;BR /&gt;%SYSMAN-I-NODERR, error returned from node XXXXXX&lt;BR /&gt;-SYSTEM-W-SYSVERDIF, system version mismatch; please relink&lt;BR /&gt;%PWRK-F-NOSUCHDEV, could not load PCFS driver&lt;BR /&gt;&lt;BR /&gt;Can anyone shed any light on where I should go next?&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Oct 2007 07:47:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072921#M86694</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2007-10-08T07:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072922#M86695</link>
      <description>Hi Dave,&lt;BR /&gt;&lt;BR /&gt;From the message, looks like it's not supported. I think you need Pathworks V7.3B advanced server for VMS AXP V8.3&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/pathworks/pwnew.html" target="_blank"&gt;http://h71000.www7.hp.com/pathworks/pwnew.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/pathworks/upgrading.html" target="_blank"&gt;http://h71000.www7.hp.com/pathworks/upgrading.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/pathworks/advancedserver.html" target="_blank"&gt;http://h71000.www7.hp.com/pathworks/advancedserver.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;John.</description>
      <pubDate>Mon, 08 Oct 2007 08:46:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072922#M86695</guid>
      <dc:creator>John Abbott_2</dc:creator>
      <dc:date>2007-10-08T08:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072923#M86696</link>
      <description>Dave,&lt;BR /&gt;&lt;BR /&gt;you will find that this page&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/pathworks/differences.html" target="_blank"&gt;http://h71000.www7.hp.com/pathworks/differences.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;gives details of the supported OS versions.&lt;BR /&gt;&lt;BR /&gt;VMS 8.3 does not appear to be a supported platform for Pathworks 6.1, so you should look at upgrading to 7.3B.&lt;BR /&gt;&lt;BR /&gt;Duncan&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Oct 2007 08:47:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072923#M86696</guid>
      <dc:creator>Duncan Morris</dc:creator>
      <dc:date>2007-10-08T08:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072924#M86697</link>
      <description>I had pretty much reached the same conclusion, and am in the process of extracting the pcsi files for Advanced Server, from the "Layered Products" CD.&lt;BR /&gt;&lt;BR /&gt;Thanks for confirming the solution.&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Mon, 08 Oct 2007 08:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072924#M86697</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2007-10-08T08:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072925#M86698</link>
      <description>hi Dave, you post a reply as to how diffcult your pathworks upgrade went. ie&lt;BR /&gt;any convertions needed etc. curious.  Dean</description>
      <pubDate>Mon, 08 Oct 2007 15:50:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072925#M86698</guid>
      <dc:creator>Dean McGorrill</dc:creator>
      <dc:date>2007-10-08T15:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072926#M86699</link>
      <description>Hi Dean,&lt;BR /&gt;       Only a couple of comments.&lt;BR /&gt;&lt;BR /&gt;1.   I pulled the Advanced Server compressed PCSI file, and the associated manifest file (*.pcsi$compressed_esw), however when I ran "product install" I got some strange messages.  (basically saying that the install process couldn't validate the product because the name supplied was different from the name in the manifest file.)    I tried doing a "product list" and got the same result.    To try to move forward, I renamed the manifest file to *.temp, and reran the "product list".   This time it reported that "...there is supposed to be a manifest file, however I cant find it.   Do you want to continue...?"&lt;BR /&gt;I answered "Yes" to this and it went ahead and displayed the contents of the pcsi file.&lt;BR /&gt;&lt;BR /&gt;    This being the case, (and since I was working on a TEST system with a good backup), I went ahead and ran the "product install" command.   I got the "missing manifest file" message, but told it to continue.     It then went ahead and installed the product without any obvious issues.    &lt;BR /&gt;&lt;BR /&gt;2.    In the process of installing, it sets up the initial parameters.    The only one you might want to keep an eye on is the "Transports".   It defaults to IP, however the implication is that the IP option is for TCPWARE (this may not be true, however I didn't follow up).   I discovered the problem when I tried to start pathworks, I got a message saying that the PWIPDriver needed to be loaded.   Googling for the solution, I only found a reference to TCPWARE (which provides a com file to do this).     In my case, I just ran an "admin/config" command, and changed the transport to DECNet.&lt;BR /&gt;&lt;BR /&gt;Pathworks then started up OK.   &lt;BR /&gt;&lt;BR /&gt;I haven't got fully around to testing yet.&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Oct 2007 06:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072926#M86699</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2007-10-09T06:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: Problem installing PathWorks on Alpha 8.3.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072927#M86700</link>
      <description>The PWIPdriver is supplied with each of the 3 IP stacks supported by OVMS and must be enabled in order to get TCP/IP support in Advanced Server.&lt;BR /&gt;&lt;BR /&gt;With TCP/IP Services for OpenVMS, you enable it in tcpip$config (under Optional Components)...&lt;BR /&gt;&lt;BR /&gt;REgards,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Paul</description>
      <pubDate>Tue, 09 Oct 2007 06:32:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-installing-pathworks-on-alpha-8-3/m-p/5072927#M86700</guid>
      <dc:creator>Paul Nunez</dc:creator>
      <dc:date>2007-10-09T06:32:12Z</dc:date>
    </item>
  </channel>
</rss>

