Hi
This error points to a DB2 environment problem. Double check your
environment variables. Follow through any links and make sure they actually
point to real files.
My settings look like this:
DSMI_CONFIG=/db2/db2t20/sqllib/adsm/dsm.opt
DSMI_LOG=/db2/db2t20/errors
Hi
We experience the SAP problem except I don't believe TSM 'holds' the drive.
DB2 will read backup header from tape
DB2 then creates containers as required.
While the containers are being created, TSM waits for the client to return.
The tape is unmounted after a timeout period.
When containers
Hi Lindy
I guess your using the SAP supplied db2uext2. I suggest you contact SAP for
assistance.
Oss note 104019 provides some good information regarding the return codes
Cheers
Troy Tudor
-Original Message-
From: Crawford, Lindy [mailto:[EMAIL PROTECTED]
Sent: 21 July 2003 12:14
To:
Hi Bill
With Collocation on, we had one small problem with the DB2 API.
We backup our DB2 databases with multiple sessions. If the DB2 backup is
directed to tape, the backup can only occur single session, because the
second sessions sits waiting on the tape being used by the first session.
I understood the only options for collocation were on or off
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]
Sent: 30 July 2003 16:41
To: [EMAIL PROTECTED]
Subject: Re: Collocation from nocollocation
With Collocation on, we had one small problem with the DB2 API.
What
Hi John
It works (on AIX anyway), you just need to take extra special care that your
DSMI environment variables are set correctly
eg
DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt
DSMI_LOG=/db2/GD1/errors
DSMI_DIR=/usr/tivoli/tsm/client/api/bin64
You also need to check the soft link to
