-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
James R Owen
Sent: Wednesday, January 23, 2008 1:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Upgrading TSM on an AIX server running multiple
TSM instances

Orville,
Can you clarify exactly what is the problem with multiple TSM service
instances running from a  shared dsmserv binary?  AFAIK, IBM/Tivoli does
not suggest to copy and run a separate executable for each TSM instance.
We have not seen any problems sharing the same executable among several
TSM instances.

Do you use this technique to allow production TSM services to continue
running while you upgrade the default installation TSM service?

Have you used this technique to safely run different maintenance levels
of TSM service simultaneously on the same AIX host?  If so, have you
experienced any problems doing this?  Did you ever need to copy
additional files to the running directories for the other TSM services?

I'm also looking for advice: how best to make an inoperative AUTOSRVR
entry in /etc/inittab?  We leave the tiny default TSM service in the
installation directory for upgrade processing, and never want it to
start up automatically, but the upgrade process recreates the entry if
it has been removed.
--
Jim.Owen AT Yale DOT Edu   (203.432.6693)

Orville Lantto wrote:
> The reason to have separate binaries for each instance is that the
process in AIX is tied to the binary file and holds it open.
>
> Orville L. Lantto
>
> ________________________________
>
> From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM
> Sent: Tue 1/22/2008 02:55
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Upgrading TSM on an AIX server running multiple 
> TSM instances
>
>
>
> Hi Orville!
> Thank you very much for you help!
> I read the technote (1052631) Richard pointed out. That doesn't 
> mention copying the dsmserv executable.
> Any reason why you choose to do so?
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Orville Lantto
> Sent: maandag 21 januari 2008 19:11
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Upgrading TSM on an AIX server running multiple TSM 
> instances
>
> You do not really need a full install of the TSM server code in both 
> locations.  Just a separate directory, separate config files, a 
> separate copy of the dsmserv binary and a the appropriate environment 
> to run it in.
>
> export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
> export DSMSERV_CONFIG=/usr/tivoli/tsm/server/instance2/dsmserv.opt
>
> Our upgrade procedure is to do the primary install and copy the 
> dsmserv binary to each instance directory.  Done.
>
>
> Orville L. Lantto
>
>
>
> Hi *SM-ers!
> I'm running two TSM server instances on an AIX host.
> Upgrading them from 5.3 to 5.4.0.0 works fine. I installed the 5.4.0.0

> code through smitty, changed the /usr/tivoli/tsm/server path to the 
> second instance and install the 5.4.0.0 code here, using the force 
> (-F) flag. Both instances are on 5.4.0.0 at that point.
> Now I'm trying the same trick for the upgrade to 5.4.2.0. Upgrading 
> the first instance works fine, but since this is an update, the -F 
> flage is not allowed by smitty during the upgrade of the second
instance:
>
> Force Apply Failures
> --------------------
> The following is a list of fileset updates.  Updates cannot be 
> specified from the command line when the force flag (-F) is used in 
> combination with the apply flag (-a).
>
> Maybe an AIX expert (and I now there are plenty of them on this list) 
> can help me with this one?
> Thank you VERY much in advance!!!!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>

I'm with Jim Owen above, I don't think you need completely separate
binaries, unless You WANT to keep the two at different versions.  But,
something inside me vaguely remembers reading about running two
different versions on 1 box and having problems.  

Anyway, all you have to do is make sure you run the dbupgrade for each
instance before you start up the server for all of them.  

See Ya'
Howard