Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Connection Cache and DBPARM

4 posts in General Discussion (old) Last posting was on 2000-03-07 19:50:07.0Z
Tim Nesham Posted on 2000-03-07 15:53:39.0Z
Newsgroups: sybase.public.easerver
From: "Tim Nesham" <tim.nesham@born.com>
Subject: Connection Cache and DBPARM
Date: Tue, 7 Mar 2000 09:53:39 -0600
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Original-NNTP-Posting-Host: 161.49.6.89
Organization: Quad/Graphics,Inc.
NNTP-Posting-Host: dns2.qgraph.com 206.158.124.2
Message-ID: <347_38c52607@news.qgraph.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com!news.qgraph.com!161.49.6.89
Xref: forums-1-dub sybase.public.easerver:26983
Article PK: 157929

Powerbuiler has a transaction object that allows the connection to take on
certain options using the dbparm property. But the connection cache does
not allow us to define the dbparm. So my question is, if I want to have my
connection cache use the other DBMS options available, is this done through
the transaction object in the normal way?

Are there not X amount of connection caches created as soon as they are
defined? This implies those immediately active CCs have not had a dbparm
option affect the cache. So when I pull the cache out of the pool using

itr_trans.dbms = as_dbms
itr_trans.DBParm = "UseContextObject='Yes',CacheName='" + as_cache_nm + "'"
CONNECT USING itr_trans;

is the cached connection affected by the dbparm options such as password
encryption or is the pooled connection used "as is"?

TIA,

Tim


Jim O'Neil [Sybase] Posted on 2000-03-07 18:57:41.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 07 Mar 2000 13:57:41 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Connection Cache and DBPARM
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 50
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38C55125.CCD79038@sybase.com>
References: <347_38c52607@news.qgraph.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26966
Article PK: 157913


Tim Nesham wrote:

> Powerbuiler has a transaction object that allows the connection to take on
> certain options using the dbparm property. But the connection cache does
> not allow us to define the dbparm. So my question is, if I want to have my
> connection cache use the other DBMS options available, is this done through
> the transaction object in the normal way?
>
> Are there not X amount of connection caches created as soon as they are
> defined? This implies those immediately active CCs have not had a dbparm
> option affect the cache. So when I pull the cache out of the pool using
>
> itr_trans.dbms = as_dbms
> itr_trans.DBParm = "UseContextObject='Yes',CacheName='" + as_cache_nm + "'"
> CONNECT USING itr_trans;
>
> is the cached connection affected by the dbparm options such as password
> encryption or is the pooled connection used "as is"?
>
> TIA,
>
> Tim

I haven't had a chance to investigate this fully, but I'll give you my opinion
on this. I do know that when PowerBuilder issues a CONNECT in Jaguar it passes
off the actual connection work to Jaguar; therefore, any of the DBParms that
would actually take effect when the connection is made would probably not take
effect. Some of the DBParms, however, are settings that would take affect
AFTER the connection is made, by PowerBuilder sending specific directives via
the specific established connection - those settings would still work as you
are used to them working in a 2-tier environment. Without a better
understanding of how a specific DBParm is actually implemented though (i.e., is
it an option that has to be set before the connection is made or is it an
option that makes a setting after the connection is made) it would be difficult
to determine what the behavior should be.

Is there a specific circumstance, as in one specific DBParm, that you are
trying to figure out?
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Tim Nesham Posted on 2000-03-07 19:45:30.0Z
Newsgroups: sybase.public.easerver
From: "Tim Nesham" <tim.nesham@born.com>
Subject: Re: Connection Cache and DBPARM
Date: Tue, 7 Mar 2000 13:45:30 -0600
Lines: 80
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Original-NNTP-Posting-Host: 161.49.6.89
Organization: Quad/Graphics,Inc.
NNTP-Posting-Host: dns2.qgraph.com 206.158.124.2
Message-ID: <347_38c55c5d@news.qgraph.com>
References: <347_38c52607@news.qgraph.com> <347_38C55125.CCD79038@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com!news.qgraph.com!161.49.6.89
Xref: forums-1-dub sybase.public.easerver:26961
Article PK: 157909

The two we are most interested in are:
PWEncrypt = "Yes"
Sec_Confidential = 1

Both are usable by the SYJ driver according to documentation.
The second one requires a bit more effort to use it. See PB documentation:
"DBParm parameters and supported database interfaces"

Using a Jaguar connection cache, the questions are:
1. Do these parameters affect the connection?
2. If they do, when? For all connections regardless of when started or only
those that weren't in the pool but had to be created at the same time
requested by CONNECT USING TransObject?

TIA,

Tim

