<?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 image file identification in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131894#M13856</link>
    <description>I am currently porting software from the ALPHA to the HP Integrity (I64).&lt;BR /&gt;&lt;BR /&gt;On the ALPHA, I was able to programmable read and write to the ‘image file identification’ and ‘image file build identification’ fields in the header record of an executable.&lt;BR /&gt;&lt;BR /&gt;On the I64 with the ELF executables have been unable to determine how to do this.&lt;BR /&gt;&lt;BR /&gt;Can you tell me how to access the ‘image file identification’ and ‘image file build identification’ fields in the ELF executable on the I64?&lt;BR /&gt;</description>
    <pubDate>Fri, 18 Jan 2008 15:55:39 GMT</pubDate>
    <dc:creator>James Trickey</dc:creator>
    <dc:date>2008-01-18T15:55:39Z</dc:date>
    <item>
      <title>image file identification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131894#M13856</link>
      <description>I am currently porting software from the ALPHA to the HP Integrity (I64).&lt;BR /&gt;&lt;BR /&gt;On the ALPHA, I was able to programmable read and write to the ‘image file identification’ and ‘image file build identification’ fields in the header record of an executable.&lt;BR /&gt;&lt;BR /&gt;On the I64 with the ELF executables have been unable to determine how to do this.&lt;BR /&gt;&lt;BR /&gt;Can you tell me how to access the ‘image file identification’ and ‘image file build identification’ fields in the ELF executable on the I64?&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Jan 2008 15:55:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131894#M13856</guid>
      <dc:creator>James Trickey</dc:creator>
      <dc:date>2008-01-18T15:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: image file identification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131895#M13857</link>
      <description>See HELP SHOW IMAGE</description>
      <pubDate>Fri, 18 Jan 2008 16:03:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131895#M13857</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2008-01-18T16:03:45Z</dc:date>
    </item>
    <item>
      <title>Re: image file identification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131896#M13858</link>
      <description>ELF headers are sort of easier, because there is a standard definition for them.&lt;BR /&gt;They are not OpenVMS specific.&lt;BR /&gt;&lt;BR /&gt;Do you want the ID for the 'current running image', or just a tool to get at it?&lt;BR /&gt;&lt;BR /&gt;Anyway, check out the prior topic below.&lt;BR /&gt;I'm pretty sure it answers your question and then some.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1105618" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1105618&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Jan 2008 16:06:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-file-identification/m-p/4131896#M13858</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2008-01-18T16:06:20Z</dc:date>
    </item>
  </channel>
</rss>

