Thanks for the clarification on my concern.

There was some talk a long time ago about having one copy of ADSM code
installed on the server, and then having each user use that copy instead of
installing it on each individual machine.  Each customer would obviously need
to have his own DSM.OPT, but the rest is shared in typical server based
product fashion.  Is this still a supported method of running ADSM under V3?

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: mcf42.dll - where does it come from?
Author:  owner-adsm-l (INTERNET.OWNERAD) at SNADGATE
Date:    3/26/98 12:37 PM


Liz, Tony, Jerry:

MFC42.DLL is copied at installation time to your
<windows installation>/system32 directory.  If MFC42.DLL
is locked by another process then InstallShield stages the
update/replacement for the next boot of the machine.  The
installation logic will not down-level an existing MFC42.DLL
i.e. it will only replace MFC42.DLL if the level shipped with
MFC is higher than that already installed on your system.
You should *not* need to put the adsm shared directory
in your path.  You should install the client using the ADSM
installer on each machine and not simply copy the files from
one installed machine to another.  There is no NT vs Win95
issue with the MFC DLLs; the same ones are used for both
platforms.

Hope this clarifies and answers your questions.

Regards,

Mike Dile
IBM Storage Systems Division
ADSM Client Development
mikedile AT us.ibm DOT com