hi,
I need to connect to DB2 UDB running in mainframes to a DTS package
that imports data from the DB2 database to a SQL server Database.

I got DB2 Runtime client installed and i use DB2 ODBC driver.

Do i need DB2 Connect installed in the same machine where the DB2 RT is
installed and do i need DB2 Connect lisense for connecting to a the DB2
UDB server which runs in mainframes?

Is installing DB2 Connect on the same machine where the DB2 runtime
installed is ok?


TIA
-Satish Sivasubramanian Gopinathan

In article <1135942809.638073.170270@z14g2000cwz.googlegroups .com>,
techsatish@gmail.com says...
> hi,
> I need to connect to DB2 UDB running in mainframes to a DTS package
> that imports data from the DB2 database to a SQL server Database.
>
> I got DB2 Runtime client installed and i use DB2 ODBC driver.
>
> Do i need DB2 Connect installed in the same machine where the DB2 RT is
> installed and do i need DB2 Connect lisense for connecting to a the DB2
> UDB server which runs in mainframes?
>
> Is installing DB2 Connect on the same machine where the DB2 runtime
> installed is ok?
>
>
> TIA
> -Satish Sivasubramanian Gopinathan
>
>

I just spent a lot of time researching this. IBM does not make it easy
to find out.

But, from my research, it seems that anytime you want to connect from a
non-mainframe computer to a mainframe DB2, IBM wants you to purchase a
DB2 Connect license. You don't have to really install DB2 Connect --
the driver is downloadable by itself. However, the conditions listed by
IBM indicate that you must purchase the DB2 Connect license.

--
Barry Schrager

I do not think Barry is correct.

It is necessary to have DB2 Connect installed, either as a personal
edition for the client or as a seperate connect server.
Runtime Client allone won't work for z/OS.

What you probably want to do is installing a personal edition of DB2
Connect.

And, btw, the documentation is clear about this:
"To connect to an IBM mainframe database you require a licensed DB2
Connect product or a licensed product that contains a DB2 Connect
component, like DB2 Universal Database(TM) Enterprise Server Edition.
You cannot connect to an IBM mainframe database using a DB2 Run-Time
client."

http://publib.boulder.ibm.com/infoce...n/c0008225.htm

techsatish@gmail.com wrote:
> hi,
> I need to connect to DB2 UDB running in mainframes to a DTS package
> that imports data from the DB2 database to a SQL server Database.
>
> I got DB2 Runtime client installed and i use DB2 ODBC driver.
>
> Do i need DB2 Connect installed in the same machine where the DB2 RT is
> installed and do i need DB2 Connect lisense for connecting to a the DB2
> UDB server which runs in mainframes?
>
> Is installing DB2 Connect on the same machine where the DB2 runtime
> installed is ok?
>
>
> TIA
> -Satish Sivasubramanian Gopinathan
>
From a technical standpoint, somewhere you must have DB2 Connect
installed to access DB2 on z, DB2 on 390, or DB2 on iseries from a
web-based or distributed application on Windows/Linux/UNIX ... unless
you are using a Java type 4 driver.

From a technical standpoint, DB2 Connect comes in two primary flavors:
Personal Edition or Enterprise Edition. PE is standalone single-user,
cannot accept inbound connections from other servers, other clients, or
app servers ... and must connect directly to DB2 on the mainframe. EE is
a server-based edition that can accept multiple inbound connections from
clients or from app servers. This can be used as a 3-tiered approach and
is required for advanced host-based functions such as WLM exploitation
and connection pooling.

From a licensing standpoint, you must be licensed for DB2 Connect in
order to access DB2 on z, DB2 on 390, or DB2 on iseries from a web-based
or distributed application on Windows/Linux/UNIX. Whether you use type-4
or not. Also, from a licensing and packaging standpoint, there are four
options: Personal Edition, Enterprise Edition, Application Server
Edition, and Unlimited Edition. UE ships with both Personal and
Enterprise Editions while Application server edition ships with
Enterprise Edition only (makes sense cause it's the only "technical"
solution for use with App servers).

