Hi Gerhard, Yes to both. We are running two TSM 3740 servers on a single machine. We run both out of root uid (I think Cornell use an alternative uid - please ask Paul Zarnowski about that) and it works very well. Files in each directory are as you expected but including the .lic files; it does expect to find them there too. We link the core file to a much larger space and get the dump elsewhere. ls -l /dsmservers/SERVER_A total 20944 -r-xr-xr-x 1 root sys 696 Aug 3 14:10 10client.lic* -r-xr-xr-x 1 root sys 694 Aug 3 14:10 1client.lic* -r-xr-xr-x 1 root sys 696 Aug 3 14:10 50client.lic* -r-xr-xr-x 1 root sys 695 Aug 3 14:10 5client.lic* -rw-r--r-- 1 root sys 58 Jan 4 14:36 adsmserv.lock -r-xr-xr-x 1 root sys 705 Aug 3 14:10 advdev.lic* lrwxrwxrwx 1 root sys 21 Jul 28 17:49 core -> /coredump/core.SERVER_A -rw-r--r-- 1 root system 682 Jan 11 09:56 devconfig -r-xr-xr-x 1 root sys 698 Aug 3 14:10 domino.lic* -r-xr-xr-x 1 root sys 696 Aug 3 14:10 drm.lic* -rw-r--r-- 1 root system 239507 Jan 11 10:30 dsmaccnt.log -rw-r--r-- 1 root sys 868 Aug 3 14:10 dsmerror.log -rwx--x--x 1 root sys 687634 Aug 3 14:10 dsmlicense* -rw-r--r-- 1 root sys 169 Jan 4 14:36 dsmserv.dsk -rw-r--r-- 1 root sys 1043 Sep 8 10:13 dsmserv.opt -rwxr-xr-- 1 root sys 678 Aug 4 16:45 dsmstart.SERVER_A -r-xr-xr-x 1 root sys 702 Aug 3 14:10 informix.lic* -r-xr-xr-x 1 root sys 705 Aug 3 14:10 lnotes.lic* drwxrwx--- 2 root system 512 Jul 18 11:58 lost+found/ -rw-r--r-- 1 root sys 666 Aug 3 14:10 monitor.log -r-xr-xr-x 1 root sys 705 Aug 3 14:10 msexch.lic* -r-xr-xr-x 1 root sys 700 Aug 3 14:10 mssql.lic* -r-xr-xr-x 1 root sys 693 Aug 3 14:10 network.lic* -rw-r--r-- 1 root sys 1513 Aug 3 15:06 nodelock -r-xr-xr-x 1 root sys 698 Aug 3 14:10 opensys.lic* -r-xr-xr-x 1 root sys 700 Aug 3 14:10 oracle.lic* -r-xr-xr-x 1 root sys 701 Aug 3 14:10 sapr3.lic* -r-xr-xr-x 1 root sys 706 Aug 3 14:10 spacemgr.lic* -rw-r----- 1 root system 29483 Jan 11 06:13 volumehistory Sample script to start a server in foreground : #!/bin/ksh -x # # start up ADSM server in foreground # DSMSERV_DIR=/dsmservers/SERVER_A DSMCODE_DIR=/usr/tivoli/tsm/server/bin export DSMSERV_DIR cd $DSMSERV_DIR $DSMCODE_DIR/dsmserv.SERVER_A Sample for background (dsmstart.SERVER_A) : #!/bin/ksh # # start up ADSM server # DSMSERV_DIR=/dsmservers/SERVER_A # DSMCODE_DIR=/usr/tivoli/tsm/server/bin DSMLOGFILE=/var/adm/syslog/SERVER_A.dsmserv.log.$(date +%d-%b-%Y) export DSMSERV_DIR cd $DSMSERV_DIR ulimit -c unlimited ulimit -d unlimited ulimit -s unlimited if [ -f /etc/nodsm.SERVER_A ]; then sleep 60 else ( sleep 5 ; if ps -eo comm|grep xmservd > /dev/null; then # xmservd is already running, so give it a HUP kill -1 `ps -eo comm,pid | awk '$1 == "xmservd" { print $2 }'` else # got to kick xmservd to start it xmpeek -l >/dev/null fi ) & $DSMCODE_DIR/dsmserv.SERVER_A quiet fi sleep 120 exit 0 (this procedure runs all the time and autoatically restarts server if it falls over - providing the file /etc/... does not exist; we've run this for years, more or less as it is now. we start it in inittab as respawn) In the install directory you need to make some links : % ls -l /usr/tivoli/tsm/server/bin/dsmserv* /usr/tivoli/tsm/server/bin/dsmserv lrwxrwxrwx 1 root system 7 Oct 25 08:46 /usr/tivoli/tsm/server/bin/dsmserv.SERVER_A -> dsmserv* lrwxrwxrwx 1 root system 7 Oct 25 08:46 /usr/tivoli/tsm/server/bin/dsmserv.SERVER_B -> dsmserv* If you do this, linking to give two names to the server code, then when you do a ps you can distinguish which instance is which (so you can kill the correct one, should this be so needed ...). I hope this helps and that I haven't missed any more out. If you are still running ADSM rather than TSM you can still do it but you need a lot more in the server config directories; I have deleted all knowledge of that list I am afraid. Regards, Sheelagh -- >Content-Transfer-Encoding: 7bit >X-Priority: 3 (Normal) >X-MSMail-Priority: Normal >Importance: Normal >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 >Date: Thu, 11 Jan 2001 10:43:05 +0100 >From: Gerhard Rentschler <[EMAIL PROTECTED]> >Subject: Putting ADSM config files in a separate directory >To: [EMAIL PROTECTED] > >Hi, >I'm about to move my ADSM Server to a new system. I thought it would be a >good idea to have the config files no longer in /usr/lpp/adsmserv/bin, but >in a separate directory, e.g. /adsm/config. >I know I have to use environment variable DSMSERV_DIR o point to the new >directory. Also, because dsmserv assumes a few files like nodelock to be in >the directory where dsmserv is started in I have to do a cd before the start >of dsmserv. > >Now I would like to have a comlete list o files which have to be moved to >the new directory. I know the following files: >dsmserv.opt >volhistory >devconfig >nodelock >dsmserv.dsk >Are there any others? What happens if I do a register license? Where does >this command look for the *.lic files? > >Another question in this context. I may have to run 2 different ADSM servers >on the same hardware. It may be helpful to run both servers not as root but >with different userids. This would allow to protect the servers file against >access by the other. Does anyone have experience with such a setup? > >Best regards >Gerhard >--- >Gerhard Rentschler email:[EMAIL PROTECTED] >Regional Computing Center tel. ++49/711/685 5806 >University of Stuttgart fax: ++49/711/682357 >Allmandring 30a >D 70550 >Stuttgart >Germany Sheelagh Treweek Oxford University Computing Services Email: [EMAIL PROTECTED] Phone: +44 (0)1865 273205 Fax:-273275