Does anyone have experience resolving AKCS abends (timeout)? We were getting them quite infrequently, then suddenly a lot after a DB2 index change. We since reversed out the index changes, but the abends continue!
Vivekster 270002S93P3 Posts
Re: CICS-TX AKCS abends2010-09-13T06:39:42ZThis is the accepted answer. This is the accepted answer.jentek,
AKCS abend is a deadlock timeout abend that is specified in seconds. The deadlock may resolve itself, so try increasing the DeadLockTimeout attribute ( in the TD Stanza ) to the maximum possible value.
Can you also attach the console and symrecs file of that region?
lakshuraghav 0600009XU07 Posts
Re: CICS-TX AKCS abends2010-09-13T07:14:25ZThis is the accepted answer. This is the accepted answer.Hi Steve,
I see below explanation about AKCS abend in the documentation. Have you checked the user response already? Have you checked whether any DB2 specific errors are recorded in db2 logs? We sometimes see the issue when a DB2 SQL query takes a long time to respond.Can you check if you are seeing any transaction spending long time on the database side.
CICS detected a deadlock timeout condition. This condition may occur within any transaction defined with a non-zero DeadLockTimeout attribute in the Transaction Definitions (TD). This condition can also be raised by DB2 when it detects a deadlock or timeout on its resources. Deadlock timeout occurs when a transaction waits for longer than the time specified in DeadLockTimeout. (Note: the DeadLockTimeout attribute is specified in seconds.)
CICS abnormally terminates the transaction but does not produce a transaction dump.
You should re-run the transaction because the situation causing the transaction to wait, may well clear itself. If this does not solve the problem, try increasing the value of the DeadlockTimeout attribute to the maximum acceptable value. If this does not solve the problem, please read Problem Determination. If SQLCODE -913 is reported in the symrecs file, refer to the relevant DB2 Problem Determination Guide for further assistance.
SystemAdmin 110000D4XK308 Posts
Re: CICS-TX AKCS abends2010-09-13T07:37:34ZThis is the accepted answer. This is the accepted answer.>> We were getting them quite infrequently, then suddenly a lot after a DB2 index change.
Can you elaborate on this change ? Are you using DB2 as filemanager ?
Re: CICS-TX AKCS abends2010-09-14T21:07:59ZThis is the accepted answer. This is the accepted answer.
- lakshuraghav 0600009XU0
We restarted DB2 to reset the deadlock and timeout counters. During the CICS sessions we saw AKCS abends BUT no increase in the DB2 counters, therefore can we assume it is NOT a DB2 issue?
We do have some long SQL transactions, but we had those before we got a big increase in AKCS abends.
lakshuraghav 0600009XU07 Posts
Re: CICS-TX AKCS abends2010-09-21T05:57:40ZThis is the accepted answer. This is the accepted answer.Hi Steve,
AKCS is very generic abend.AKCS abends are common when DeadlockTimeout is set and multiple transactions contend for a same resource.In this case, I suspect the DB2 to be the issue as the problem started appearing in your case after changing the indices of DB2 table. But AKCS can happen irrespective any kind of resource contention such as RM,TDQ,TSQ,ENQ etc. Probably , you can quickly check by enabling Monitoring facility in TXSeries to check if there are any waits on the cics side which is resulting in AKCS abend. With the Monitoring facility, you can identify if the problem is due to CICS resource or the DB2/external resource.