See
http://www-128.ibm.com/developerwork...kopoulos1.html
for more info.

Back to the OP's question. It depends upon what you are trying to do and
what your objectives are. You do not have to have DB2 Connect on the
same machine with the RT client ... you can do as described above using
the 3-tiered approach. But understand that you must be licensed in some
way for a connection into the "other" DB2 Connect EE server and you also
add another network hop that may impact performance.

If you wish, you can install DB2 Connect on the same machine ... you
then don't need a separate RT client because it should be laid down with
DB2 Connect. Then, you must be licensed for a complete DB2 Connect
Personal Edition or Enterprise Edition on that machine.

Hope this helps.

Larry Edelstein

Or you can also consider an alternative driver (StarSQL, HiT etc...)
:-)

Larry wrote:
> techsatish@gmail.com wrote:
> > hi,
> > I need to connect to DB2 UDB running in mainframes to a DTS package
> > that imports data from the DB2 database to a SQL server Database.
> >
> > I got DB2 Runtime client installed and i use DB2 ODBC driver.
> >
> > Do i need DB2 Connect installed in the same machine where the DB2 RT is
> > installed and do i need DB2 Connect lisense for connecting to a the DB2
> > UDB server which runs in mainframes?
> >
> > Is installing DB2 Connect on the same machine where the DB2 runtime
> > installed is ok?
> >
> >
> > TIA
> > -Satish Sivasubramanian Gopinathan
> >
> From a technical standpoint, somewhere you must have DB2 Connect
> installed to access DB2 on z, DB2 on 390, or DB2 on iseries from a
> web-based or distributed application on Windows/Linux/UNIX ... unless
> you are using a Java type 4 driver.
>
> From a technical standpoint, DB2 Connect comes in two primary flavors:
> Personal Edition or Enterprise Edition. PE is standalone single-user,
> cannot accept inbound connections from other servers, other clients, or
> app servers ... and must connect directly to DB2 on the mainframe. EE is
> a server-based edition that can accept multiple inbound connections from
> clients or from app servers. This can be used as a 3-tiered approach and
> is required for advanced host-based functions such as WLM exploitation
> and connection pooling.
>
> From a licensing standpoint, you must be licensed for DB2 Connect in
> order to access DB2 on z, DB2 on 390, or DB2 on iseries from a web-based
> or distributed application on Windows/Linux/UNIX. Whether you use type-4
> or not. Also, from a licensing and packaging standpoint, there are four
> options: Personal Edition, Enterprise Edition, Application Server
> Edition, and Unlimited Edition. UE ships with both Personal and
> Enterprise Editions while Application server edition ships with
> Enterprise Edition only (makes sense cause it's the only "technical"
> solution for use with App servers).
>
> See
> http://www-128.ibm.com/developerwork...kopoulos1.html
> for more info.
>
> Back to the OP's question. It depends upon what you are trying to do and
> what your objectives are. You do not have to have DB2 Connect on the
> same machine with the RT client ... you can do as described above using
> the 3-tiered approach. But understand that you must be licensed in some
> way for a connection into the "other" DB2 Connect EE server and you also
> add another network hop that may impact performance.
>
> If you wish, you can install DB2 Connect on the same machine ... you
> then don't need a separate RT client because it should be laid down with
> DB2 Connect. Then, you must be licensed for a complete DB2 Connect
> Personal Edition or Enterprise Edition on that machine.
>
> Hope this helps.
>
> Larry Edelstein

