Powerbuilder Debugger Creates Multiple Sessions in Sybase ASE

[sallylloyd]

Is there a way to prevent creation of multiple ASE sessions
when using the Powerbuilder debugger? If I stop the
debugger and then resume without closing Powerbuilder, it
creates new connections to the Sybase databases. I'm
concerned these are being counted as part of our total ASE
license usage. Thanks, Sally

[Chris Pollach]

Hi Sally;

First of all .. ASE allows (but doe not immediately allocate) 4
connections for every user license (way better than the competition eh
<bg>). This was an original design aspect of SQLServer by Sybase (before it
was renamed to ASE). The idea was that other threads could be opened up to
handle things like multiple result sets, special locking requests, fetching
asynchronously, etc.

If you are getting more than one connection in the debugger vs normal
application execution, I would be really surprised. Unless you are issuing
multiple Connect SQL statements with various Transaction Objects or used the
SetTrans ( ) method with DataWindow or DataStores vs SetTransObject ( )
command.
So what you are seeing in the debugger is probably happening in the normal
execution of the application. Its just that the ASE client may be opening up
other threads as required but then closing them right afterwards. This is
normal.

The total number of allowed threads in ASE is actually #user licenses x
4. So unless you are getting close to that number in concurrent
connections - you have nothing to worry about.

BTW: Since Sybase took over SQLAnywhere - the SQLAnywhere DB engine (SA)
also works on the same memory model.

--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com

<Sally Lloyd> wrote in message news:4ac22546.6b6...@sybase.com...

[sallylloyd]

Chris, I'd still like to find a way to easily cancel the
multiple PB sessions I get while using the debugger.
Here's more info:
When I debug my code the first time, I have one connection
to ASE. If I stop the debugger before the transaction is
closed,
that connection remains active until I completely close PB.
If I don't close PB, each time I run the debugger, it adds
another connection until I have so many (10 or so), PB
crashes.

I was hoping that when I close the debugger it whould kill
those connections, but it doesn't - I have to close PB.

Thanks for the info about threads & usage count.
Sally

[Chris Pollach]

Hi Sally;

Have you tried ...

1) Setting your application object's "FreeDBLibraries" property to TRUE?
2) Setting your IDE's general System options "Free Database Driver Libraries
on Disconnect" to TRUE?

BTW: What versions of PB and ASE are you using?

--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com

<Sally Lloyd> wrote in message news:4acb5099.5e...@sybase.com...