db2 /tsm api issue

[tsm_dude]

Hi TSM`ers,

I have prob with db2 backups using tsm/api on linux
Client Version 5, Release 3, Level 4.0
Linux lditm01 2.6.16.60-0.21-bigsmp #1 SMP Tue May 6 12:41:02 UTC 2008 i686 i686 i386 GNU/Linux

I usually specify DSMI_CONFIG=/somewhere unique for each instance
Whic is the normal way. But the backup wont work unless I copy the DSM_CONFIG file to the api/bin directory.
It seems hard-coded to only look there.
The other 2 variables work, with the log dir being custom area etc.
It means I can only have 1 instance,
any ideas, I have earlier versions of TSM without prob on same platform.

 

[cheffern]

hi -

in my case for setup, I want the file to go to DSMI_DIR (api/bin) -
mainly like you said, because it seems hard-coded to look there anyway...

(I did notice a change from 5.2 to 5.3 & 5.4 also, if that helps)

what I normally do is setup the DB2 users' profile as follows (.csh example):

setenv DSM_DIR /opt/tivoli/tsm/client/ba/bin
setenv DSM_CONFIG /db2/db2sid/sqllib/tsm/dsm.opt
setenv DSM_LOG /db2/db2sid/sqllib/tsm
setenv DSMI_DIR /opt/tivoli/tsm/client/api/bin
setenv DSMI_CONFIG /db2/db2sid/sqllib/tsm/dsm.opt
setenv DSMI_LOG /db2/db2sid/sqllib/tsm

then in addition, this in the root users' profile (.bash example):

DSMI_DIR=/opt/tivoli/tsm/client/api/bin; export DSMI_DIR
DSMI_CONFIG=$DSMI_DIR/dsm.opt; export DSMI_CONFIG
DSMI_LOG=/opt/tivoli/tsm/client/api/log; export DSMI_LOG

then when you log in as the DB2 user, things should be setup already to point to the right place. you do have to 'override' the filesystem backup setup for DSM*

I do (in some cases - not all - sometimes things magically work without this) link the dsm.opt file back to the api/bin dir.
but - do you have multiple DB2 instances under the same user?
that is where things can really get hairy...

hope that helps -
-Chef.

 

[tsm_dude]

Thanks for your ideas but the point here is the variable is not working, I dont need it to if I only have 1 instance but I have multiple.
So I need to do something dodgy like link/copy opt files etc in the backup script.
I never had this issue on AIX, and setup many muliple instance db2s.
Since linux is dodgy freeware rubish I guess a dodgy hack will have to do.
The other point is i have another linux box that works, and it has a lower version of tsm, I guess I could downgrade to that level also.
Thx