Managed to fix the problem.  We initially installed this system at TSM
client API 4.1.2.  However we were advised to backlevel to a previous
version of the API.
Apparently 4.1.2 was known not to work.

We thought we had correctly deinstalled the TSM client but a file
c:\winnt\system32\adsmv3.dll was left lying around. When we installed an
earlier version of the
TSM API this DLL did not get overwritten.  Even though the whole client was
at 4.1.0, just this one file was at 4.1.2.

We manually deleted this file and reinstalled the TSM client.

DB2 backups now working!!!!!!!

Richard.


Richard Bates
Storage Specialist
ITS - SB - Enterprise Consultancy Services
==========================================
Voice : +44  (0) 1926 462298          (Hicom : 662298)
IBM Mobile: +44 (0)775 386 8289 (Mobex : 270798)
richard_bates AT uk.ibm DOT com
---------------------- Forwarded by Richard Bates/UK/IBM on 22-02-2001
22:07 ---------------------------
22:07 ---------------------------

Richard Bates
22-02-2001 00:02

To:   ADSM-L AT vm.marist DOT edu
cc:
From: Richard Bates/UK/IBM@ibmgb
Subject:  db2 backup to tsm fails


This is a DB2/TSM backup question (and I have appended to those newsgroups
too).  Someone out there must have got this working.

We are a site running DB2 UDB v7 fixpack2 on NT v4 (service pack 5).
We are also running TSM v4.1.1 (client and api) and v4.1.2 (server) on
the same NT server.  We are trying to achieve a backup from DB2 through
the API to TSM.

We have setup all the necessary DSMI_* NT system variables via control
panel--> system.  We then rebooted so that they would take effect.

DSMI_CONFIG=c\:progra~1\tivoli\tsm\api\dsm.opt
DSMI_DIR=c\:progra~1\tivoli\tsm\api
DSMI_LOG=c\:progra~1\tivoli\tsm\api

We have configured the dsm.opt so that "passwordaccess generate" is
specified.  Therefore we have not configured the db2 variables TSM_* on
the database we are trying to backup.  We have set the password (in the
registry) with dsmapipw.  A "db2adutl query" starts a session with the
TSM server and returns no objects backed up (as expected).

I don't think there is anything else we have missed out.

When we start the "db2 backup db <dbname> use tsm" command we
immediately get a Dr Watson  message on db2syscs.exe.  A backup session
does not start with the TSM server.  Has anyone seen this before?  We
have tried all sorts of TSM clients with no joy.  This is currently with
the DB2 developers in Toronto.

Has anyone done this before on these specific versions?

Richard Bates
Storage Specialist
ITS - SB - Enterprise Consultancy Services
==========================================
Voice : +44  (0) 1926 462298          (Hicom : 662298)
IBM Mobile: +44 (0)775 386 8289 (Mobex : 270798)
richard_bates AT uk.ibm DOT com