db2team@hotmail.com wrote:
> Or you can also consider an alternative driver (StarSQL, HiT etc...)
> :-)
>
> Larry wrote:
>
>>techsatish@gmail.com wrote:
>>
>>>hi,
>>>I need to connect to DB2 UDB running in mainframes to a DTS package
>>>that imports data from the DB2 database to a SQL server Database.
>>>
>>>I got DB2 Runtime client installed and i use DB2 ODBC driver.
>>>
>>>Do i need DB2 Connect installed in the same machine where the DB2 RT is
>>>installed and do i need DB2 Connect lisense for connecting to a the DB2
>>>UDB server which runs in mainframes?
>>>
>>>Is installing DB2 Connect on the same machine where the DB2 runtime
>>>installed is ok?
>>>
>>>
>>>TIA
>>>-Satish Sivasubramanian Gopinathan
>>>
>>
>> From a technical standpoint, somewhere you must have DB2 Connect
>>installed to access DB2 on z, DB2 on 390, or DB2 on iseries from a
>>web-based or distributed application on Windows/Linux/UNIX ... unless
>>you are using a Java type 4 driver.
>>
>> From a technical standpoint, DB2 Connect comes in two primary flavors:
>>Personal Edition or Enterprise Edition. PE is standalone single-user,
>>cannot accept inbound connections from other servers, other clients, or
>>app servers ... and must connect directly to DB2 on the mainframe. EE is
>>a server-based edition that can accept multiple inbound connections from
>>clients or from app servers. This can be used as a 3-tiered approach and
>>is required for advanced host-based functions such as WLM exploitation
>>and connection pooling.
>>
>> From a licensing standpoint, you must be licensed for DB2 Connect in
>>order to access DB2 on z, DB2 on 390, or DB2 on iseries from a web-based
>>or distributed application on Windows/Linux/UNIX. Whether you use type-4
>>or not. Also, from a licensing and packaging standpoint, there are four
>>options: Personal Edition, Enterprise Edition, Application Server
>>Edition, and Unlimited Edition. UE ships with both Personal and
>>Enterprise Editions while Application server edition ships with
>>Enterprise Edition only (makes sense cause it's the only "technical"
>>solution for use with App servers).
>>
>>See
>>http://www-128.ibm.com/developerwork...kopoulos1.html
>>for more info.
>>
>>Back to the OP's question. It depends upon what you are trying to do and
>>what your objectives are. You do not have to have DB2 Connect on the
>>same machine with the RT client ... you can do as described above using
>>the 3-tiered approach. But understand that you must be licensed in some
>>way for a connection into the "other" DB2 Connect EE server and you also
>>add another network hop that may impact performance.
>>
>>If you wish, you can install DB2 Connect on the same machine ... you
>>then don't need a separate RT client because it should be laid down with
>>DB2 Connect. Then, you must be licensed for a complete DB2 Connect
>>Personal Edition or Enterprise Edition on that machine.
>>
>>Hope this helps.
>>
>>Larry Edelstein
>
>
But if you do, then do the proper comparisons from a feature/function
and total cost of ownership perspective ... before you make your decision.

Larry Edelstein

One thing to add if it is not clear - if the client application is on
zOS, MVS, VM, VSE, or AS/400, you do not need a client license to get
data from a DB2 database server on Linux, UNIX or Windows.

