Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

How to solve the contention Issue (SQL code -911)

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging
View previous topic :: :: View next topic  
Author Message
Pons

New User


Joined: 25 May 2007
Posts: 61
Location: Coimbatore

PostPosted: Sun Jul 29, 2007 12:07 pm    Post subject: How to solve the contention Issue (SQL code -911)
Reply with quote

Hi,

In my project nearly 250 jobs are running daily night cycle. In that two jobs like J0B1 and JOB2 are running the same time.
Most of the time one of the job got abended due to contention with another job (SQL return code as -911)

I think it get abending due to Dead Lock, (REASON Code: 00C90088).
The both jobs using the same program with same plan.
In that program Update and Delete Query is there, so one of the job may hold the table with X (Exclusive Lock), that's what it getting abended.

What are the possible way to solve this issue.

I have some solutions,

1. Making dependency with one another (But it may delay my batch
cycle)
2. Changing the bind parameter (Lock Parameters)
they already using the following parameters,

Plan : PLAN1
Owner : USER007
Valdat : bind
Isolat : CS
Valid : Alt
Operat : Yes
Acq : use
Rel : dea
Bound : 2007-07-19

So i guess it is an perfect isolation parameters (CS). I don't think this will help to solve. i thought to change the Release parameter as commit but it will make more I/O operations.

3. Retry logic, suppose if it gave the return code as -911 i just release the locks and wait for some time and then call the same paragraph again in the program.

4. Otherwise if it gave the return code -911 then set the RC as 2049 and stop the program. In the JCL if the RC = 2049 then i try to execute the previous step again.

This are ways i am thinking to solve. But if any thing else is there to solve this issue please let mt know. because this is more high priority work in my project.

Please post your comments on my solutions and your ideas as soon as possible...
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Jul 29, 2007 9:21 pm    Post subject:
Reply with quote

Hello,

I'd suggest you make your first attempt by scheduling one job after the other. This should remove the abend. I believe that running a bit longer will be better than dealing with the abend.

Then, look at the processes and determine if the current locking method is needed or if the lockng order might be made more "friendly". This would require careful study and realistic testing.

If you look at the longest running of the jobs that are processed in your critical timeframe, there may be tuning that can be done with them and relieve some of the time pressure.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Job failing with USER = 4093 REASON C... Pradeepa S ABENDS & Debugging 1 Wed May 17, 2017 3:35 pm
No new posts Issue with NDM process to transmit ES... chetanambi All Other Mainframe Topics 6 Wed May 03, 2017 10:52 am
No new posts COBOL Code Parsers and Lineage Establ... balimanja COBOL Programming 2 Tue May 02, 2017 3:30 am
No new posts Cobol upgrade - source code missing f... gthmrj IBM Tools 1 Wed Apr 26, 2017 6:04 pm
No new posts DB2 utilities, contention or failure? sheersh DB2 2 Fri Apr 21, 2017 6:18 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us