DB2 Connect Enterprise adtition

Leon Katsnelson

DB2 Connect Enterprise adtition
There are several ways of figuring out this information. Which are
available to you will depend on the version that you have. DB2 Connect V6.1
has the most complete set. In all versions you can issue LIST DCS
APPLICATIONS command using command line processor to display a line for
each database connection coming through a DB2 Connect EE server. It is
important to note that connections originating from DB2 Connect EE box
itself will not be reflected in this display unless you are using V6.1 and
do something special i.e. set DBCONNECT_IN_APP_PROCESS=0.

In V5.2 and later you can also use DB2 Control Center to display pretty
much the same information. In V6.1 you can also use Windows NT Performance
monitor to display active connections and lots of other very useful info.
Both DB2 Control Center and Windows NT performance monitor allow you to do
all monitoring form a remote workstation i.e. you don't have to sit at the
DB2 Connect EE console.

To invoke Windows NT Performance Monitor click on
Start/Programs/Administrative Tools/Performance Monitor. Then click on "+"
button to add DB2 Connect performance counters that you want
graphed/reported. Keep in mind that if no applications are active DB2
Connect counters will not even show up in the list.

As I said before, if you want applications running on the DB2 Connect box
itself to be reported you will need to set DBCONNECT_IN_APP_PROCESS=0.

Leon Katsnelson, DB2 Connect Development Manager
mailto:[login to unmask email]


"Whittaker, Stephen" <[login to unmask email]> on 01/05/2000 09:48:19 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: DB2 Connect Enterprise addtition




Could use some info if anyone knows:

We are currently running DB2 Connect Enterprise addition on an NT box.
(I'm a DB2/DBA
mainframe guy so please bear with me on this question).
Is there a way to monitor the number of connections from that NT machine
at
any given
time?? What I would be looking for is there a way to tell how many threads
are currently
being run off that box? Is there a command that can be issued from DB2
Connect that lists
the current active threads coming thru it??
I know that when I'm in my little ole DB2 world I can display the active
threads and see them
but I'm looking for something that would give me this information from
outside of the DB2
mainframe and back down on the NT.
Would appreciate any info you might have.

Thanks:
--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267








Stephen Whittaker

Re: DB2 Connect Enterprise adtition
(in response to RompotK@SCHNEIDER.COM)
Leon:
Thanks for the info...I set the db2connect_in_app_process=0 and that did
the trick..

Appreciate the response.

--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267


-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, January 05, 2000 10:48 AM
To: [login to unmask email]
Subject: Re: DB2 Connect Enterprise adtition


There are several ways of figuring out this information. Which are
available to you will depend on the version that you have. DB2 Connect V6.1
has the most complete set. In all versions you can issue LIST DCS
APPLICATIONS command using command line processor to display a line for
each database connection coming through a DB2 Connect EE server. It is
important to note that connections originating from DB2 Connect EE box
itself will not be reflected in this display unless you are using V6.1 and
do something special i.e. set DBCONNECT_IN_APP_PROCESS=0.

In V5.2 and later you can also use DB2 Control Center to display pretty
much the same information. In V6.1 you can also use Windows NT Performance
monitor to display active connections and lots of other very useful info.
Both DB2 Control Center and Windows NT performance monitor allow you to do
all monitoring form a remote workstation i.e. you don't have to sit at the
DB2 Connect EE console.

To invoke Windows NT Performance Monitor click on
Start/Programs/Administrative Tools/Performance Monitor. Then click on "+"
button to add DB2 Connect performance counters that you want
graphed/reported. Keep in mind that if no applications are active DB2
Connect counters will not even show up in the list.

As I said before, if you want applications running on the DB2 Connect box
itself to be reported you will need to set DBCONNECT_IN_APP_PROCESS=0.

Leon Katsnelson, DB2 Connect Development Manager
mailto:[login to unmask email]


"Whittaker, Stephen" <[login to unmask email]> on 01/05/2000 09:48:19 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: DB2 Connect Enterprise addtition




Could use some info if anyone knows:

We are currently running DB2 Connect Enterprise addition on an NT box.
(I'm a DB2/DBA
mainframe guy so please bear with me on this question).
Is there a way to monitor the number of connections from that NT machine
at
any given
time?? What I would be looking for is there a way to tell how many threads
are currently
being run off that box? Is there a command that can be issued from DB2
Connect that lists
the current active threads coming thru it??
I know that when I'm in my little ole DB2 world I can display the active
threads and see them
but I'm looking for something that would give me this information from
outside of the DB2
mainframe and back down on the NT.
Would appreciate any info you might have.

Thanks:
--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267













[login to unmask email]

Re: DB2 Connect Enterprise adtition
(in response to Leon Katsnelson)
Minor typo Leon, that should be DB2CONNECT_IN_APP_PROCESS.

"db2set DB2CONNECT_IN_APP_PROCESS=0"

Are there any performance implications by making this change?

--------------------
Kurt Rompot
DB2 Database Analyst
Schneider National, Inc.
[login to unmask email]




[login to unmask email]
OM To: [login to unmask email]
Sent by: DB2 cc:
Data Base Subject: Re: DB2 Connect Enterprise adtition
Discussion
List
<[login to unmask email]
OM>


01/05/2000
09:47 AM
Please
respond to
DB2 Data Base
Discussion
List





There are several ways of figuring out this information. Which are
available to you will depend on the version that you have. DB2 Connect V6.1
has the most complete set. In all versions you can issue LIST DCS
APPLICATIONS command using command line processor to display a line for
each database connection coming through a DB2 Connect EE server. It is
important to note that connections originating from DB2 Connect EE box
itself will not be reflected in this display unless you are using V6.1 and
do something special i.e. set DBCONNECT_IN_APP_PROCESS=0.

In V5.2 and later you can also use DB2 Control Center to display pretty
much the same information. In V6.1 you can also use Windows NT Performance
monitor to display active connections and lots of other very useful info.
Both DB2 Control Center and Windows NT performance monitor allow you to do
all monitoring form a remote workstation i.e. you don't have to sit at the
DB2 Connect EE console.

To invoke Windows NT Performance Monitor click on
Start/Programs/Administrative Tools/Performance Monitor. Then click on "+"
button to add DB2 Connect performance counters that you want
graphed/reported. Keep in mind that if no applications are active DB2
Connect counters will not even show up in the list.

As I said before, if you want applications running on the DB2 Connect box
itself to be reported you will need to set DBCONNECT_IN_APP_PROCESS=0.

Leon Katsnelson, DB2 Connect Development Manager
mailto:[login to unmask email]


"Whittaker, Stephen" <[login to unmask email]> on 01/05/2000 09:48:19 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: DB2 Connect Enterprise addtition




Could use some info if anyone knows:

We are currently running DB2 Connect Enterprise addition on an NT box.
(I'm a DB2/DBA
mainframe guy so please bear with me on this question).
Is there a way to monitor the number of connections from that NT machine
at
any given
time?? What I would be looking for is there a way to tell how many threads
are currently
being run off that box? Is there a command that can be issued from DB2
Connect that lists
the current active threads coming thru it??
I know that when I'm in my little ole DB2 world I can display the active
threads and see them
but I'm looking for something that would give me this information from
outside of the DB2
mainframe and back down on the NT.
Would appreciate any info you might have.

Thanks:
--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267













Leon Katsnelson

Re: DB2 Connect Enterprise adtition
(in response to Stephen Whittaker)
I accidentally deleted a post from somebody (Kurt I think) who was asking
me about performance implications of setting DB2CONNECT_IN_APP_PROCESS=0 in
DB2 Connect. The answer is "yes, there are possible performance
implications". However, the extent of these implications is highly version,
application, and configuration dependent.

I'll try to explain what setting this parameter does and some of the
conclusions that may be drawn from it. All requests from remote clients
(those applications running on boxes physically separated from the DB2
Connect EE server by a LAN) are handled by an "agent" in the DB2 Connect EE
address space. However, application running on the DB2 Connect EE server
box (as opposed to remote client) loads DB2 Connect shared library on UNIX
or DLL on Windows NT and OS/2 into its own address space instead of giving
it to an agent in the DB2 Connect EE address space to handle. In other
words DB2 Connect code is executed as part of the application in the
application address space. All of the monitoring we do is tied to
extracting the information from the agents about the work they are doing or
they've already done on behalf of the application. Because local to the
server) applications don't use agents, you don't see them reflected in any
monitoring information that you receive. Another side effect is they don't
get to participate in the SYSPLEX load-balancing and fail-over support we
have on the engine side. A third implication is that in V6.1 they also
don't participate in connection pooling that is available on the DB2
Connect engine side but they can still participate in ODBC connection
pooling on Windows NT.

So, here comes the DB2CONNECT_IN_APP_PROCESS=0 or "=NO" parameter. As the
name suggests, setting this parameter to NO or 0 (default is YES or 1) will
change the behaviour of the local applications and will make them use the
DB2 Connect agents running in the DB2 Connect address space. if this
parameter is turned on local applications participate in all aspects of
engine work and are treated exactly the same as remote applications i.e.
they are reflected in all monitoring, participate in SYSPEX load-balancing
and fail-over, and can fully exploit DB2 Connect native connection pooling
in addition to the ODBC connection pooling (the difference between the 2 is
a subject of another post or a white paper). However, this means that every
request from an application has to cross address space boundary (we call it
firewall) and that can add to the cost of executing a request. The
additional cost varies by operating system.

