check this also ..very close to your problem 




 

IC31884: V4.2.1 SERVER CORE DUMPING, ANR7837S ON LOCKCYCLE02 
[IMAGE]





 





Abstract 




 

V4.2.1 SERVER CORE DUMPING, ANR7837S ON LOCKCYCLE02 
[IMAGE]




Error description
TSM Server V4.2.1 core dumps with ANR7837S Internal error 
LOCKCYCLE02 detected. The error messages are in the dsmserv.err 
Trace back in dsmserv.err: 
ANR7838S Server operation terminated. 
ANR7837S Internal error LOCKCYCLE02 detected. 
0x100085A4 pkLogicAbort 
0x100303F0 CheckLockCycles 
0x100324C0 TmFindDeadlock 
0x100322A4 TmDeadlockDetector 
0x10006DB4 StartThread 
0xD00081FC _pthread_body 
ANR7833S Server thread 1 terminated in response to program abort
ANR7833S Server thread 2 terminated in response to program abort
............. 
The LOCKCYCLE02 indicates that the problem is related to 
transactions between the storage agent and TSM server. TSM 
set a waiter flag in the lock request. Situations can occur 
where the lock request is aborted. The abort causes a 
LOCKCYCLE02 problem because the deadlock detector 
woke up and went looking for waiters. Since there is a small 
window between when the abort code signals the lock waiter 
(because the mutex is released to allow the receiver to 
respond), this allowed the deadlock detector to start looking 
for deadlocks. Since the request had been satisfied by being 
aborted, there were no locks being waited on (but the flag was 
still set). Hence, TSM aborted because there was a waiter not 
waiting on anything. 

Local fix
Set the RESOURCETIMEOUT value in dsmserv.opt to a higher 
timeout value. (See the administrator reference for more 
information.) Higher timeout value should allow the locke waiter
flag to clear. 
. 
Apply fixtest 4.2.1.6 to resolve this problem. 

Problem summary
****************************************************************
* USERS AFFECTED: This effect users of Tivoli Storage *
* Manager version 4.2.1 and above on AIX, *
* NT, SUN, HP and MVS. *
****************************************************************
* PROBLEM DESCRIPTION: The TSM server aborts with the *
* following *
* abort codes: TMLOCK011, TXNLOCK16 and *
* LOCKCYCLE02 *
****************************************************************
* RECOMMENDATION: Install PTF or PATCH when available. *
****************************************************************
The problem is that the a lock request is aborted by the 
resource manager. The resource manager does not remove the 
waiter from the list of waiters. When the transaction is 
aborted (TXNLOCK16), deadlock detector looks for a deadlock 
(LOCKCYCLE02) or a the next 
waiter is being granted the lock (TMLOCK011), the server abends.

Problem conclusion
This problem has been corrected. 


Circumvention
The current workaround this problem is to prevent the resource 
manager from aborting lock requests. This can be done by 
setting the RESOURCETIMEOUT in the DSMSERV.OPT file to a 
higher value like 100. The option applies to all TSM servers 
and storage agents even though it is documented only for 
Windows. 




 


APAR/Component information: 
APAR number: 
IC31884 
Component name: 
TSM AIX SERVER 
Component number: 
5698TSMAX 
Reported release: 
420 
Fixed component: 
5698TSMAX 
Fixed component name: 
TSM AIX SERVER 





Status information: 
[IMAGE]
Status: 
CLOSED PER 
Close date: 
2001-10-18 
Last changed: 
2001-10-29