<?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: NANQ in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443686#M42459</link>
    <description>If You program in Fortran, see in addition &lt;BR /&gt; HELP FORTRAN /IEEE_MODEand &lt;BR /&gt; HELP FORTRAN INTRINSIC ERRSNS&lt;BR /&gt;</description>
    <pubDate>Sat, 20 Jun 2009 13:49:56 GMT</pubDate>
    <dc:creator>Joseph Huber_1</dc:creator>
    <dc:date>2009-06-20T13:49:56Z</dc:date>
    <item>
      <title>NANQ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443684#M42457</link>
      <description>I do math calculation in OpenVMS I64. Many a time it is due to divided by zero, sqrt of -VE number etc. How to stop the application without proceeding further? In general how to handle it?</description>
      <pubDate>Sat, 20 Jun 2009 10:46:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443684#M42457</guid>
      <dc:creator>R Samantaray_1</dc:creator>
      <dc:date>2009-06-20T10:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: NANQ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443685#M42458</link>
      <description>&lt;!--!*#--&gt;Patient: "Doctor, it hurts when I do this."&lt;BR /&gt;Doctor: "Don't do that."&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I do math calculation in OpenVMS I64. [...]&lt;BR /&gt;&lt;BR /&gt;Language?  VMS is a big place.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; In general how to handle it?&lt;BR /&gt;&lt;BR /&gt;"In general" is also a big place.&lt;BR /&gt;&lt;BR /&gt;Many programming languages offer an "if"&lt;BR /&gt;statement, which can be used to check for&lt;BR /&gt;valid data before performing any calculation&lt;BR /&gt;which has an obvious restriction on its&lt;BR /&gt;domain.&lt;BR /&gt;&lt;BR /&gt;Alternatively, in many environments, one can&lt;BR /&gt;establish an exception/signal handler,&lt;BR /&gt;letting a program's execution path change&lt;BR /&gt;when a math error occurs.&lt;BR /&gt;&lt;BR /&gt;HELP CRTL signal&lt;BR /&gt;HELP RTL_ROUTINES LIB$ LIB$ESTABLISH&lt;BR /&gt;[...]</description>
      <pubDate>Sat, 20 Jun 2009 12:45:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443685#M42458</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-06-20T12:45:25Z</dc:date>
    </item>
    <item>
      <title>Re: NANQ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443686#M42459</link>
      <description>If You program in Fortran, see in addition &lt;BR /&gt; HELP FORTRAN /IEEE_MODEand &lt;BR /&gt; HELP FORTRAN INTRINSIC ERRSNS&lt;BR /&gt;</description>
      <pubDate>Sat, 20 Jun 2009 13:49:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443686#M42459</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2009-06-20T13:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: NANQ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443687#M42460</link>
      <description>What's wrong with your Quiet NaN?  You can check for those at convenient points.&lt;BR /&gt;Or if you have IEEE, you can check the flags there.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Steven: Many programming languages offer an "if" statement, which can be used to check for&lt;BR /&gt;valid data before performing any calculation&lt;BR /&gt;&lt;BR /&gt;IEEE FP operations defines all inputs with valid outputs that can be checked later.</description>
      <pubDate>Sat, 20 Jun 2009 23:56:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443687#M42460</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-06-20T23:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: NANQ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443688#M42461</link>
      <description>Especially, in the development stage it is one of the very handy things of OpenVMS that you can set the program to stop and give full trace-back when something weird occurs (i.e. divide by zero, write/read outside the array boundaries etc...).&lt;BR /&gt;&lt;BR /&gt;On my Alpha's I normally run in VAX-float mode and use the /check=all on the compiler line.&lt;BR /&gt;This forces all the run time errors to be flagged and the program to stop and write a trace-back.&lt;BR /&gt;&lt;BR /&gt;You can also use the /check qualifier to test only for the i.e. divide by zero. See the user manual of the compiler, for the possible options.&lt;BR /&gt;&lt;BR /&gt;                Jouk</description>
      <pubDate>Mon, 22 Jun 2009 08:06:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nanq/m-p/4443688#M42461</guid>
      <dc:creator>Jansen_8</dc:creator>
      <dc:date>2009-06-22T08:06:13Z</dc:date>
    </item>
  </channel>
</rss>

