The ODBC driver is a completely separate entity from the rest of the
backup-archive client. It has no dependencies on the b-a client, and the
b-a client has no dependencies on the ODBC driver. Therefore, in order to
help reduce the already substantial size of the client package, the ODBC
driver was packaged separately. (Note: the ODBC driver used to be around
14 MB in size, but starting with version 5.1, we stopped shipping the
English version of the MDAC. This significantly reduced the size of the
ODBC driver package to around 5 MB. But for now, it is still a separate
package.)
As far as the API goes, it is always installed with the b-a client since
certain b-a components rely on the API (such as the DSMCUTIL utility). The
API SDK (not to be confused with the API) is included in the client
package, but its size is negligible.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Burak Demircan <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/09/2002 04:09
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Antwort: odbc ?
Merhaba Tsm,
Then why is API is included in the client installation set? (it gives us
the
option to install or not)
Thanks
Burak
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09.07.2002 14:06
Please respond to ADSM-L
� � � �
� � � � To: � � � �[EMAIL PROTECTED]
� � � � cc: � � � �
� � � � Subject: � � � �Antwort: odbc ?
Merhaba Burak
An ODBC driver allows you to use a relational database product such as SQL
to query the database and display the results. Client installation does
not
set include everything we need. You have to install API and ODBC
separately.
selamlar...
