<?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 TCPWARE select() replacement. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267057#M56838</link>
    <description>Versions of products.&lt;BR /&gt;DEC AXPVMS TCPIP V5.4-15&lt;BR /&gt;Compaq C V6.4-008 on OpenVMS Alpha V7.3-2&lt;BR /&gt;&lt;BR /&gt;I am trying to use select() in my C program&lt;BR /&gt;with a socket operation on non-socket.&lt;BR /&gt;I have read on the Internet talking about&lt;BR /&gt; just this problem. Was looking to see if a replacement option was available or code snipit would provide a workaround for this limitation.&lt;BR /&gt;&lt;BR /&gt;Would like to keep the code able to work on UNIX/OpenVMS. But wanted to see if other options where availble instead of a separate section of code just for OpenVMS. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 10 Sep 2008 21:34:43 GMT</pubDate>
    <dc:creator>factor</dc:creator>
    <dc:date>2008-09-10T21:34:43Z</dc:date>
    <item>
      <title>TCPWARE select() replacement.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267057#M56838</link>
      <description>Versions of products.&lt;BR /&gt;DEC AXPVMS TCPIP V5.4-15&lt;BR /&gt;Compaq C V6.4-008 on OpenVMS Alpha V7.3-2&lt;BR /&gt;&lt;BR /&gt;I am trying to use select() in my C program&lt;BR /&gt;with a socket operation on non-socket.&lt;BR /&gt;I have read on the Internet talking about&lt;BR /&gt; just this problem. Was looking to see if a replacement option was available or code snipit would provide a workaround for this limitation.&lt;BR /&gt;&lt;BR /&gt;Would like to keep the code able to work on UNIX/OpenVMS. But wanted to see if other options where availble instead of a separate section of code just for OpenVMS. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Sep 2008 21:34:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267057#M56838</guid>
      <dc:creator>factor</dc:creator>
      <dc:date>2008-09-10T21:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: TCPWARE select() replacement.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267058#M56839</link>
      <description>AFAIK, OpenVMS (still) doesn't implement select() on non-network I/O sockets.  AFAIK, this isn't specifically TCPware or any other IP stack; it's a generic limit in the C run-time.&lt;BR /&gt;&lt;BR /&gt;The usual approach here tends to involve threads, if you need/want portable C code.  The select call itself isn't fully portable.&lt;BR /&gt;&lt;BR /&gt;OpenVMS-native code often uses ASTs.&lt;BR /&gt;&lt;BR /&gt;Or you conditionalize the I/O to the platform.</description>
      <pubDate>Wed, 10 Sep 2008 22:57:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267058#M56839</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-09-10T22:57:20Z</dc:date>
    </item>
    <item>
      <title>Re: TCPWARE select() replacement.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267059#M56840</link>
      <description>Thanks Hoff, wanted to make sure before I got most of the way thru it, then found another way. I will make an ifdef VMS section with&lt;BR /&gt; the native AST stuff.</description>
      <pubDate>Wed, 10 Sep 2008 23:13:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267059#M56840</guid>
      <dc:creator>factor</dc:creator>
      <dc:date>2008-09-10T23:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: TCPWARE select() replacement.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267060#M56841</link>
      <description>Neither TCPware nor MultiNet's select operation works on non-socket channels.&lt;BR /&gt;&lt;BR /&gt;Depending upon what the non-socket channel is it may be possible to write a vms_select function that looks at the type of device behind the channel and does the appropriate sensing.  Mailboxes have attention ASTs that are very similar to network attention ASTs.  Terminals are harder, but can be done with an associated mailbox.  I'm not sure how I would do it with a file though.</description>
      <pubDate>Thu, 11 Sep 2008 00:11:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267060#M56841</guid>
      <dc:creator>Richard Whalen</dc:creator>
      <dc:date>2008-09-11T00:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: TCPWARE select() replacement.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267061#M56842</link>
      <description>Oh nifty, I will look into that, the non socket would be stdio stdout and stderr. &lt;BR /&gt;&lt;BR /&gt;Yes, I was wanting to make a vms_select()&lt;BR /&gt;Would be nice if a code snippit of it was&lt;BR /&gt;hanging around some where on the internet.&lt;BR /&gt;&lt;BR /&gt;Thanks for the pointers. See what I can come up with.</description>
      <pubDate>Thu, 11 Sep 2008 02:42:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpware-select-replacement/m-p/4267061#M56842</guid>
      <dc:creator>factor</dc:creator>
      <dc:date>2008-09-11T02:42:11Z</dc:date>
    </item>
  </channel>
</rss>

