Hello,
With my NT Client I administrate 3 ADSM Server (1xV2 & 2xV3). The way to
do this is to define several dsm.opt file.
And to define a batch file with put the following env variable

SET DSM_CONFIG=c:\win32app\ibm\adsm\baclient\dsmbuc.opt
SET DSMG_CONFIG=c:\win32app\ibm\adsm\baclient\dsmbuc.opt
cd \win32app\ibm\adsm\baclient
dsmadm

I do this for each program and each server, then it works fine

Regards

> g          GE Medical Systems 
> __________________________________
> Eric Boireau                                                GITS
> Unix / NT  System Engineer
> 
> GE Medical Systems S.A
> 283, rue de la Minière 
> 78533 BUC Cedex France
> Tél: (33) 01 30 70 39 51,  DC: 8*644 3951
> Fax: (33) 01 30 70 39 20, DC: 8*644 3920
> mailto:boireer AT euromsx.gemse DOT fr
> 
> Salutations / Best Regards
> 
> 
> ----------
> From:         Espen Toren[SMTP:Espen.Toren AT HDA.HYDRO DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         lundi 12 janvier 1998 14:13
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      NT Admin client administrating mulitiple servers
> 
> Hi all!
> 
> I am currently setting up a new ADSM-server at a new site (v3) in
> addition to the one we already have (v2). I am using the v3 admin
> client
> for NT Workstation 4.0
> 
> My problem is telling the NT admin client to connect to the new
> ADSM-server without installing the admin client into a new directory.
> (I
> imagine future nightmares where we probably are operating up to 6-7
> ADSM-servers, and we are forced to fill up our hard-disks with
> admin-clients....)
> 
> The documentation is telling me that the NT B/A client have this
> option
> built in as the -optfile argument. But I can't see that the
> admin-client
> have the same option.
> 
> Anyone?
> 
> 
> Regards
> 
> Espen Torin
> Norsk Hydro ASA
>