Receiving SQLCODE -911 for CICS-DB2 module

Ask question on - DataBase Concepts, IBM Mainframe DB2, DB2/UDB, DB2 Tools, SQL , DB2 programming with languages like COBOL, PL1.

Moderators: Kalicharan, Moderator Group

Post Reply
Posts: 1
Joined: Sun Oct 26, 2014 1:52 pm

Receiving SQLCODE -911 for CICS-DB2 module

Post by gunjansoni4983 » Sun Oct 26, 2014 2:04 pm


I am having a CICS-DB2 module which is triggered via MQ through a transaction. Module first searches the row in database with some criteria and then do Insert if the row does not exist or update if the row exists. The module is doing this Insert/Update for 816 rows sequentially in one call.

When multiple requests(Multiple transactions triggered through CICS at the same time) with 816 rows in each transaction request then for 2 requests in parallel the program is working fine but for the other requests it throws SQLCODE -911 with reason code C90088(Deadlock).

There is only one DB2 table in the module where update/Inserts are performed and i am using intermediate Syncpoints after every 50 Inserts in database to release the lock in DB2. Even with this the program is giving -911 for other requests in parallel. Lockrule on tablespace is set to 'R' (Row level) so it should not acquire lock.

Can someone please suggest some resolution for this.

User avatar
Posts: 981
Joined: Mon Oct 02, 2006 8:31 pm

Post by dbzTHEdinosauer » Mon Oct 27, 2014 7:39 pm

are you also performing a syncpoint after the updates?
the inserts will not give you a deadlock, but the updates in one task could cause a dealock for the updates in a second.

have you considered running only one task?
have you considered running this process in batch. what you are describing is 'batch work'.
have a batch started task continually read the mq queue, and process what it finds.
you can have set a delay on the mq read to wait for time before returning a no-message response.
by using the delay, you have a permanent running job (that should run as a started task), that drains the queue. by running in batch, you do away with the added overhead from cics to start and manage a task evertime some message hits the queue.
since it is db2, there is no need to run this process in cics.
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

Post Reply


Free tutorials from mainframegurukul
  • JCL Tutorial
    Covers all important JCL concepts.
  • Cobol Tutorial
    This tutorials covers all Cobol Topics from STRING to COMP-3.
  • DB2 Tutorial
    DB2 Tutorial focuses on DB2 COBOL Programming.
  • SORT Tutorial
    This Tutorial covers all important aspects of DFSORT with examples
  • CICS Tutorial
    This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Mainframe Interview questions

Other References
Mainframe Tools and others