Larry wrote:
> techsatish@gmail.com wrote:
> > hi,
> > I need to connect to DB2 UDB running in mainframes to a DTS package
> > that imports data from the DB2 database to a SQL server Database.
> >
> > I got DB2 Runtime client installed and i use DB2 ODBC driver.
> >
> > Do i need DB2 Connect installed in the same machine where the DB2 RT is
> > installed and do i need DB2 Connect lisense for connecting to a the DB2
> > UDB server which runs in mainframes?
> >
> > Is installing DB2 Connect on the same machine where the DB2 runtime
> > installed is ok?
> >
> >
> > TIA
> > -Satish Sivasubramanian Gopinathan
> >
> From a technical standpoint, somewhere you must have DB2 Connect
> installed to access DB2 on z, DB2 on 390, or DB2 on iseries from a
> web-based or distributed application on Windows/Linux/UNIX ... unless
> you are using a Java type 4 driver.
>
> From a technical standpoint, DB2 Connect comes in two primary flavors:
> Personal Edition or Enterprise Edition. PE is standalone single-user,
> cannot accept inbound connections from other servers, other clients, or
> app servers ... and must connect directly to DB2 on the mainframe. EE is
> a server-based edition that can accept multiple inbound connections from
> clients or from app servers. This can be used as a 3-tiered approach and
> is required for advanced host-based functions such as WLM exploitation
> and connection pooling.
>
> From a licensing standpoint, you must be licensed for DB2 Connect in
> order to access DB2 on z, DB2 on 390, or DB2 on iseries from a web-based
> or distributed application on Windows/Linux/UNIX. Whether you use type-4
> or not. Also, from a licensing and packaging standpoint, there are four
> options: Personal Edition, Enterprise Edition, Application Server
> Edition, and Unlimited Edition. UE ships with both Personal and
> Enterprise Editions while Application server edition ships with
> Enterprise Edition only (makes sense cause it's the only "technical"
> solution for use with App servers).
>
> See
> http://www-128.ibm.com/developerwork...kopoulos1.html
> for more info.
>
> Back to the OP's question. It depends upon what you are trying to do and
> what your objectives are. You do not have to have DB2 Connect on the
> same machine with the RT client ... you can do as described above using
> the 3-tiered approach. But understand that you must be licensed in some
> way for a connection into the "other" DB2 Connect EE server and you also
> add another network hop that may impact performance.
>
> If you wish, you can install DB2 Connect on the same machine ... you
> then don't need a separate RT client because it should be laid down with
> DB2 Connect. Then, you must be licensed for a complete DB2 Connect
> Personal Edition or Enterprise Edition on that machine.
>
> Hope this helps.
>
> Larry Edelstein

In article <ZYetf.1022$l06.247@fe11.lga>, larry@nospam.net says...
> But if you do, then do the proper comparisons from a feature/function
> and total cost of ownership perspective ... before you make your decision.
>
> Larry Edelstein
>
>

Larry,

The problem I ran into was that it was difficult to correlate the cost
of each of the DB2 Connect variations.

Additionally, the DB2 Connect Enterprise Edition talks about "named" and
"concurrent" users, but fails to spell out exactly which one applies to
what, what exactly a "named" user is, and how you get the user changed,
etc.

--
Barry Schrager

Barry Schrager wrote:
> In article <ZYetf.1022$l06.247@fe11.lga>, larry@nospam.net says...
>
>>But if you do, then do the proper comparisons from a feature/function
>>and total cost of ownership perspective ... before you make your decision.
>>
>>Larry Edelstein
>>
>>
>
>
> Larry,
>
> The problem I ran into was that it was difficult to correlate the cost
> of each of the DB2 Connect variations.
>
> Additionally, the DB2 Connect Enterprise Edition talks about "named" and
> "concurrent" users, but fails to spell out exactly which one applies to
> what, what exactly a "named" user is, and how you get the user changed,
> etc.
>
Did you read the article I provided in the link? It really breaks all of
this down. As far as named vs. concurrent is concerned, there is more on
this in

http://www-128.ibm.com/developerwork...kopoulos1.html

but not specific to DB2 Connect.

See the DB2 Connect announcement letter:

http://www-306.ibm.com/common/ssi/OI...etter%20search

and search for "concurrent" or "registered":

A concurrent user is a person, application, or device used by a single
person or device that has established one or more connections to one or
more databases through a DB2 Connect server. A user with multiple
connections to a single DB2 Connect server counts as only one concurrent
user of the DB2 Connect server. Persons using applications that connect
to a DB2 Connect server through other products that act as connection
concentrators must be counted as DB2 Connect users and are subject to
use-based charges. Persons using applications based on Web technologies
(intranet or Internet) can not be licensed as concurrent users. In such
cases, each potential application user must be licensed as a registered
user or either DB2 Connect Application Server Edition or DB2 Connect
Unlimited Edition products should be used.

Registered user

A registered user is a person, application, or device used by a single
person , application, or device entitled to establish one or more
connections to any authorized DB2 Connect server in the customer's
enterprise, either directly or through a multiplexing program,
application server, or Web server.


Larry Edelstein