<?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: Reflections IA64_LINK Runtime Errors in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168391#M94115</link>
    <description>I don't that IA64_LINK is what you think it is. See SYS$HELP:VMS831H1I_IA64_LINK-V0100.RELEASE_NOTES which informs that in addition to the the executable, a new CLD is provided (SYS$COMMON:[SYSUPD]IA64_LINK.CLD). Inspecting the CLD you'll see that the verb defined is LINK. IA64_LINK is the VMS linker utility (and not the I64 equivalent of the Reflection file transfer utility previously named VAXLINK2).</description>
    <pubDate>Tue, 07 Apr 2009 10:17:07 GMT</pubDate>
    <dc:creator>Jim_McKinney</dc:creator>
    <dc:date>2009-04-07T10:17:07Z</dc:date>
    <item>
      <title>Reflections IA64_LINK Runtime Errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168389#M94113</link>
      <description>&lt;!--!*#--&gt;I had IA64_LINK (VAXLINK2) running on my Itanium server, but it's now failing with errors below. My guess is that some of the recent patches has upset it in some way.&lt;BR /&gt;&lt;BR /&gt;Can anyone help to identify the problem?&lt;BR /&gt;&lt;BR /&gt;Rob.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;CURIE_RAA$ run IA64_LINK.EXE&lt;BR /&gt;%ILINK-F-SYNTAX, unable to parse the command line: either the command&lt;BR /&gt;        definition (CLD file) is incompatible or a foreign command was used&lt;BR /&gt;-CLI-F-SYNTAX, error parsing 'TRACE'&lt;BR /&gt;-CLI-E-ENTNF, specified entity not found in command tables&lt;BR /&gt;%ILINK-F-SYNTAX, unable to parse the command line: either the command&lt;BR /&gt;        definition (CLD file) is incompatible or a foreign command was used&lt;BR /&gt;-CLI-F-SYNTAX, error parsing 'CONTIGUOUS'&lt;BR /&gt;-CLI-E-ENTNF, specified entity not found in command tables&lt;BR /&gt;%ILINK-F-SYNTAX, unable to parse the command line: either the command&lt;BR /&gt;        definition (CLD file) is incompatible or a foreign command was used&lt;BR /&gt;-CLI-F-SYNTAX, error parsing 'P0IMAGE'&lt;BR /&gt;-CLI-E-ENTNF, specified entity not found in command tables&lt;BR /&gt;%ILINK-F-SYNTAX, unable to parse the command line: either the command&lt;BR /&gt;        definition (CLD file) is incompatible or a foreign command was used&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Apr 2009 09:19:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168389#M94113</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-04-07T09:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: Reflections IA64_LINK Runtime Errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168390#M94114</link>
      <description>&lt;!--!*#--&gt;I've managed to get it working by renaming it to something else :-&lt;BR /&gt;&lt;BR /&gt;Directory SYS$COMMON:[SYSEXE]&lt;BR /&gt;&lt;BR /&gt;IA64LK.EXE;2                       2526/2528      7-APR-2009 11:25:43.84&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Not sure what's going on. Perhaps IA64_LINK is some kind of reserved name on Itanium?&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Tue, 07 Apr 2009 09:53:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168390#M94114</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-04-07T09:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Reflections IA64_LINK Runtime Errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168391#M94115</link>
      <description>I don't that IA64_LINK is what you think it is. See SYS$HELP:VMS831H1I_IA64_LINK-V0100.RELEASE_NOTES which informs that in addition to the the executable, a new CLD is provided (SYS$COMMON:[SYSUPD]IA64_LINK.CLD). Inspecting the CLD you'll see that the verb defined is LINK. IA64_LINK is the VMS linker utility (and not the I64 equivalent of the Reflection file transfer utility previously named VAXLINK2).</description>
      <pubDate>Tue, 07 Apr 2009 10:17:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168391#M94115</guid>
      <dc:creator>Jim_McKinney</dc:creator>
      <dc:date>2009-04-07T10:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Reflections IA64_LINK Runtime Errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168392#M94116</link>
      <description>Hi Jim.&lt;BR /&gt;&lt;BR /&gt;I'd also found that as well, after some Googling. My original reaction was that a patch had killed it, which in effect it had, as it overwrote my Reflections version of IA64_LINK.EXE.&lt;BR /&gt;&lt;BR /&gt;How unlucky can a man be to pick the same name as a new patch file?&lt;BR /&gt;&lt;BR /&gt;Cheers Rob.</description>
      <pubDate>Tue, 07 Apr 2009 11:02:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/reflections-ia64-link-runtime-errors/m-p/5168392#M94116</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-04-07T11:02:49Z</dc:date>
    </item>
  </channel>
</rss>