"Jim O'Neil [Sybase]" <joneil@sybase.com> wrote in message
news:38C55125.CCD79038@sybase.com...
> Tim Nesham wrote:
>
> > Powerbuiler has a transaction object that allows the connection to take
on
> > certain options using the dbparm property. But the connection cache
does
> > not allow us to define the dbparm. So my question is, if I want to have
my
> > connection cache use the other DBMS options available, is this done
through
> > the transaction object in the normal way?
> >
> > Are there not X amount of connection caches created as soon as they are
> > defined? This implies those immediately active CCs have not had a dbparm
> > option affect the cache. So when I pull the cache out of the pool using
> >
> > itr_trans.dbms = as_dbms
> > itr_trans.DBParm = "UseContextObject='Yes',CacheName='" + as_cache_nm +
"'"
> > CONNECT USING itr_trans;
> >
> > is the cached connection affected by the dbparm options such as password
> > encryption or is the pooled connection used "as is"?
> >
> > TIA,
> >
> > Tim
>
> I haven't had a chance to investigate this fully, but I'll give you my
opinion
> on this. I do know that when PowerBuilder issues a CONNECT in Jaguar it
passes
> off the actual connection work to Jaguar; therefore, any of the DBParms
that
> would actually take effect when the connection is made would probably not
take
> effect. Some of the DBParms, however, are settings that would take affect
> AFTER the connection is made, by PowerBuilder sending specific directives
via
> the specific established connection - those settings would still work as
you
> are used to them working in a 2-tier environment. Without a better
> understanding of how a specific DBParm is actually implemented though
(i.e., is
> it an option that has to be set before the connection is made or is it an
> option that makes a setting after the connection is made) it would be
difficult
> to determine what the behavior should be.
>
> Is there a specific circumstance, as in one specific DBParm, that you are
> trying to figure out?
> --
> Jim O'Neil
> Senior Technical Support Engineer
> Sybase, Inc
>
>


Jim O'Neil [Sybase] Posted on 2000-03-07 19:50:07.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 07 Mar 2000 14:50:07 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Connection Cache and DBPARM
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 79
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38C55D6F.C2882849@sybase.com>
References: <347_38c52607@news.qgraph.com> <347_38C55125.CCD79038@sybase.com> <347_38c55c5d@news.qgraph.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26960
Article PK: 157908


Tim Nesham wrote:

> The two we are most interested in are:
> PWEncrypt = "Yes"
> Sec_Confidential = 1
>
> Both are usable by the SYJ driver according to documentation.
> The second one requires a bit more effort to use it. See PB documentation:
> "DBParm parameters and supported database interfaces"
>
> Using a Jaguar connection cache, the questions are:
> 1. Do these parameters affect the connection?
> 2. If they do, when? For all connections regardless of when started or only
> those that weren't in the pool but had to be created at the same time
> requested by CONNECT USING TransObject?
>
> TIA,
>
> Tim
>
> "Jim O'Neil [Sybase]" <joneil@sybase.com> wrote in message
> news:38C55125.CCD79038@sybase.com...
> > Tim Nesham wrote:
> >
> > > Powerbuiler has a transaction object that allows the connection to take
> on
> > > certain options using the dbparm property. But the connection cache
> does
> > > not allow us to define the dbparm. So my question is, if I want to have
> my
> > > connection cache use the other DBMS options available, is this done
> through
> > > the transaction object in the normal way?
> > >
> > > Are there not X amount of connection caches created as soon as they are
> > > defined? This implies those immediately active CCs have not had a dbparm
> > > option affect the cache. So when I pull the cache out of the pool using
> > >
> > > itr_trans.dbms = as_dbms
> > > itr_trans.DBParm = "UseContextObject='Yes',CacheName='" + as_cache_nm +
> "'"
> > > CONNECT USING itr_trans;
> > >
> > > is the cached connection affected by the dbparm options such as password
> > > encryption or is the pooled connection used "as is"?
> > >
> > > TIA,
> > >
> > > Tim
> >
> > I haven't had a chance to investigate this fully, but I'll give you my
> opinion
> > on this. I do know that when PowerBuilder issues a CONNECT in Jaguar it
> passes
> > off the actual connection work to Jaguar; therefore, any of the DBParms
> that
> > would actually take effect when the connection is made would probably not
> take
> > effect. Some of the DBParms, however, are settings that would take affect
> > AFTER the connection is made, by PowerBuilder sending specific directives
> via
> > the specific established connection - those settings would still work as
> you
> > are used to them working in a 2-tier environment. Without a better
> > understanding of how a specific DBParm is actually implemented though
> (i.e., is
> > it an option that has to be set before the connection is made or is it an
> > option that makes a setting after the connection is made) it would be
> difficult
> > to determine what the behavior should be.
> >
> > Is there a specific circumstance, as in one specific DBParm, that you are
> > trying to figure out?
> > --
> > Jim O'Neil
> > Senior Technical Support Engineer
> > Sybase, Inc
> >
> >

Let me look into this - I don't think I'll be able to give you an answer without
consulting development on this one, so it may take a day or two.
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc