- 1. ADSM V3 for NT DSM.OPT file (score: 1)
- Author: "Swartz, Ian" <Iswartz AT SELIGMANDATA DOT COM>
- Date: Wed, 29 Jul 1998 16:39:33 -0400
- Hi, I am beta testing ADSM V3 for NT. Is there anyway to force client PC's to use a DSM.OPT file that is located on a server? rather than having separate DSM.OPT files sitting on each client PC, Howe
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg01051.html (10,622 bytes)
- 2. Re: ADSM V3 for NT DSM.OPT file (score: 1)
- Author: Matt Cleland <adsmrus AT STLNET DOT COM>
- Date: Wed, 29 Jul 1998 16:24:27 -0500
- Hi Ian: You can accomplish what you are trying to do by using the "Client Option Sets" feature of ADSM V3. Look at the docs for "DEFINE CLOPTSET" and "DEFINE CLIENTOPT" for more information. -- Matt
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg01057.html (11,752 bytes)
- 3. Re: ADSM V3 for NT DSM.OPT file (score: 1)
- Author: Eric van Loon <evanloon AT KLM DOT NL>
- Date: Thu, 30 Jul 1998 09:50:52 +0200
- Hi Ian! Find my replies embedded below: I am beta testing ADSM V3 for NT. Is there anyway to force client PC's to use a DSM.OPT file that is located on a server? rather than having separate DSM.OPT f
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg01072.html (11,729 bytes)
This search system is powered by
Namazu