When we recently started with multiple instances (on aix),, I implemented
it by creating
a directory for the each instance that contains the instance specific
files.

    /tsmdata/<tsminstance>/config

I then created a soft link on the dsmserv binary to dsmserv_<tsminstance>
in the
normal tsm bin dir.  This way a "ps -ef | grep dsm" shows the symlink name.

In the config dir are scripts to start/stop the instance.  Here is the
start script
for our instance "TSM1".    The actual tsm log and db are on raw volumes.
The dsmserv.opt and instance is setup to put volhist, dev config, accnt
log,
etc, etc in the same directory.

fe-bkup3:/tsmdata/tsm1/config==>cat rc.start_tsm1.ksh
#!/bin/ksh
# Set the language....
#
export LANG=en_US
#
# Max out size of data area
#
ulimit -d unlimited
#
# Allow the server to pack shared memory segments
#
export EXTSHM=ON
# setup to run tsmlm2
cd /tsmdata/tsm1/config
export PATH=${PATH}:/usr/tivoli/tsm/server/bin
export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
export DSMSERV_CONFIG=/tsmdata/tsm1/config/dsmserv.opt
export DSMSERV_ACCOUNTING_DIR=/tsmdata/tsm1/config
#
# Start the server in quiet mode.
#
print "$(date '+%D %T') Starting Tivoli Storage Manager Server"
nohup dsmserv_tsm1    quiet &


fe-bkup3:/tsmdata/tsm1/config==>cat kill_tsm1.ksh
#!/bin/ksh
kill $(cat /tsmdata/tsm1/config/adsmserv.lock | awk '{print $4}')


fe-bkup3:/tsmdata/tsm1/config==>cat kill9_tsm1.ksh
#!/bin/ksh
kill -9 $(cat /tsmdata/tsm1/config/adsmserv.lock | awk '{print $4}')




                                                                           
             "Bernaldo de                                                  
             Quiros, Iban 1"                                               
             <iban.bernaldodeq                                          To 
             uiros AT SUN DOT COM>            ADSM-L AT VM.MARIST DOT EDU       
         
             Sent by: "ADSM:                                            cc 
             Dist Stor                                                     
             Manager"                                              Subject 
             <[email protected]         Second TSM Instance                 
             .EDU>                                                         
                                                                           
                                                                           
             11/28/2006 06:03                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
             "ADSM: Dist Stor                                              
                 Manager"                                                  
             <[email protected]                                             
                   .EDU>                                                   
                                                                           
                                                                           




Hi all,

I am planning to create a second instance in my TSM on Solaris 9. I have
read on the quick reference guide, that I have to export the following
environment variables:
DSMSERV_DIR
DSMSERV_CONFIG

To the new path of my second instance.

The change will affect to my first TSM instance...¿?

What does these environment variables do ¿?

Thanks in advance,

Regards,
Ibán.



-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.