headers
Jonathan Foy | 6 Apr 16:14
Picon

connecting through Cobol via odbc

Hello

I am trying to get pgbouncer to work in my environment, and have run into a snag. 

I have it up and running and it appears to be working fine for straight psql commands, either from the local server or from others on the network.  I can connect without issue.

However, if I try to connect through our cobol app, via the entries in odbc.ini, I keep getting the following error:

2010-04-05 16:48:56.658 22760 NOISE get_header: unknown special pkt: len=296 code=131072
2010-04-05 16:48:56.658 22760 LOG C-0x944d708: (nodb)/(nouser) <at> 172.22.1.34:39865 closing because: bad packet header (age=0)
2010-04-05 16:48:56.658 22760 WARNING C-0x944d708: (nodb)/(nouser) <at> 172.22.1.34:39865 Pooler Error: bad packet header

I know that it's failing because of the packet code (131072, or 0x20000)...the normal requests all have 80877103 (and the packet lengths are 8 bytes vs the 296 here), which maps to the PKT_SSLREQ type from my perusal of the code.  But I'm not quite sure where to go from here.  I'm suspecting an odbc config setting may be missing...has anyone seen this before? 

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Marko Kreen | 6 Apr 17:36
Picon

Re: connecting through Cobol via odbc

On 4/6/10, Jonathan Foy <thefoy@...> wrote:
> Hello
>
> I am trying to get pgbouncer to work in my environment, and have run into a
> snag.
>
> I have it up and running and it appears to be working fine for straight psql
> commands, either from the local server or from others on the network.  I can
> connect without issue.
>
> However, if I try to connect through our cobol app, via the entries in
> odbc.ini, I keep getting the following error:
>
> 2010-04-05 16:48:56.658 22760 NOISE get_header: unknown special pkt: len=296
> code=131072
>  2010-04-05 16:48:56.658 22760 LOG C-0x944d708:
> (nodb)/(nouser)@172.22.1.34:39865 closing because: bad
> packet header (age=0)
>  2010-04-05 16:48:56.658 22760 WARNING C-0x944d708:
> (nodb)/(nouser)@172.22.1.34:39865 Pooler Error: bad packet
> header
>
> I know that it's failing because of the packet code (131072, or
> 0x20000)...the normal requests all have 80877103 (and the packet lengths are
> 8 bytes vs the 296 here), which maps to the PKT_SSLREQ type from my perusal
> of the code.  But I'm not quite sure where to go from here.  I'm suspecting
> an odbc config setting may be missing...has anyone seen this before?

It seems to request V2 protocol, which is not supported by pgbouncer.

Perhaps you should upgrade your odbc driver?

Such case may be worth better error message...

--

-- 
marko
Permalink | Reply |
headers
Jonathan Foy | 6 Apr 18:05
Picon

Re: connecting through Cobol via odbc

That's my current course of action...the existing driver is quite old. I tried it briefly with a newer version (8.04.0200), but in a setup where I don't have full access and am not free to test as I would like...the odbc.ini entry was not setup properly either I don't believe.

It may take a day or two to get things setup properly unfortunately...this is a side-project of mine that is not considered top-priority.

Sorry for the double-reply Marko, forgot to reply to the list.

On Tue, Apr 6, 2010 at 11:36 AM, Marko Kreen <markokr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 4/6/10, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello
>
> I am trying to get pgbouncer to work in my environment, and have run into a
> snag.
>
> I have it up and running and it appears to be working fine for straight psql
> commands, either from the local server or from others on the network.  I can
> connect without issue.
>
> However, if I try to connect through our cobol app, via the entries in
> odbc.ini, I keep getting the following error:
>
> 2010-04-05 16:48:56.658 22760 NOISE get_header: unknown special pkt: len=296
> code=131072
>  2010-04-05 16:48:56.658 22760 LOG C-0x944d708:
> (nodb)/(nouser) <at> 172.22.1.34:39865 closing because: bad
> packet header (age=0)
>  2010-04-05 16:48:56.658 22760 WARNING C-0x944d708:
> (nodb)/(nouser) <at> 172.22.1.34:39865 Pooler Error: bad packet
> header
>
> I know that it's failing because of the packet code (131072, or
> 0x20000)...the normal requests all have 80877103 (and the packet lengths are
> 8 bytes vs the 296 here), which maps to the PKT_SSLREQ type from my perusal
> of the code.  But I'm not quite sure where to go from here.  I'm suspecting
> an odbc config setting may be missing...has anyone seen this before?

It seems to request V2 protocol, which is not supported by pgbouncer.

Perhaps you should upgrade your odbc driver?

Such case may be worth better error message...

