---------- Forwarded message ----------
From: Matthew Persico <[EMAIL PROTECTED]>
Date: Mar 2, 2006 10:21 AM
Subject: Re: Can't connect to Sybase Rep server
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>


On 3/2/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Here's the code that checks to see if the remote server understands the
> ct_option call.
>
>     /* Check to see if the server supports the ct_option() call */
>     if(!imp_dbh->optSupported) {
>         CS_BOOL val;
>         CS_RETCODE ret = ct_capability(connection, CS_GET,
>                                        CS_CAP_REQUEST,
>                                        CS_OPTION_GET, (CS_VOID*)&val);
>         if(DBIc_DBISTATE(imp_dbh)->debug >= 3)
>             PerlIO_printf(DBIc_LOGPIO(imp_dbh), "    syb_db_login() ->
> checking for ct_option support (ret = %d, val = %d)\n", ret, val);
>         if(ret != CS_SUCCEED || val == CS_FALSE)
>           imp_dbh->optSupported = 0;
>         else
>           imp_dbh->optSupported = 1;
>         if(DBIc_DBISTATE(imp_dbh)->debug >= 3)
>             PerlIO_printf(DBIc_LOGPIO(imp_dbh), "    syb_db_login() ->
> ct_option is %ssupported\n", imp_dbh->optSupported == 1 ?"":"not ");
>     }
>
> BTW - which version of DBI are you using?
>

DBI = 1.48.  It also turns out that I have two versions of repserver
running 12.1 and 12.5. Too many variables in this equasion!

What I will do this weekend is set up a small program that simply
attempts to connect to a rep server. I will use the following matrix:

DBI/DBD        RepServer        Success?
1.37/1.00        12.1
1.48/1.07        12.1
1.37/1.00        12.5
1.48/1.07        12.5

What setting of DBI trace should I use to get useful diagnostics?

> Michael
>
>
>
>
> Extranet
> [EMAIL PROTECTED] - 01/03/2006 18:57
>
>
> To:     dbi-users
> cc:
> Subject:        Re: Can't connect to Sybase Rep server
>
>
> Edited for brevity
>
> On 3/1/06, Matthew Persico <[EMAIL PROTECTED]> wrote:
> > On 3/1/06, Matthew Persico <[EMAIL PROTECTED]> wrote:
> > > On 2/28/06, Matthew Persico <[EMAIL PROTECTED]> wrote:
> > > > > -------- Message d'origine--------
> > > > > De: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]
> > > > > Date: mar. 28.02.2006 07:54
> > > > > À: [EMAIL PROTECTED]
> > > > > Cc: dbi-users@perl.org
> > > > > Objet: Re: Can't connect to Sybase Rep server
> > > > >
> > > > >
> > > > >
> > > > > This is a known problem, and has been fixed in either 1.07 or
> > > > > 1.07_01.
> > > >
> > > > Must be 1.07_01 'cause I am running 1.07. I will download and try
> it.
> > > > is the _01 designation ok for production use?
> > >
> > > Better yet, can anyone point me to where 1.07_01 lives? It's not on
> CPAN.
> >
> > Never mind:
> >
> > http://www.peppler.org/downloads/
> >
>
> I did a diff on 1.07 vs 1.07_01 and I didn't notice any differences
> that would indicate this problem being solved.
>
> I also diffed 1.00 vs 1.07_01 and didn't notice any differences that
> would indicate this problem being solved.
>
> What should I be looking for?
>
>
> This message and any attachments (the "message") is
> intended solely for the addressees and is confidential.
> If you receive this message in error, please delete it and
> immediately notify the sender. Any use not in accord with
> its purpose, any dissemination or disclosure, either whole
> or partial, is prohibited except formal approval. The internet
> can not guarantee the integrity of this message.
> BNP PARIBAS (and its subsidiaries) shall (will) not
> therefore be liable for the message if modified.
>
>                 ---------------------------------------------
>
> Ce message et toutes les pieces jointes (ci-apres le
> "message") sont etablis a l'intention exclusive de ses
> destinataires et sont confidentiels. Si vous recevez ce
> message par erreur, merci de le detruire et d'en avertir
> immediatement l'expediteur. Toute utilisation de ce
> message non conforme a sa destination, toute diffusion
> ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse. L'internet ne permettant pas
> d'assurer l'integrite de ce message, BNP PARIBAS (et ses
> filiales) decline(nt) toute responsabilite au titre de ce
> message, dans l'hypothese ou il aurait ete modifie.
>
>


--
Matthew O. Persico


--
Matthew O. Persico

Reply via email to