> > >> > The IBM's terms, concurrent users and multiplexing program are
> > >> > confusing. Okay, there are 12 server processes that make connection
> > >> > the databases to do updates/select, etc. There are hundreds of
> > >> > "client" systems, which do not use DB2 software, communicating with
> > >> > another daemon process (on the same server) that does not make
> > >> > connection to the DB2 database. This non-DB2 process is the middleman
> > >> > between the DB2-bound processes and the "client" computers. Are these
> > >> > client computers concurrent users or the 12 DB2 server processes?
> > >> > Which are the multiplexing programs here?
> > >>
> > >> My understanding of "multiplexing" would mean that the application that
> > >> works on behalf of n users requires n user licenses for DB2. User
> > >> licenses (named or concurrent) refers to real, living, breathing bodies
> > >> that use the data from the database. Note that IBM may make exceptions
> > >> for this if those real, living, breathing bodies are, say, canines,
> > >> felines, or the like.
> > >>
> > >> My understanding of this entire thread would mean you should be talking
> > >> to your IBM or ISV sales rep rather than the techies in here ;-)
> > >
> > > I don't think that is correct. If the maximum number of threads to DB2
> > > created by the application is 12 at ay given time (assuming that is the
> > > situation here), you would only need 12 licenses. Otherwise, such if a
> > > page contained data from a DB2 database, you would need a license for
> > > every person who ever accessed that webpage, which is absurd.
> > Which is what the web or unlimited versions are all about.
> The following two paragraphs are from the IBM article about licensing at:
> "DB2 WSE is licensed by the Client-to-Server model using a concurrent
> (sometimes referred to as "capacity pricing") or registered user option."
> "The 'concurrent user license' is appropriate for applications or devices
> that have established a connection to one or more databases on one server. A
> user with multiple connections to a single server counts as only one
> concurrent user. The one exception is the case where multiple connections
> are made by a multiplexing program, application server, or other program
> that connects to DB2 UDB, providing access on behalf of other users. In the
> concurrent user model, the customer must ensure that each server is licensed
> for the maximum number of users that will use that server product at any one
> time. The base license cost ($999) still applies, and each concurrent user
> license costs $249."
> Notice that you can license by registered user OR by number of concurrent
> users. To quote the article "In the concurrent user model, the customer must
> ensure that each server is licensed for the maximum number of users that
> will use that server product at any one time." So if your application only
> can process 12 connections to DB2 simultaneously (because it can only
> process 12 clients at a time), you only need 12 licenses with the concurrent
> user licensing option.
> The section about multiplexing sounds like a description of your application
> which provides access to DB2 on behalf of other users, even if the same
> userid is always connected to DB2 by the server application (on behalf of
> the clients).