<?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: EVENT LOG ON VMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5373925#M102326</link>
    <description>&lt;P&gt;accountng.dat is not the right place. Best it can offer is a final error status code for a process that ran into an error.&lt;/P&gt;&lt;P&gt;Hardware errors should be recorded in SYS$ERRORLOG:ERRLOG.SYS&lt;/P&gt;&lt;P&gt;Current OpenVMS version put up ridiculous hurdles to read that file, but best I recall under 6.2, as you indicate, you can just use ANALYZE/ERROR. Check the HELP&lt;/P&gt;&lt;P&gt;Finally you may want to look at SYS$MANAGER:OPERATOR.LOG&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hth,&lt;/P&gt;&lt;P&gt;Hein&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;[Edited to&amp;nbsp;use the full word&amp;nbsp;ANALYZE instead of its first 4 charaters which were **bleep**-ed. assholes.]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2011 12:42:04 GMT</pubDate>
    <dc:creator>Hein van den Heuvel</dc:creator>
    <dc:date>2011-10-27T12:42:04Z</dc:date>
    <item>
      <title>EVENT LOG ON VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5373919#M102325</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;Is / are they are logs etc that I could look at on a VMS 6.2 system to check events like failed disks etc and why they happened&lt;/P&gt;&lt;P&gt;I was thinking accounting.dat - is there any quick way / basic commands to interrogate this ?&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 12:30:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5373919#M102325</guid>
      <dc:creator>gunners</dc:creator>
      <dc:date>2011-10-27T12:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: EVENT LOG ON VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5373925#M102326</link>
      <description>&lt;P&gt;accountng.dat is not the right place. Best it can offer is a final error status code for a process that ran into an error.&lt;/P&gt;&lt;P&gt;Hardware errors should be recorded in SYS$ERRORLOG:ERRLOG.SYS&lt;/P&gt;&lt;P&gt;Current OpenVMS version put up ridiculous hurdles to read that file, but best I recall under 6.2, as you indicate, you can just use ANALYZE/ERROR. Check the HELP&lt;/P&gt;&lt;P&gt;Finally you may want to look at SYS$MANAGER:OPERATOR.LOG&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hth,&lt;/P&gt;&lt;P&gt;Hein&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;[Edited to&amp;nbsp;use the full word&amp;nbsp;ANALYZE instead of its first 4 charaters which were **bleep**-ed. assholes.]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 12:42:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5373925#M102326</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2011-10-27T12:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: EVENT LOG ON VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5374037#M102327</link>
      <description>&lt;P&gt;Or, if your system was under maintenance at one time, you may have DECevent.&amp;nbsp; ANALYZE/ERROR for V6.2 did the job but was a little basic.&amp;nbsp; DECevent, at the time, had some slight advantages.&amp;nbsp; Search for DECEVENT$STARTUP.COM or try using the DIAG command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both are exceptional when compared to the current solutions especially if your system is in a tightly secured environment or totally standalone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;bob&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 13:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5374037#M102327</guid>
      <dc:creator>Bob Blunt</dc:creator>
      <dc:date>2011-10-27T13:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: EVENT LOG ON VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5374073#M102328</link>
      <description>&lt;P&gt;Brilliant Folks, thanks , thats given me loads to go on - thanks a mill as always , I get so much&amp;nbsp;learning from these forums&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 13:56:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/event-log-on-vms/m-p/5374073#M102328</guid>
      <dc:creator>gunners</dc:creator>
      <dc:date>2011-10-27T13:56:48Z</dc:date>
    </item>
  </channel>
</rss>

