Hi Gerald,

Glad to hear that you've got it working!

You are, of course, correct... ideally the ODBC driver install would
launch as soon as it is unpacked.

The reason we don't do this is because of the prerequisite that the MDAC
be installed prior to running the setup.exe program. If the MDAC is not
installed (as could be the case for Windows 95, 98 and NT 4.0), then the
ODBC setup program should not be run until you've verified that you have
the correct MDAC install package (or you can install the MDAC on your own,
then run the ODBC setup program). The README file for the ODBC driver
discusses this in the "Installation" sections.

I think that there are areas of the install process that can be improved,
especially for the case where MDAC is already installed. That's something
we can consider for future releases.

Thanks for your feedback.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Gerald Wichmann <gwichmann AT SANSIA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/05/2001 15:08
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: ODBC Driver



That was the problem. After running the BA Client exe which runs the
install after it unpacks, I just assumed the ODBC .exe would do the
same. I noticed by the README you suggested that there should be a
/program files/Tivoli/TSM/odbc directory and there was none. Then I
noticed the behavior of the ODBC exe and dug down to find that disk1
directory and ran setup.exe.

Problem solved.. works fine once you figure that out. Confusing way of
doing things though. You guys should package the two similarly IMO.

Gerald Wichmann
System Engineer
StorageLink
408-844-8893 (v)
408-844-9801 (f)