I have found that most all of the "cannot find, or cannot read" I run into are 
ultimately permission related, especially with DB2.


-Rick 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Karel Bos
Sent: Thursday, February 02, 2017 6:43 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] DB2 back-up issues on Windows

Hi,



Every day I have to restart DB2 (sometimes multiple times) due to backups stop 
working. The DB2 database is doing log file and normal backups to TSM and the 
backups stop working after the following couple of errors:



31.01.2017 10:48:04 instrStart: Unable to get write file lock or report file 
handler.

31.01.2017 10:48:16 ANS1035S Options file 'D:\TSM\client\dsm.opt' could not be 
found, or it cannot be read.

31.01.2017 10:48:31 instrStop: Unable to get write file lock or report file 
handler.



My idea is this has nothing to do with the dsm.opt itself but with the 
dsmopt.lock file and the handler stops working. This leads me to believe it has 
something to do with:



https://urldefense.proofpoint.com/v2/url?u=http-3A__www-2D01.ibm.com_support_docview.wss-3Fuid-3Dswg21646969&d=DwICAg&c=AzgFQeXLLKhxSQaoFCm29A&r=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxw&m=NYVXmJstnwXOL1D-oICuOCJtMLO01UY9BP_P6Hazv40&s=ppbHkreaOeHpE_RvUd4NGYQUx08O5dTlezN0U_pVems&e=
 



but ofc its al directed to Unix as although IBM supports their products on 
Windows their support and documentation are mostly based on AIX installations.



Also note, this symptom should be fixed in TSM V7.1.4 but this environment is 
running BAclient V7.1.6.2 on Windows 2008R2 64b. Support ticket with IBM has 
been opened but sofar they are not really helpfull.



I wonder if someone is running into the same issues and if its only on windows 
or also still on AIX (as I have multiple AIX servers running DB2 without the 
option to restart them everytime the backup stops working which are about to be 
upgraded to this TSM client version).



Kind regards,



Karel