Now what does this all meant to performance? We know there is some delta
cost associated with crossing address space boundary, however, we also know
that the additional elapsed time for doing so is insignificant when
measured against the length of the entire transaction (we are talking way
less then a millisecond). So, the implication will be potentially reduced
overall throughput of the DB2 Connect EE server rather then response time
because. However, we don't see this happening in practice. I will explain
why not. Typically people run applications local to the DB2 Connect EE
server because we recommend it for Application Servers and Web Servers. In
the web server world, it is typical for a CGI script (that is executed on
every web page hit) to build a connection execute a transaction (e.g.
stored procedure) and disconnect. When an agent is used in the DB2 Connect
EE server these applications get tremendous boost in performance and
greatly reduced resource utilisation from utilising connection pooling. The
extra cost of crossing the address space boundary does not even show up
next to the savings achieved by connection pooling. When it comes to
Application Servers that may have long running persistent connections to
the database server, the savings of connection pooling are not there YET.
However, in V7.1 we are delivering Connection Concentrator (reusing
connection on transaction boundary but this is not yet announced and a
topic of yet another white paper). With Connection Concentrator turned on
we expect that the savings of going through an agent will be dwarf any cost
of crossing address space. As a matter of fact, we estimate that Connection
Concentrator will greatly improve both response time and increase capacity
of DB2 Connect servers by several orders of magnitude. In addition, it will
greatly reduce OS/390 CPU time required to service heavy volume of web and
client-server requests.

You asked a very simple answer and I gave you a very complex answer. I do
hope, however, that it does help everybody make a bit better decisions and
sheds some light on where we are going with this technology.

Leon Katsnelson, DB2 Connect Development Manager
mailto:[login to unmask email]


"Whittaker, Stephen" <[login to unmask email]> on 01/05/2000 11:31:26 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: Re: DB2 Connect Enterprise adtition




Leon:
Thanks for the info...I set the db2connect_in_app_process=0 and that did
the trick..

Appreciate the response.

--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267


-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, January 05, 2000 10:48 AM
To: [login to unmask email]
Subject: Re: DB2 Connect Enterprise adtition


There are several ways of figuring out this information. Which are
available to you will depend on the version that you have. DB2 Connect V6.1
has the most complete set. In all versions you can issue LIST DCS
APPLICATIONS command using command line processor to display a line for
each database connection coming through a DB2 Connect EE server. It is
important to note that connections originating from DB2 Connect EE box
itself will not be reflected in this display unless you are using V6.1 and
do something special i.e. set DBCONNECT_IN_APP_PROCESS=0.

In V5.2 and later you can also use DB2 Control Center to display pretty
much the same information. In V6.1 you can also use Windows NT Performance
monitor to display active connections and lots of other very useful info.
Both DB2 Control Center and Windows NT performance monitor allow you to do
all monitoring form a remote workstation i.e. you don't have to sit at the
DB2 Connect EE console.

To invoke Windows NT Performance Monitor click on
Start/Programs/Administrative Tools/Performance Monitor. Then click on "+"
button to add DB2 Connect performance counters that you want
graphed/reported. Keep in mind that if no applications are active DB2
Connect counters will not even show up in the list.

As I said before, if you want applications running on the DB2 Connect box
itself to be reported you will need to set DBCONNECT_IN_APP_PROCESS=0.

Leon Katsnelson, DB2 Connect Development Manager
mailto:[login to unmask email]


"Whittaker, Stephen" <[login to unmask email]> on 01/05/2000 09:48:19 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: DB2 Connect Enterprise addtition




Could use some info if anyone knows:

We are currently running DB2 Connect Enterprise addition on an NT box.
(I'm a DB2/DBA
mainframe guy so please bear with me on this question).
Is there a way to monitor the number of connections from that NT machine
at
any given
time?? What I would be looking for is there a way to tell how many threads
are currently
being run off that box? Is there a command that can be issued from DB2
Connect that lists
the current active threads coming thru it??
I know that when I'm in my little ole DB2 world I can display the active
threads and see them
but I'm looking for something that would give me this information from
outside of the DB2
mainframe and back down on the NT.
Would appreciate any info you might have.

Thanks:
--Steve....

Steve Whittaker
DB2/DBA Carolina Power & Light
Mail stop: CPB 17A4 - Raleigh
Email: [login to unmask email]
Phone: (919) 546-7267








the