<?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: Command used to install a software/package in OpenVMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944671#M73058</link>
    <description>That depends on the format of the software package.&lt;BR /&gt;&lt;BR /&gt;- you may have a VMSINSTALable kit, these are in BACKUP format and consist of backup savesets names .A,.B,... At least a .A saveset is needed. You then install the software using the command:&lt;BR /&gt;  @SYS$UPDATE:VMSINSTAL product location ...&lt;BR /&gt;where product is the filename of the saveset (without .A;vers). Pls. see the system manager's manual for more options to VMSINSTAL&lt;BR /&gt;&lt;BR /&gt;- newer softare packages are created with PRODUCT and are installed with&lt;BR /&gt; PRODUCT INSTALL product /source=....&lt;BR /&gt;Pls. consult the manuals on how to use PRODUCT. &lt;BR /&gt;&lt;BR /&gt;- some software is just UNZIPped to any location, may contain a INSTALL.COM or else&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
    <pubDate>Tue, 06 Dec 2005 05:04:22 GMT</pubDate>
    <dc:creator>Karl Rohwedder</dc:creator>
    <dc:date>2005-12-06T05:04:22Z</dc:date>
    <item>
      <title>Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944670#M73057</link>
      <description>Hi, can someone tell me the "Command used to install a software/package in OpenVMS" ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Tue, 06 Dec 2005 04:51:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944670#M73057</guid>
      <dc:creator>aique</dc:creator>
      <dc:date>2005-12-06T04:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944671#M73058</link>
      <description>That depends on the format of the software package.&lt;BR /&gt;&lt;BR /&gt;- you may have a VMSINSTALable kit, these are in BACKUP format and consist of backup savesets names .A,.B,... At least a .A saveset is needed. You then install the software using the command:&lt;BR /&gt;  @SYS$UPDATE:VMSINSTAL product location ...&lt;BR /&gt;where product is the filename of the saveset (without .A;vers). Pls. see the system manager's manual for more options to VMSINSTAL&lt;BR /&gt;&lt;BR /&gt;- newer softare packages are created with PRODUCT and are installed with&lt;BR /&gt; PRODUCT INSTALL product /source=....&lt;BR /&gt;Pls. consult the manuals on how to use PRODUCT. &lt;BR /&gt;&lt;BR /&gt;- some software is just UNZIPped to any location, may contain a INSTALL.COM or else&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Tue, 06 Dec 2005 05:04:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944671#M73058</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2005-12-06T05:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944672#M73059</link>
      <description>There are two ways&lt;BR /&gt;&lt;BR /&gt;1) if your software comes as several files with an extension .A .B .C (cob023.A, COB023.B for example), you will use vmsinstal, if your files are in dka200:[kits], you will do&lt;BR /&gt;&lt;BR /&gt;@sys$update:vmsinstal product dka200:[kits]&lt;BR /&gt;&lt;BR /&gt;2) if your software has a file with an extension .PCSI, if you file is ABCXXX.PCSI, in dka200:[kits], you will do &lt;BR /&gt;&lt;BR /&gt;$ product instal * /source=dka200:[kits]</description>
      <pubDate>Tue, 06 Dec 2005 05:07:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944672#M73059</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-12-06T05:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944673#M73060</link>
      <description>Didier Morandi wrote a nice command procedure called pcsi_menu.com to generate a pcsi-file.&lt;BR /&gt;&lt;BR /&gt;eberhard&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Dec 2005 05:26:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944673#M73060</guid>
      <dc:creator>Heuser-Hofmann</dc:creator>
      <dc:date>2005-12-06T05:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944674#M73061</link>
      <description>Abdul,&lt;BR /&gt;&lt;BR /&gt;for completeness:&lt;BR /&gt;many packages can be downloaded.&lt;BR /&gt;If they come from HP, they nowadays are usually self-extracting images.&lt;BR /&gt;If the package has an extension of .VAXEXE, .AXPEXE, or ,I64EXE, then you dowload the one for your architecture, and just RUN it. A .PCSI kit will generally be the result, which can be installed using PRODUCT INSTALL, as mentioned above.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Tue, 06 Dec 2005 05:32:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944674#M73061</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-12-06T05:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944675#M73062</link>
      <description>On the PRODUCT INSTALL I also like to use the /SAVE switch so that I can uninstall if there are issues.&lt;BR /&gt;&lt;BR /&gt;You can also see what has been installed by looking at the following areas:&lt;BR /&gt;TYPE SYS$UPDATE:VMSINSTAL.HISTORY&lt;BR /&gt;PRODUCT SHOW HISTORY&lt;BR /&gt;&lt;BR /&gt;Nothing will show you products that have to only be "unzipped" to be installed.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 07 Dec 2005 10:17:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944675#M73062</guid>
      <dc:creator>Peter Zeiszler</dc:creator>
      <dc:date>2005-12-07T10:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Command used to install a software/package in OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944676#M73063</link>
      <description>PRODUCT INSTALL product /source=....&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Dec 2005 00:56:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/command-used-to-install-a-software-package-in-openvms/m-p/4944676#M73063</guid>
      <dc:creator>aique</dc:creator>
      <dc:date>2005-12-08T00:56:28Z</dc:date>
    </item>
  </channel>
</rss>

