<?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: -PROCDUMP-E-NOREAD, no access to location in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597237#M98012</link>
    <description>The process dump file is very likely valid.&lt;BR /&gt;&lt;BR /&gt;It's very likely an application problem. But I may misinterpret the "Their process always crash".&lt;BR /&gt;&lt;BR /&gt;I would make sure that the process dump is analyzed on the system where the "crash" happened. Again, on the very same system I would try to read the process dump with SDA. I would make sure that the latest ECOs for exception handling and the debugger are installed.</description>
    <pubDate>Tue, 09 Mar 2010 10:20:13 GMT</pubDate>
    <dc:creator>H.Becker</dc:creator>
    <dc:date>2010-03-09T10:20:13Z</dc:date>
    <item>
      <title>-PROCDUMP-E-NOREAD, no access to location</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597236#M98011</link>
      <description>Hi , &lt;BR /&gt;  We have customer runing IA64 HP OpenVMS, 8.3-1H1 . Their process always crash many time and AP vendor still can not find out why ?&lt;BR /&gt;&lt;BR /&gt;We suggest then open debug option and get process dump file to analyze .&lt;BR /&gt;&lt;BR /&gt;During the AP process dump , getting following message :&lt;BR /&gt;%PROCDUMP-W-BADLOGIC, internal logic error detected at PC 00000000.7B5D3160&lt;BR /&gt;-PROCDUMP-E-NOREAD, no access to location 22000580.0A211801, length 00000000.000000B8, requested at PC 00000000.7B5D1840&lt;BR /&gt;&lt;BR /&gt;We want to know&lt;BR /&gt;1. if the process dump file still valid ?&lt;BR /&gt;2. it maybe system or AP oriented issue ?&lt;BR /&gt;3. From system view , any tip we can help the AP vendor to debug the crash issue ?&lt;BR /&gt;&lt;BR /&gt;  Thank in advance !&lt;BR /&gt;&lt;BR /&gt;- Honda</description>
      <pubDate>Tue, 09 Mar 2010 08:10:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597236#M98011</guid>
      <dc:creator>Honda_2</dc:creator>
      <dc:date>2010-03-09T08:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: -PROCDUMP-E-NOREAD, no access to location</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597237#M98012</link>
      <description>The process dump file is very likely valid.&lt;BR /&gt;&lt;BR /&gt;It's very likely an application problem. But I may misinterpret the "Their process always crash".&lt;BR /&gt;&lt;BR /&gt;I would make sure that the process dump is analyzed on the system where the "crash" happened. Again, on the very same system I would try to read the process dump with SDA. I would make sure that the latest ECOs for exception handling and the debugger are installed.</description>
      <pubDate>Tue, 09 Mar 2010 10:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597237#M98012</guid>
      <dc:creator>H.Becker</dc:creator>
      <dc:date>2010-03-09T10:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: -PROCDUMP-E-NOREAD, no access to location</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597238#M98013</link>
      <description>Sorry , I should say &lt;BR /&gt;The critical user process crash many times.&lt;BR /&gt;&lt;BR /&gt;This machine is going to production so the ECO should already uptodate , to make sure I would verify with user tomorrow .&lt;BR /&gt;&lt;BR /&gt;We transfer the dump file to AP vendor and forget to veriy in local machine , would also veriy tomorrow .&lt;BR /&gt;&lt;BR /&gt;Thank you so much for giving the hints :-)</description>
      <pubDate>Tue, 09 Mar 2010 14:16:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597238#M98013</guid>
      <dc:creator>Honda_2</dc:creator>
      <dc:date>2010-03-09T14:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: -PROCDUMP-E-NOREAD, no access to location</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597239#M98014</link>
      <description>Customer ECO already up to date .&lt;BR /&gt;We make sure the dump is ok and now please AP vendor do their buziness .&lt;BR /&gt;&lt;BR /&gt;Thank you so much !</description>
      <pubDate>Thu, 11 Mar 2010 05:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/procdump-e-noread-no-access-to-location/m-p/4597239#M98014</guid>
      <dc:creator>Honda_2</dc:creator>
      <dc:date>2010-03-11T05:27:24Z</dc:date>
    </item>
  </channel>
</rss>