--
marko

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Jonathan Foy | 8 Apr 22:27
Picon

Re: connecting through Cobol via odbc

Do you know if anyone uses pgbouncer with the psqlODBC driver from their site?  I have compiled the latest version, and I'm still getting the same error.  No matter how I set it up, configure the odbc.ini file, etc, I still end up sending that 0x20000 version number.  In testing the connection with isql, a unixodbc program, there's even a flag to explicitly set V3 method calls.  Does not seem to work...

I HAVE gotten quite an education on odbc though...still incomplete it would seem.

On Tue, Apr 6, 2010 at 11:36 AM, Marko Kreen <markokr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 4/6/10, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello
>
> I am trying to get pgbouncer to work in my environment, and have run into a
> snag.
>
> I have it up and running and it appears to be working fine for straight psql
> commands, either from the local server or from others on the network.  I can
> connect without issue.
>
> However, if I try to connect through our cobol app, via the entries in
> odbc.ini, I keep getting the following error:
>
> 2010-04-05 16:48:56.658 22760 NOISE get_header: unknown special pkt: len=296
> code=131072
>  2010-04-05 16:48:56.658 22760 LOG C-0x944d708:
> (nodb)/(nouser) <at> 172.22.1.34:39865 closing because: bad
> packet header (age=0)
>  2010-04-05 16:48:56.658 22760 WARNING C-0x944d708:
> (nodb)/(nouser) <at> 172.22.1.34:39865 Pooler Error: bad packet
> header
>
> I know that it's failing because of the packet code (131072, or
> 0x20000)...the normal requests all have 80877103 (and the packet lengths are
> 8 bytes vs the 296 here), which maps to the PKT_SSLREQ type from my perusal
> of the code.  But I'm not quite sure where to go from here.  I'm suspecting
> an odbc config setting may be missing...has anyone seen this before?

It seems to request V2 protocol, which is not supported by pgbouncer.

Perhaps you should upgrade your odbc driver?

Such case may be worth better error message...

--
marko

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Merlin Moncure | 8 Apr 22:31
Picon

Re: connecting through Cobol via odbc

On Thu, Apr 8, 2010 at 4:27 PM, Jonathan Foy <thefoy@...> wrote:
> Do you know if anyone uses pgbouncer with the psqlODBC driver from their
> site?  I have compiled the latest version, and I'm still getting the same
> error.  No matter how I set it up, configure the odbc.ini file, etc, I still
> end up sending that 0x20000 version number.  In testing the connection with
> isql, a unixodbc program, there's even a flag to explicitly set V3 method
> calls.  Does not seem to work...
>
> I HAVE gotten quite an education on odbc though...still incomplete it would
> seem.

sure you are using the right odbc driver? on linux, you can ldd the
executable to get the list of .so dependencies...

merlin
Permalink | Reply |
headers
Jonathan Foy | 8 Apr 22:51
Picon

Re: connecting through Cobol via odbc



On Thu, Apr 8, 2010 at 4:31 PM, Merlin Moncure <mmoncure <at> gmail.com> wrote:
On Thu, Apr 8, 2010 at 4:27 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Do you know if anyone uses pgbouncer with the psqlODBC driver from their
> site?  I have compiled the latest version, and I'm still getting the same
> error.  No matter how I set it up, configure the odbc.ini file, etc, I still
> end up sending that 0x20000 version number.  In testing the connection with
> isql, a unixodbc program, there's even a flag to explicitly set V3 method
> calls.  Does not seem to work...
>
> I HAVE gotten quite an education on odbc though...still incomplete it would
> seem.

sure you are using the right odbc driver? on linux, you can ldd the
executable to get the list of .so dependencies...


merlin

The isql program indeed does not list the libodbcpsql.so file, but then that library is supposed to be linked in based upon what dsn I'm trying to connect to.  The runcbl program (and I've been paying no heed to it while trying to simply get the connection working through the odbc) indeed lists the appropriate library.
_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Merlin Moncure | 8 Apr 22:55
Picon

Re: connecting through Cobol via odbc

On Thu, Apr 8, 2010 at 4:51 PM, Jonathan Foy <thefoy@...> wrote:
> On Thu, Apr 8, 2010 at 4:31 PM, Merlin Moncure <mmoncure@...> wrote:
>>
>> On Thu, Apr 8, 2010 at 4:27 PM, Jonathan Foy <thefoy@...> wrote:
>> > Do you know if anyone uses pgbouncer with the psqlODBC driver from their
>> > site?  I have compiled the latest version, and I'm still getting the
>> > same
>> > error.  No matter how I set it up, configure the odbc.ini file, etc, I
>> > still
>> > end up sending that 0x20000 version number.  In testing the connection
>> > with
>> > isql, a unixodbc program, there's even a flag to explicitly set V3
>> > method
>> > calls.  Does not seem to work...
>> >
>> > I HAVE gotten quite an education on odbc though...still incomplete it
>> > would
>> > seem.
>
> The isql program indeed does not list the libodbcpsql.so file, but then that
> library is supposed to be linked in based upon what dsn I'm trying to
> connect to.  The runcbl program (and I've been paying no heed to it while
> trying to simply get the connection working through the odbc) indeed lists
> the appropriate library.

if I were you, I would be figuring out under which circumstances the
pg odbc driver decides or is forced to use v2 protocol, and disable
those conditions or possibly hack the driver to force v3 protocol.
you also might want to query odbc lists (haven't used odbc in years
myself)...

merlin
Permalink | Reply |
headers
Jonathan Foy | 8 Apr 23:00
Picon

Re: connecting through Cobol via odbc



On Thu, Apr 8, 2010 at 4:55 PM, Merlin Moncure <mmoncure <at> gmail.com> wrote:
On Thu, Apr 8, 2010 at 4:51 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Thu, Apr 8, 2010 at 4:31 PM, Merlin Moncure <mmoncure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> On Thu, Apr 8, 2010 at 4:27 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > Do you know if anyone uses pgbouncer with the psqlODBC driver from their
>> > site?  I have compiled the latest version, and I'm still getting the
>> > same
>> > error.  No matter how I set it up, configure the odbc.ini file, etc, I
>> > still
>> > end up sending that 0x20000 version number.  In testing the connection
>> > with
>> > isql, a unixodbc program, there's even a flag to explicitly set V3
>> > method
>> > calls.  Does not seem to work...
>> >
>> > I HAVE gotten quite an education on odbc though...still incomplete it
>> > would
>> > seem.
>
> The isql program indeed does not list the libodbcpsql.so file, but then that
> library is supposed to be linked in based upon what dsn I'm trying to
> connect to.  The runcbl program (and I've been paying no heed to it while
> trying to simply get the connection working through the odbc) indeed lists
> the appropriate library.

if I were you, I would be figuring out under which circumstances the
pg odbc driver decides or is forced to use v2 protocol, and disable
those conditions or possibly hack the driver to force v3 protocol.
you also might want to query odbc lists (haven't used odbc in years
myself)...

merlin

I've been on the postgres odbc boards a bit, threw it back here to check if I was trying to do something unusual.  Doesn't seem like it, but thought I'd check.  Thanks for the advice...I always seem to start with nothing, jump too far ahead, and then go back to the basics and step my way through.  You'd think I'd learn...
_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Jonathan Foy | 14 Apr 14:32
Picon

Re: connecting through Cobol via odbc

For what it's worth, I WAS using the wrong driver.  I was led astray by he-who-compiled.  Once I took over everything and compiled for myself I realized that the compiled library, psqlodbcw.so, was clearly NOT the one I had been using, libodbcpsql.so.  I was further confused by a terrible mis-mash of unixODBC libraries from different versions installed in different directories.  The ldd command was vital in tracking down who was using what.

In case anyone else comes across my idiocy, to save them any hassle...

libodbcpsql.so seems to be the old stripped postgres driver/library that is included with unixODBC.
psqlodbcw.so is the driver/library compiled from recent psqlODBC downloads from postgresql.org.
libodbc.so is the unixODBC driver.

When the cobol runtime was compiled with libodbc.so, I registered the Postgres driver in odbcinst.ini (referencing psqlodbcw.so), and setup the dsns in odbc.ini, using the Postgres driver reference...and removed all references to the previous unixODBC version's libraries...everything worked as it should. v3 protocol is being used.

Amazing how that goes.

So, it's working now, more or less.  Still toying with the configuration, and need to figure out exactly how the cobol is calling the functions, but progress is being made. Thanks for all the help, and sorry for wasting time with nonsensical questions.

On Thu, Apr 8, 2010 at 5:00 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:


On Thu, Apr 8, 2010 at 4:55 PM, Merlin Moncure <mmoncure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Thu, Apr 8, 2010 at 4:51 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Thu, Apr 8, 2010 at 4:31 PM, Merlin Moncure <mmoncure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> On Thu, Apr 8, 2010 at 4:27 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > Do you know if anyone uses pgbouncer with the psqlODBC driver from their
>> > site?  I have compiled the latest version, and I'm still getting the
>> > same
>> > error.  No matter how I set it up, configure the odbc.ini file, etc, I
>> > still
>> > end up sending that 0x20000 version number.  In testing the connection
>> > with
>> > isql, a unixodbc program, there's even a flag to explicitly set V3
>> > method
>> > calls.  Does not seem to work...
>> >
>> > I HAVE gotten quite an education on odbc though...still incomplete it
>> > would
>> > seem.
>
> The isql program indeed does not list the libodbcpsql.so file, but then that
> library is supposed to be linked in based upon what dsn I'm trying to
> connect to.  The runcbl program (and I've been paying no heed to it while
> trying to simply get the connection working through the odbc) indeed lists
> the appropriate library.

if I were you, I would be figuring out under which circumstances the
pg odbc driver decides or is forced to use v2 protocol, and disable
those conditions or possibly hack the driver to force v3 protocol.
you also might want to query odbc lists (haven't used odbc in years
myself)...

merlin

I've been on the postgres odbc boards a bit, threw it back here to check if I was trying to do something unusual.  Doesn't seem like it, but thought I'd check.  Thanks for the advice...I always seem to start with nothing, jump too far ahead, and then go back to the basics and step my way through.  You'd think I'd learn...

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Merlin Moncure | 14 Apr 15:06
Picon

Re: connecting through Cobol via odbc

On Wed, Apr 14, 2010 at 8:32 AM, Jonathan Foy <thefoy@...> wrote:
> For what it's worth, I WAS using the wrong driver.  I was led astray by
> he-who-compiled.  Once I took over everything and compiled for myself I
> realized that the compiled library, psqlodbcw.so, was clearly NOT the one I
> had been using, libodbcpsql.so.  I was further confused by a terrible
> mis-mash of unixODBC libraries from different versions installed in
> different directories.  The ldd command was vital in tracking down who was
> using what.
>
> In case anyone else comes across my idiocy, to save them any hassle...
>
> libodbcpsql.so seems to be the old stripped postgres driver/library that is
> included with unixODBC.
> psqlodbcw.so is the driver/library compiled from recent psqlODBC downloads
> from postgresql.org.
> libodbc.so is the unixODBC driver.
>
> When the cobol runtime was compiled with libodbc.so, I registered the
> Postgres driver in odbcinst.ini (referencing psqlodbcw.so), and setup the
> dsns in odbc.ini, using the Postgres driver reference...and removed all
> references to the previous unixODBC version's libraries...everything worked
> as it should. v3 protocol is being used.
>
> Amazing how that goes.
>
> So, it's working now, more or less.  Still toying with the configuration,
> and need to figure out exactly how the cobol is calling the functions, but
> progress is being made. Thanks for all the help, and sorry for wasting time
> with nonsensical questions.
>

glad to be of help!

merlin

p.s. please don't top post! :-)
Permalink | Reply |
headers
Merlin Moncure | 6 Apr 17:45
Picon

Re: connecting through Cobol via odbc

On Tue, Apr 6, 2010 at 10:14 AM, Jonathan Foy <thefoy@...> wrote:
> Hello
>
> I am trying to get pgbouncer to work in my environment, and have run into a
> snag.
>
> I have it up and running and it appears to be working fine for straight psql
> commands, either from the local server or from others on the network.  I can
> connect without issue.

which cobol?

merlin
Permalink | Reply |
headers
Jonathan Foy | 6 Apr 18:06
Picon

Re: connecting through Cobol via odbc

Acucobol.  5.3 (I believe) and 8.1.

On Tue, Apr 6, 2010 at 11:45 AM, Merlin Moncure <mmoncure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Tue, Apr 6, 2010 at 10:14 AM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello
>
> I am trying to get pgbouncer to work in my environment, and have run into a
> snag.
>
> I have it up and running and it appears to be working fine for straight psql
> commands, either from the local server or from others on the network.  I can
> connect without issue.

which cobol?

merlin

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Merlin Moncure | 6 Apr 18:14
Picon

Re: connecting through Cobol via odbc

On Tue, Apr 6, 2010 at 12:06 PM, Jonathan Foy <thefoy@...> wrote:
> Acucobol.  5.3 (I believe) and 8.1.

Cool, I have quite a bit of experience w/acucobol.  At a previous job
I actually was able to implement a native postgresql driver and get a
HUGE cobol erp working with postgres as the data store with very few
code changes.  I had to reverse engineer the runtime to figure out how
to link in a custom file system.  Their ODBC driver is absolutely
terrible.   Performance was excellent -- comparable with acuserver.

Short of that, you are in for a rocky ride.   If it was me I'd bypass
odbc completely and link libpq to your app and run queries that way --
unless you are using 3rd party tool that requires odbc?

merlin
Permalink | Reply |
headers
Jonathan Foy | 7 Apr 17:57
Picon

Re: connecting through Cobol via odbc

I was afraid of this...

I'll go ahead and be upfront in that I currently am NOT very familiar with Acucobol. I'm getting quite comfortable with postgres since picking up most of the DBA duties around here a couple years ago (before that I had no experience with it at all), but haven't had to get into the cobol/odbc side of things yet, and my java does not use the odbc.  Looks like that's changing.

So forgive me if I seem dense.

You mention that their ODBC driver is terrible...does this mean that the cobol is not actually using the psqlODBC that I pulled from the website?  It certainly seems to be ignoring most of the options outside of dbname, port, host, user and pass.


On Tue, Apr 6, 2010 at 12:14 PM, Merlin Moncure <mmoncure <at> gmail.com> wrote:
On Tue, Apr 6, 2010 at 12:06 PM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Acucobol.  5.3 (I believe) and 8.1.

Cool, I have quite a bit of experience w/acucobol.  At a previous job
I actually was able to implement a native postgresql driver and get a
HUGE cobol erp working with postgres as the data store with very few
code changes.  I had to reverse engineer the runtime to figure out how
to link in a custom file system.  Their ODBC driver is absolutely
terrible.   Performance was excellent -- comparable with acuserver.

Short of that, you are in for a rocky ride.   If it was me I'd bypass
odbc completely and link libpq to your app and run queries that way --
unless you are using 3rd party tool that requires odbc?

merlin

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |
headers
Merlin Moncure | 7 Apr 18:04
Picon

Re: connecting through Cobol via odbc

On Wed, Apr 7, 2010 at 11:57 AM, Jonathan Foy <thefoy@...> wrote:
> I was afraid of this...
>
> I'll go ahead and be upfront in that I currently am NOT very familiar with
> Acucobol. I'm getting quite comfortable with postgres since picking up most
> of the DBA duties around here a couple years ago (before that I had no
> experience with it at all), but haven't had to get into the cobol/odbc side
> of things yet, and my java does not use the odbc.  Looks like that's
> changing.
>
> So forgive me if I seem dense.
>
> You mention that their ODBC driver is terrible...does this mean that the
> cobol is not actually using the psqlODBC that I pulled from the website?  It
> certainly seems to be ignoring most of the options outside of dbname, port,
> host, user and pass.

ah, it either is or it isn't.  this was actually possibly a bit of bad
info on my part -- acucobol has an odbc driver for accessing vision
files which is what i was really thinking of when i meant 'terrible'.
if you are browsing postgresql database from cobol code, then it's
probably got to be using the odbc driver (acucobol doesn't speak
native libpq afaik).

what's possibly happening is that you are passing through a generic
odbc wrapper inside acucobol layer that does not understand or pass pg
specific options.

merlin
Permalink | Reply |
headers
Jonathan Foy | 7 Apr 19:31
Picon

Re: connecting through Cobol via odbc

Okay, that makes more sense.  I know that acucobol was compiled with libodbcpsql.so as the odbc library, but it seems to utilize it in the most limited of fashions.  Since serious changes to the program are not really a possibility right now, I guess I need to look into the odbc setup more.  Time to peruse the postgres odbc archives a bit more I think...

Thanks for all of your input.  Learning as I go here.

On Wed, Apr 7, 2010 at 12:04 PM, Merlin Moncure <mmoncure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Wed, Apr 7, 2010 at 11:57 AM, Jonathan Foy <thefoy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I was afraid of this...
>
> I'll go ahead and be upfront in that I currently am NOT very familiar with
> Acucobol. I'm getting quite comfortable with postgres since picking up most
> of the DBA duties around here a couple years ago (before that I had no
> experience with it at all), but haven't had to get into the cobol/odbc side
> of things yet, and my java does not use the odbc.  Looks like that's
> changing.
>
> So forgive me if I seem dense.
>
> You mention that their ODBC driver is terrible...does this mean that the
> cobol is not actually using the psqlODBC that I pulled from the website?  It
> certainly seems to be ignoring most of the options outside of dbname, port,
> host, user and pass.

ah, it either is or it isn't.  this was actually possibly a bit of bad
info on my part -- acucobol has an odbc driver for accessing vision
files which is what i was really thinking of when i meant 'terrible'.
if you are browsing postgresql database from cobol code, then it's
probably got to be using the odbc driver (acucobol doesn't speak
native libpq afaik).

what's possibly happening is that you are passing through a generic
odbc wrapper inside acucobol layer that does not understand or pass pg
specific options.

merlin

_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general@...
http://pgfoundry.org/mailman/listinfo/pgbouncer-general
Permalink | Reply |

Gmane