<?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: RDB/JDBC native driver in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904136#M21067</link>
    <description>Thanks</description>
    <pubDate>Mon, 16 Jan 2006 02:59:15 GMT</pubDate>
    <dc:creator>ptrskg</dc:creator>
    <dc:date>2006-01-16T02:59:15Z</dc:date>
    <item>
      <title>RDB/JDBC native driver</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904133#M21064</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have for some time now used the the RDB/JDBC thin driver(pool) to access RDB db's on VMS. Now I plan to move some java app's to the VMS server and then start to use the native driver to avoid IP overhead.&lt;BR /&gt;But I'm afraid that this will give me trouble, I suspect that the db-accesses will be "syncronized" as RDB only allows one connection to a DB from a process?. The java process have many threads accessing the DB. Have anyone experience in this area?&lt;BR /&gt;&lt;BR /&gt;Greateful for any advice/tips.&lt;BR /&gt;Peter&lt;BR /&gt;</description>
      <pubDate>Thu, 26 May 2005 12:34:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904133#M21064</guid>
      <dc:creator>ptrskg</dc:creator>
      <dc:date>2005-05-26T12:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: RDB/JDBC native driver</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904134#M21065</link>
      <description>Rdb is not  multithreaded so a  process with several  threads can not&lt;BR /&gt;execute Rdb requets in // in several threads.&lt;BR /&gt;&lt;BR /&gt;you should test, send a huge  request and then in // a small one, you will see if the small is waiting&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 26 May 2005 13:00:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904134#M21065</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-05-26T13:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: RDB/JDBC native driver</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904135#M21066</link>
      <description>You could try to see on jcc (the Rdb mailing list) if this is known (&lt;A href="http://jcc.com/listserver.htm)" target="_blank"&gt;http://jcc.com/listserver.htm)&lt;/A&gt; or search in their database &lt;A href="http://jcc.com/searchengine.asp" target="_blank"&gt;http://jcc.com/searchengine.asp&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
      <pubDate>Fri, 27 May 2005 01:08:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904135#M21066</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-05-27T01:08:25Z</dc:date>
    </item>
    <item>
      <title>Re: RDB/JDBC native driver</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904136#M21067</link>
      <description>Thanks</description>
      <pubDate>Mon, 16 Jan 2006 02:59:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rdb-jdbc-native-driver/m-p/4904136#M21067</guid>
      <dc:creator>ptrskg</dc:creator>
      <dc:date>2006-01-16T02:59:15Z</dc:date>
    </item>
  </channel>
</rss>

