<?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 TCP socket startup issue in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tcp-socket-startup-issue/m-p/3016827#M46491</link>
    <description>I have a c program that opens and connects a socket to one of our vendors for the purpose of exchanging information. We disconnect the socket after midnight using ndd disconnect by address. The problem we're having is, when we start the process in the morning, the socket status starts in "Established" mode and since their are no files to exchange with the vendor the socket goes into "Time_Wait" status which causes our program to fail and socket to disconnect. My workaround, was to send a single packet at startup across the connection. That causes the socket to stay open. If someone has a solution or suggestion to how I can fix this, please send me your thoughts.</description>
    <pubDate>Mon, 07 Jul 2003 14:21:37 GMT</pubDate>
    <dc:creator>Osa Jousou</dc:creator>
    <dc:date>2003-07-07T14:21:37Z</dc:date>
    <item>
      <title>TCP socket startup issue</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-socket-startup-issue/m-p/3016827#M46491</link>
      <description>I have a c program that opens and connects a socket to one of our vendors for the purpose of exchanging information. We disconnect the socket after midnight using ndd disconnect by address. The problem we're having is, when we start the process in the morning, the socket status starts in "Established" mode and since their are no files to exchange with the vendor the socket goes into "Time_Wait" status which causes our program to fail and socket to disconnect. My workaround, was to send a single packet at startup across the connection. That causes the socket to stay open. If someone has a solution or suggestion to how I can fix this, please send me your thoughts.</description>
      <pubDate>Mon, 07 Jul 2003 14:21:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-socket-startup-issue/m-p/3016827#M46491</guid>
      <dc:creator>Osa Jousou</dc:creator>
      <dc:date>2003-07-07T14:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: TCP socket startup issue</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-socket-startup-issue/m-p/3016828#M46492</link>
      <description>Sorry, posted in the wrong forum. Please disregard.</description>
      <pubDate>Mon, 07 Jul 2003 14:56:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-socket-startup-issue/m-p/3016828#M46492</guid>
      <dc:creator>Osa Jousou</dc:creator>
      <dc:date>2003-07-07T14:56:48Z</dc:date>
    </item>
  </channel>
</rss>

