<?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: DCL Script with parameter / in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863549#M78971</link>
    <description>&lt;!--!*#--&gt;If you define the command cd as&lt;BR /&gt;&lt;BR /&gt;$ cd :== @somefixedplace:cd x """"&lt;BR /&gt;&lt;BR /&gt;Then the 2nd parameter will contain everything that is entered after the command in whatever case is entered.&lt;BR /&gt;&lt;BR /&gt;Here's a short example:&lt;BR /&gt;&lt;BR /&gt;test.com contains the one line&lt;BR /&gt;$ sho sym p%&lt;BR /&gt;&lt;BR /&gt;If I define the command cd as&lt;BR /&gt;&lt;BR /&gt;$ cd :== @test X """&lt;BR /&gt;&lt;BR /&gt;and enter the command &lt;BR /&gt;&lt;BR /&gt;$ cd/this /is /a TEST&lt;BR /&gt;&lt;BR /&gt;Here is the output:&lt;BR /&gt;&lt;BR /&gt;  P1 = "X"&lt;BR /&gt;  P2 = " /this /is /a TEST"&lt;BR /&gt;  P3 = ""&lt;BR /&gt;  P4 = ""&lt;BR /&gt;  P5 = ""&lt;BR /&gt;  P6 = ""&lt;BR /&gt;  P7 = ""&lt;BR /&gt;  P8 = ""&lt;BR /&gt;&lt;BR /&gt;$ cd /this is a /test&lt;BR /&gt;&lt;BR /&gt;  P1 = "X"&lt;BR /&gt;  P2 = " /this is a /test"&lt;BR /&gt;  P3 = ""&lt;BR /&gt;  P4 = ""&lt;BR /&gt;  P5 = ""&lt;BR /&gt;  P6 = ""&lt;BR /&gt;  P7 = ""&lt;BR /&gt;  P8 = ""&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Ken</description>
    <pubDate>Fri, 15 Sep 2006 11:56:20 GMT</pubDate>
    <dc:creator>Ken Robinson</dc:creator>
    <dc:date>2006-09-15T11:56:20Z</dc:date>
    <item>
      <title>DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863546#M78968</link>
      <description>&lt;!--!*#--&gt;Hi,&lt;BR /&gt;Can we use / as commandscript parameter ?&lt;BR /&gt;&lt;BR /&gt;Purpose is I want to create an enviornment where some of the Unix command work (cd, ls,mkdir etc.) in VMS.&lt;BR /&gt;E.g.&lt;BR /&gt;@CD /usr/bin&lt;BR /&gt;As per my analysis DCL will throw an error if we use / as parameter. &lt;BR /&gt;@CD "/" will work , but I can not ask the user to enter a command @CD "/usr/bin"&lt;BR /&gt;&lt;BR /&gt;Please suggest &lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sethu&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Sep 2006 09:34:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863546#M78968</guid>
      <dc:creator>Sethunath K.O</dc:creator>
      <dc:date>2006-09-15T09:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863547#M78969</link>
      <description>&lt;BR /&gt;Well, you don't really want your users to type @CD anyway right? Not knowing where CD lives and all that?&lt;BR /&gt;&lt;BR /&gt;So you could define "$CD = @some_fixed_place:cd.com X"&lt;BR /&gt;&lt;BR /&gt;Now, if for example you use: $CD /usr&lt;BR /&gt;The in CD.COM the P1 will be "X" and P1 will be /USR  (uppercased!)&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Sep 2006 09:53:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863547#M78969</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2006-09-15T09:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863548#M78970</link>
      <description>&amp;gt; The in CD.COM the P1 will be "X" and P1 will be /USR (uppercased!)&lt;BR /&gt;&lt;BR /&gt;Oops, submitted before proofreading...&lt;BR /&gt;&lt;BR /&gt;Then in the context of CD.COM the paramater P1 will be "X" and P2 will be /USR (uppercased!)&lt;BR /&gt;&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Sep 2006 09:55:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863548#M78970</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2006-09-15T09:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863549#M78971</link>
      <description>&lt;!--!*#--&gt;If you define the command cd as&lt;BR /&gt;&lt;BR /&gt;$ cd :== @somefixedplace:cd x """"&lt;BR /&gt;&lt;BR /&gt;Then the 2nd parameter will contain everything that is entered after the command in whatever case is entered.&lt;BR /&gt;&lt;BR /&gt;Here's a short example:&lt;BR /&gt;&lt;BR /&gt;test.com contains the one line&lt;BR /&gt;$ sho sym p%&lt;BR /&gt;&lt;BR /&gt;If I define the command cd as&lt;BR /&gt;&lt;BR /&gt;$ cd :== @test X """&lt;BR /&gt;&lt;BR /&gt;and enter the command &lt;BR /&gt;&lt;BR /&gt;$ cd/this /is /a TEST&lt;BR /&gt;&lt;BR /&gt;Here is the output:&lt;BR /&gt;&lt;BR /&gt;  P1 = "X"&lt;BR /&gt;  P2 = " /this /is /a TEST"&lt;BR /&gt;  P3 = ""&lt;BR /&gt;  P4 = ""&lt;BR /&gt;  P5 = ""&lt;BR /&gt;  P6 = ""&lt;BR /&gt;  P7 = ""&lt;BR /&gt;  P8 = ""&lt;BR /&gt;&lt;BR /&gt;$ cd /this is a /test&lt;BR /&gt;&lt;BR /&gt;  P1 = "X"&lt;BR /&gt;  P2 = " /this is a /test"&lt;BR /&gt;  P3 = ""&lt;BR /&gt;  P4 = ""&lt;BR /&gt;  P5 = ""&lt;BR /&gt;  P6 = ""&lt;BR /&gt;  P7 = ""&lt;BR /&gt;  P8 = ""&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Ken</description>
      <pubDate>Fri, 15 Sep 2006 11:56:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863549#M78971</guid>
      <dc:creator>Ken Robinson</dc:creator>
      <dc:date>2006-09-15T11:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863550#M78972</link>
      <description>Sethu,&lt;BR /&gt;let me start with&lt;BR /&gt;WELCOME to VMS and to this forum! &lt;BR /&gt;&lt;BR /&gt;Hein,&lt;BR /&gt;I think Sethu is entitled to a little explanation.&lt;BR /&gt;&lt;BR /&gt;So Sethu, here goes:&lt;BR /&gt;&lt;BR /&gt;/ in VMS normally denotes a qualifier (compare the Unix - , denoting a what U* calls a switch)&lt;BR /&gt;The @ ("execute whatever you find at") command behaves similar but not the same: it only accepts maximum of one qualifier, and only if given directly after the name of the file to be executed. All other command line elements (maximum 8, separated by spaces) are command parameters, which are automatically available within the activated procedure as the symbols P1 to P8.&lt;BR /&gt;&lt;BR /&gt;So, Hein is "cheating" around the treating /USR as a qualifier by adding a dummy param.&lt;BR /&gt;The symbol CD will be replaced by its value&lt;BR /&gt;@some_fixed_place:cd.com X&lt;BR /&gt;in the command line evaluation, and then /usr/bin wil be added, resulting in&lt;BR /&gt;@some_fixed_place:cd.com X /usr/bin.&lt;BR /&gt;Now, CD.COM should never ever look at P1, but process P2. which holds the value of /USR/BIN&lt;BR /&gt;If you really need that as lowercase, then put it betweeb quotes on your command line. (same if you need embedded spaces or other special chars).&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&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Sep 2006 12:16:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863550#M78972</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-09-15T12:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863551#M78973</link>
      <description>Maybe my example of a U*x compatible "cd" command will be usefull for how it handles the "/" case:&lt;BR /&gt;&lt;BR /&gt;cd is defined as: CD == "@DCL$PATH:CD #"&lt;BR /&gt;&lt;BR /&gt;Then dcl$path:cd.com is the one at&lt;BR /&gt;    &lt;A href="http://wwwvms.mppmu.mpg.de/util_root/com/cd.com" target="_blank"&gt;http://wwwvms.mppmu.mpg.de/util_root/com/cd.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;It uses a program path_to_directory from&lt;BR /&gt; &lt;A href="http://wwwvms.mppmu.mpg.de/~huber/util/main/path_to_directory.c" target="_blank"&gt;http://wwwvms.mppmu.mpg.de/~huber/util/main/path_to_directory.c&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and needs for the "cd ~user" case a program UD&lt;BR /&gt; from &lt;BR /&gt;&lt;A href="http://wwwvms.mppmu.mpg.de/vmssig/archive/u/ud.zip" target="_blank"&gt;http://wwwvms.mppmu.mpg.de/vmssig/archive/u/ud.zip&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;whichh needs to be installed with SYSPRV to get another users home directory (if this is allowed at Your site).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Sep 2006 14:00:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863551#M78973</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2006-09-15T14:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: DCL Script with parameter /</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863552#M78974</link>
      <description>Hi Hein , Ken ,  Jan van den Ende,&amp;amp;  Joseph Huber  &lt;BR /&gt;&lt;BR /&gt;Thanks very much for your time and help. It is working fine for me &lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;BR /&gt;Sethu&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Sep 2006 08:07:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dcl-script-with-parameter/m-p/3863552#M78974</guid>
      <dc:creator>Sethunath K.O</dc:creator>
      <dc:date>2006-09-18T08:07:57Z</dc:date>
    </item>
  </channel>
</rss>

