Hi everybody,

we are using DB2 UDB 7.2 FP 11 on WinNT 4.0 (SP5) machines, LDAP works quite
fine. As I already googled, there is however the question on how to apply
e.g. "db2 catalog system odbc data source <name>" on the client-machines.

One can roll out an initial config, no problem. But how do you guys out
there manage deleted or new databases on your clients? I read one post
about "self-repairing MSI packages" but unfortunately, the author did not
elaborate further.

Would I have to use e.g. a WSH-script (check if all DBs in LDAP are
catalogued as ODBC datas ources on client)?

TIA Frederick

I would strongly recommend your creating an MSI-based installation program
("self-repairing MSI packages"). Review the documentation on installer
technologies on the MS web site
(http://msdn.microsoft.com/library/de...-us/dnanchor/h
tml/setup.asp). Purchase an installation development application (such as
InstallShield or WISE) to simplify development thereof. Both of these have
sophisticated ODBC management function, as well as a host of other function
that make development of install / uninstall / update / repair programs
easy.

Using a WSH script would probably work, but I wouldn't go that way.

"Frederick Page" <for_your_spam_only@gmx.de> wrote in message
news:7ecbf651.0402110715.2a5355b5@posting.google.c om...
> Hi everybody,
>
> we are using DB2 UDB 7.2 FP 11 on WinNT 4.0 (SP5) machines, LDAP works
quite
> fine. As I already googled, there is however the question on how to apply
> e.g. "db2 catalog system odbc data source <name>" on the client-machines.
>
> One can roll out an initial config, no problem. But how do you guys out
> there manage deleted or new databases on your clients? I read one post
> about "self-repairing MSI packages" but unfortunately, the author did not
> elaborate further.
>
> Would I have to use e.g. a WSH-script (check if all DBs in LDAP are
> catalogued as ODBC datas ources on client)?
>
> TIA Frederick