Results 1 to 2 of 2
  1. #1
    Join Date
    Feb 2004

    Unanswered: How to avoid Database contention in COBOL-DB2 Programs

    I am getting a return code og -911 and -913 when two different batch application executing as IMS-DB2 program. I am commiting the DB after about 1000 transactions. Is there any way out of this problem.

    I could think of using the same IEFRDER file for both the applications. Is this a good practice?


  2. #2
    Join Date
    May 2003
    Try setting the isolation level to CS in the bind options. Also try locksize PAGE instead of locksize ANY on the tablespace.

    If that does not work, more detailed analysis of the problem needs to be done to see whether it is a timeout or deadlock. If it is a deadlock, then it might be possible to change the order of SQL statements (so that both prgrams access the tables in the same order) to prevent that from occuring.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts