HP3000-L Archives

March 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Peter Osborne <[log in to unmask]>
Reply To:
Peter Osborne <[log in to unmask]>
Date:
Wed, 27 Mar 2002 16:47:20 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (50 lines)
I can dig up the code & send it to you if you're interested. The stuff I wrote
was in C though. Should work with Cobol. I think we may have even had it
working with Cobol briefly. Can't remember for sure though.

-Pete
On March 27, 2002 04:39 pm, Jeff Woods wrote:
> Hi, folks.
>
> On 2 Nov 2001, Pete Osborne <[log in to unmask]> wrote in a longer post:
> >Pretty Cool stuff, I just installed the latest GCC & compiled my two
> >programs. The first program uses only libpq, it connects to the PostgreSQL
> >server that I have running on a Linux Server and lists all the databases.
> >Works like a charm :-).
>
> We're trying to use Postgresql from MPE (courtesy of Mark Bixby's port of
> 7.1.2) from a COBOL/iX program and C/iX (CCXL) library we've written linked
> with libpq.a to access a Postgres database on a Linux system.  FWIW, we can
> use psql utility on MPE to access the postgres database on the Linux
> machine without any problems.
>
> We're getting the following error:
>
> Fatal DB Open Error :
>  connectMakeNonblocking -- fcntl() failed: errno=9
> Bad file number
>
> I have the impression that fcntl() isn't supported with sockets on MPE and
> that these calls should be sfcntl() instead.  Is that correct?  If so, I
> don't see how Pete's test above worked.  [The next thing I'm going to try
> is changing that fcntl() to sfcntl() and rebuilding libpq.a on MPE to see
> if that helps.]
>
> We've tried configuring for blocking and non-blocking calls, but get errors
> both ways.  [I suspect that connectMakeNonblocking() is getting called in
> either mode.]  Anyone have any idea why libpq seemed to work for Pete but
> doesn't work for us?  (Was that the same 7.1.2 release of Postgres?)
>
> Perhaps related note:
> Searching the web for this topic we found:
> http://archives.postgresql.org/pgsql-patches/2000-06/msg00003.php
> which shows a patch that was incorporated into Postgres source, but was
> backed out (perhaps inadvertantly) before the 7.1.2 release.
>
> Any suggestions or other help in this regard would be much appreciated.
>
> Thanks!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2