Please see the redbook "Backing up DB2 using TSM" SG24-6247. This manual
recommends NOT setting the TSM-related configuration parameters in each
database. This redbook has all the steps you need to perform to configure
DB2 and the API client for backups. You also can use the same DSM.OPT file,
but if you have the same database name in 2 different instances, you run
into conflicts. I created a nodename and DSM.OPT file for each instance I
want to backup.

I created a /tsm directory in the instance home directory for all the files,
and in the {$INSTHOME}/sqllib/userprofile file I put all the export DSMI*
variables. This is outlined in the redbook.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Gyula Bereczky
Sent: Tuesday, March 11, 2003 12:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: DB2


On Tue, Mar 11, 2003 at 11:03:57AM -0600, Brenda Collins wrote:
> An issue he has come across is trying to run backups and the db2adutl
utility under a 'gloabl' id.  Is this possible?

Make sure global has the authority to backup and restore the databases.
It needs to be sysadm, sysctrl or sysmaint.

> When TSM is configured on a client, does it have to be configured
separately for every database instance?

As DB2 uses the API client, you need to configure only one opt file as
long as you want to use only one TSM server.
However you have to set the TSM related DB2 parameters in each database
configuration. (db2 get db cfg for <database>)

For DB2 setup, please see the DB2 Administration Guide, for db2adutl, the
Command Reference.
--
       bx
"Seize the day - I heard him say - life will not always be this way,
Look around, hear the sounds, cherish your life while you're still around."