<?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 AST notification of socket disconnection? BGDRIVER QIO API in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003210#M55379</link>
    <description>Is it possible to set up an  AST notification of a socket being closed by the remote side?  A READATTN AST doesn't seem to be triggered on this event.&lt;BR /&gt;&lt;BR /&gt;If it isn't possible to get an AST, is there a call that would detect the close without doing a read/write?&lt;BR /&gt;&lt;BR /&gt;I can see how to fix the problem by doing a read to generate the closed error, but that requires code changes to handle&lt;BR /&gt;a successful read at that point in the code.&lt;BR /&gt;&lt;BR /&gt;I'm using the BGDRIVER QIO API from Basic.&lt;BR /&gt;&lt;BR /&gt;Jonathan&lt;BR /&gt;</description>
    <pubDate>Fri, 18 May 2007 15:34:30 GMT</pubDate>
    <dc:creator>Jonathan Cronin</dc:creator>
    <dc:date>2007-05-18T15:34:30Z</dc:date>
    <item>
      <title>AST notification of socket disconnection? BGDRIVER QIO API</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003210#M55379</link>
      <description>Is it possible to set up an  AST notification of a socket being closed by the remote side?  A READATTN AST doesn't seem to be triggered on this event.&lt;BR /&gt;&lt;BR /&gt;If it isn't possible to get an AST, is there a call that would detect the close without doing a read/write?&lt;BR /&gt;&lt;BR /&gt;I can see how to fix the problem by doing a read to generate the closed error, but that requires code changes to handle&lt;BR /&gt;a successful read at that point in the code.&lt;BR /&gt;&lt;BR /&gt;I'm using the BGDRIVER QIO API from Basic.&lt;BR /&gt;&lt;BR /&gt;Jonathan&lt;BR /&gt;</description>
      <pubDate>Fri, 18 May 2007 15:34:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003210#M55379</guid>
      <dc:creator>Jonathan Cronin</dc:creator>
      <dc:date>2007-05-18T15:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: AST notification of socket disconnection? BGDRIVER QIO API</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003211#M55380</link>
      <description>Hi Johnathan,&lt;BR /&gt;&lt;BR /&gt;Your readattnast should fire. What do you have as socket options? (Full_duplex_close, probe_idle, drop_idle)&lt;BR /&gt;&lt;BR /&gt;An alternative to a re-write of your code to cater for a successful read in the wrong place is to ucx$c_msg_peek with a readnowait. If successful the "real" read can take place unhindered at some later stage, and if the socket is closed you'll get the status from the peek.&lt;BR /&gt;&lt;BR /&gt;I too have recently done QIO Socket Programming from BASIC, and strongly suggest a change of language.&lt;BR /&gt;&lt;BR /&gt;Cheers Richard Maher</description>
      <pubDate>Sun, 20 May 2007 03:04:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003211#M55380</guid>
      <dc:creator>Richard J Maher</dc:creator>
      <dc:date>2007-05-20T03:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: AST notification of socket disconnection? BGDRIVER QIO API</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003212#M55381</link>
      <description>The TCPIP$C_FULL_DUPLEX_CLOSE option does the job,&lt;BR /&gt;at least in my little test program.  Thanks!&lt;BR /&gt;&lt;BR /&gt;I don't have any problem with using QIOs in Basic&lt;BR /&gt;(Although I don't use the BASIC$STARLET declaration&lt;BR /&gt;for SY$QIO(W);  declaring every parameter as "by value"&lt;BR /&gt;and using loc() to pass references is more flexible.)&lt;BR /&gt;&lt;BR /&gt;The HP manual on the other hand, is a bit cryptic&lt;BR /&gt;about the item list for socket options.  I had to poke around&lt;BR /&gt;to find examples to learn that you set an option by&lt;BR /&gt;pointing the item at a 1.&lt;BR /&gt;(And I think it was a TCPWARE BGDRIVER example...)&lt;BR /&gt;&lt;BR /&gt;Jonathan&lt;BR /&gt;</description>
      <pubDate>Mon, 21 May 2007 19:13:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003212#M55381</guid>
      <dc:creator>Jonathan Cronin</dc:creator>
      <dc:date>2007-05-21T19:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: AST notification of socket disconnection? BGDRIVER QIO API</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003213#M55382</link>
      <description>Hi Jonathan,&lt;BR /&gt;&lt;BR /&gt;You do a loc(opt_on) and have opt_on declared as an integer with a value of one.&lt;BR /&gt;&lt;BR /&gt;See attached.&lt;BR /&gt;&lt;BR /&gt;Cheers Richard Maher&lt;BR /&gt;&lt;BR /&gt;PS. Maybe it's only me that sees the perfect sense of *compile-time* initialization of these item lists and sockets?&lt;BR /&gt;</description>
      <pubDate>Mon, 21 May 2007 20:36:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003213#M55382</guid>
      <dc:creator>Richard J Maher</dc:creator>
      <dc:date>2007-05-21T20:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: AST notification of socket disconnection? BGDRIVER QIO API</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003214#M55383</link>
      <description>On the other hand if you're using Multinet's BG driver the you receive ss$_shut and ESHUTDOWN rather thatn ss$_linkdiscon and EPIPE :-(&lt;BR /&gt;&lt;BR /&gt;Of course this only happens when using the io$m_nowait modifier to the io$_readvblk so how much trouble could it cause. . .Arrrrrgh&lt;BR /&gt;&lt;BR /&gt;Regards Richard Maher&lt;BR /&gt;&lt;BR /&gt;PS. If you feel that you may have been affected by the issues raised in this post then please contact you Process Software rep now!</description>
      <pubDate>Fri, 10 Aug 2007 21:46:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ast-notification-of-socket-disconnection-bgdriver-qio-api/m-p/4003214#M55383</guid>
      <dc:creator>Richard J Maher</dc:creator>
      <dc:date>2007-08-10T21:46:12Z</dc:date>
    </item>
  </channel>
</rss>

