<?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: CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029971#M35740</link>
    <description>Concur.  On both.  Flag it to HP?</description>
    <pubDate>Thu, 22 Feb 2007 10:52:41 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-02-22T10:52:41Z</dc:date>
    <item>
      <title>CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029970#M35739</link>
      <description>I didn't expect this behavior.  Should I have?&lt;BR /&gt;&lt;BR /&gt;ALP2 $ show proc /pars&lt;BR /&gt;[...]&lt;BR /&gt;Parse Style: Extended&lt;BR /&gt;&lt;BR /&gt;Ok.  Let's make some files and symbolic links.&lt;BR /&gt;&lt;BR /&gt;ALP2 $ copy nl: plain.file&lt;BR /&gt;ALP2 $ create /symlink = plain.file symbolic.link&lt;BR /&gt;ALP2 $ create /symlink = "plain.file" symbolic.link_quoted&lt;BR /&gt;&lt;BR /&gt;ALP2 $ dire /size&lt;BR /&gt;&lt;BR /&gt;Directory DKA0:[test]&lt;BR /&gt;&lt;BR /&gt;plain.file;1               0&lt;BR /&gt;SYMBOLIC.LINK;1 -&amp;gt; PLAIN.FILE&lt;BR /&gt;                           1&lt;BR /&gt;SYMBOLIC.LINK_QUOTED;1 -&amp;gt; plain.file&lt;BR /&gt;                           1&lt;BR /&gt;Total of 3 files, 2 blocks.&lt;BR /&gt;&lt;BR /&gt;So, it appears to me that CREATE /SYMLINK&lt;BR /&gt;generally ignores the process parse style.&lt;BR /&gt;This is not what I'd expected.  Any wisdom?&lt;BR /&gt;&lt;BR /&gt;ALP2 $ tcpip show version&lt;BR /&gt;&lt;BR /&gt;  HP TCP/IP Services for OpenVMS Alpha Version V5.6&lt;BR /&gt;  on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3&lt;BR /&gt;&lt;BR /&gt;(Also, who else thinks that a plain DCL "SHOW&lt;BR /&gt;VERSION" command would be handy?)&lt;BR /&gt;&lt;BR /&gt;Naturally, that's an ODS5 disk.</description>
      <pubDate>Thu, 22 Feb 2007 08:00:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029970#M35739</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2007-02-22T08:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029971#M35740</link>
      <description>Concur.  On both.  Flag it to HP?</description>
      <pubDate>Thu, 22 Feb 2007 10:52:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029971#M35740</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-02-22T10:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029972#M35741</link>
      <description>I don't have access to a VMS 8.3 system but I'd be curious to see the verb definition in SYS$UPDATE:CREATE.CLD.&lt;BR /&gt;&lt;BR /&gt;If it has this line:&lt;BR /&gt;qualifier symlink value&lt;BR /&gt;&lt;BR /&gt;then to get /symlink=plain.file to work use instead:&lt;BR /&gt;qualifier symlink value(type=$file)&lt;BR /&gt;&lt;BR /&gt;However after that /symlink="plain.file" will probably not work because the CLI calls won't strip the "s from the value so the outer code must do it.  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Feb 2007 13:42:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029972#M35741</guid>
      <dc:creator>Jess Goodman</dc:creator>
      <dc:date>2007-02-22T13:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029973#M35742</link>
      <description>&lt;!--!*#--&gt;VERB claims that it's:&lt;BR /&gt;&lt;BR /&gt;define verb CREATE&lt;BR /&gt;   image CREATE&lt;BR /&gt;   parameter P1, label=OUTPUT, prompt="File"&lt;BR /&gt;      value (required,list,impcat,type=$outfile)&lt;BR /&gt;[...]&lt;BR /&gt;   qualifier SYMLINK, nonnegatable&lt;BR /&gt;      value (required)&lt;BR /&gt;[...]&lt;BR /&gt;&lt;BR /&gt;I can see why the link _target_ might need to&lt;BR /&gt;be quoted (as it may not be a VMS/RMS file&lt;BR /&gt;name), but not the file (symlink) itself.&lt;BR /&gt;Plain-old CREATE works as expected:&lt;BR /&gt;&lt;BR /&gt;ALP2 $ pipe create fred.dat &amp;lt; nl:&lt;BR /&gt;ALP2 $ dg fred&lt;BR /&gt;&lt;BR /&gt;Directory DKA0:[test]&lt;BR /&gt;&lt;BR /&gt;fred.dat;1                  0   2-MAR-2007 12:19:22.43  (RWED,RWED,RE,)&lt;BR /&gt;&lt;BR /&gt;Total of 1 file, 0 blocks.&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Mar 2007 13:20:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029973#M35742</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2007-03-02T13:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: CREATE /SYMLINK v. SET PROCESS /PARSE_STYLE = EXTENDED</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029974#M35743</link>
      <description>An informal not-really-support request&lt;BR /&gt;resulted in an admission of guilt, and&lt;BR /&gt;offered some hope for a fix at some (future)&lt;BR /&gt;time for the problem with the link name.&lt;BR /&gt;&lt;BR /&gt;Currently, the suggested work-around is to&lt;BR /&gt;define a DEC C feature logical name first&lt;BR /&gt;(and it'd probably be wise to clear it soon&lt;BR /&gt;afterward):&lt;BR /&gt;&lt;BR /&gt;DEFINE DECC$EFS_CASE_PRESERVE ENABLE&lt;BR /&gt;&lt;BR /&gt;because DCL is using the C RTL to do the job,&lt;BR /&gt;but it's not setting the features according&lt;BR /&gt;to the /PARSE_STYLE setting.&lt;BR /&gt;&lt;BR /&gt;Case preservation of the link text may&lt;BR /&gt;continue to require quotation.</description>
      <pubDate>Thu, 29 Mar 2007 00:17:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/create-symlink-v-set-process-parse-style-extended/m-p/5029974#M35743</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2007-03-29T00:17:12Z</dc:date>
    </item>
  </channel>
</rss>

