<?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 OpenVMS Diagnostics File Format in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757968#M41151</link>
    <description>Is the format of the diagnostics file (*.dia) that OpenVMS compilers produce via the /diagnostics qualifier documented anywhere?&lt;BR /&gt;&lt;BR /&gt;I would like to be able to utilize this information from tools other than LSE.  For example, emacs(XEmacs) has a next-error function that is normally bound to "control-X ~" which goes to the next error in a compilation.&lt;BR /&gt;</description>
    <pubDate>Thu, 24 Feb 2011 21:58:34 GMT</pubDate>
    <dc:creator>BruceVisscher</dc:creator>
    <dc:date>2011-02-24T21:58:34Z</dc:date>
    <item>
      <title>OpenVMS Diagnostics File Format</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757968#M41151</link>
      <description>Is the format of the diagnostics file (*.dia) that OpenVMS compilers produce via the /diagnostics qualifier documented anywhere?&lt;BR /&gt;&lt;BR /&gt;I would like to be able to utilize this information from tools other than LSE.  For example, emacs(XEmacs) has a next-error function that is normally bound to "control-X ~" which goes to the next error in a compilation.&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Feb 2011 21:58:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757968#M41151</guid>
      <dc:creator>BruceVisscher</dc:creator>
      <dc:date>2011-02-24T21:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Diagnostics File Format</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757969#M41152</link>
      <description>The compiler diagnostics .DIA file and record format is not publicly documented by HP.  &lt;BR /&gt;&lt;BR /&gt;Nor is the analysis file format; the .ANA files.&lt;BR /&gt;&lt;BR /&gt;You'd likely need to discuss this request with HP.&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Feb 2011 22:03:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757969#M41152</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2011-02-24T22:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Diagnostics File Format</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757970#M41153</link>
      <description>Hoff,&lt;BR /&gt;&lt;BR /&gt;Thanks.  I was afraid that might be the case.  Oh well.&lt;BR /&gt;&lt;BR /&gt;Bruce</description>
      <pubDate>Thu, 24 Feb 2011 22:15:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757970#M41153</guid>
      <dc:creator>BruceVisscher</dc:creator>
      <dc:date>2011-02-24T22:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Diagnostics File Format</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757971#M41154</link>
      <description>Hi Bruce,&lt;BR /&gt;&lt;BR /&gt;You can route your query to HP via Office of OpenVMS programs.&lt;BR /&gt;The email id is - OpenVMS.Programs@hp.com.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Murali</description>
      <pubDate>Fri, 25 Feb 2011 02:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-diagnostics-file-format/m-p/4757971#M41154</guid>
      <dc:creator>P Muralidhar Kini</dc:creator>
      <dc:date>2011-02-25T02:24:20Z</dc:date>
    </item>
  </channel>
</rss>

