Hello Richard,

  gererally yes, it's that easy, but some more steps:

- on the old server do a "db2ilist" and for each instance reported do a 
"db2icrt <instancename>" on the new server.

- be sure to have the same TSM-Server levels on old and new server, otherwise
you have to perform a "db2iupdt <instancename>" for each instance. Naturally,
you can only upgrade, and the instance has to be mounted when performing the
command.

To find the full paths to the programs mentioned is left as an exercise for
the reader.

-- 
Michael Prix On Fr, 2016-05-06 at 16:55 +0000, Rhodes, Richard L. wrote:
> Hello,
> 
> Current:  TSM v6.3.5 on AIX 6100-09
> New:      TSM v6.3.5 on AIX 7something
> 
> Well, it's time to rollover our TSM AIX servers.  We're purchases new
> pSeries chassis that are getting lpar'ed up to replace the existing systems.
> 
> New lpars will be AIX v7.
> All storage is SAN based on either IBM or EMC storage arrays.
> All TSM/DB2 pieces/parts are on separate luns from AIX/rootvg.
>   In rootvg lun:
>      Whatever TSM/DB2 puts in /opt, /var/, /usr
>      (tsm client stuff is in here)
>   In non-rootvg luns:
>      db2 vols
>      db2 log vols (active/mirror/archive)
>      db2 sqllib dir
>      tsm stuff (dsmserv.opt, volhist, etc)
>      tsm disk pools
> 
> We would like to
>   - setup new/clean lpars with AIX v7 on the new chassis
>   - install TSM/DB2 binaries
>   - SWING THE non-rootvg luns from the old lpar to the new lpar
>   - bring up TSM . . .
> Is it really that easy????
> 
> 
> PROBLEM - I can't find anything on how to swing a DB2 database from one AIX
> lpar to a new/clean lpar.  We're a Oracle shop - no one knows DB2 around
> here.
> 
> 
> Q)  Has anyone done a TSM storage swing like this?
> 
> 
> We are planning a TSM v7.1 upgrade.  We may need to do this to get to AIX
> v7.  I have to check this out.
> 
> Thanks
> 
> Rick
> 
> 
> 
> 
> 
> -----------------------------------------
> 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.