IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

LTXNLOCK on IDMS DB


IBM Mainframe Forums -> IDMS/ADSO
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
rajasekar2810

New User


Joined: 22 Apr 2008
Posts: 6
Location: india

PostPosted: Mon Nov 03, 2008 11:07 am
Reply with quote

Hi

Can any one tell me about what is LTXNLOCK concept in IDMS DB.
Back to top
View user's profile Send private message
nelson.pandian

Active User


Joined: 09 Apr 2008
Posts: 133
Location: Phoenix, AZ

PostPosted: Sun Nov 16, 2008 12:15 am
Reply with quote

Hallo

Quote:
Can any one tell me about what is LTXNLOCK concept in IDMS DB.

From were did you find this LTXNLOCK?????
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10801
Location: italy

PostPosted: Sun Nov 16, 2008 12:49 am
Reply with quote

maybe in a deadlock message ??

Code:
DC001000 T:20425 ADS2 P:DBCRUPD C:DEAD WAITING ON R:LTXNLOCK 00000008 0A60730D
DC001001 TXNID:000369476 RUID:000369476 RUNAME:DBCRUPD SSC:DBCRSSC1
Back to top
View user's profile Send private message
rajasekar2810

New User


Joined: 22 Apr 2008
Posts: 6
Location: india

PostPosted: Sun Nov 16, 2008 10:53 am
Reply with quote

Yes exactly in the IDMS logs I find this out.
Let me share my findings;

This situation happens when a record DB key is dead locked by some transaction and that record is requested by some other transactions and the TASK is getting in to loop.This leads to 0069 error.
Do you have any more idea on this.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


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

PostPosted: Sun Nov 16, 2008 11:18 am
Reply with quote

Hello,

Quote:
happens when a record DB key is dead locked by some transaction
Possibly you mean "locked" rather than "dead locked". One transacton might lock something, but not cause a deadlock.

A deadlock is typically caused when 2 different processes read 2 different tables in not the same order. Pg1 reads TbA key1 with lock. Pg2 reads TbB key2 with lock. To this point - no problem. Now, Pg2 needs to read TbA key1 with lock - it cannot because of the lock issued by PgA. It will wait until the lock is freed. What causes the deadlock is while Pg2 is waiting, PgA needs to read TbB key2 with lock. At this point the deadlock (sometimes called a "fatal embrace") is detected and the request causing the deadlock is terminted with an error.

The way to prevent this is to make sure the code locks rows in multiple tables in the same order or make sure the programs do not run concurrently.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> IDMS/ADSO

 


Similar Topics
Topic Forum Replies
No new posts IDMS record copybook IDMS/ADSO 3
No new posts Can records in IMS/DB be related usin... IMS DB/DC 2
No new posts IDMS DC027007 T58 TASK:ADS2 PROG:ADSO... IDMS/ADSO 2
No new posts IDMS/DC-COBOL program - SNAP error wh... IDMS/ADSO 5
No new posts ADS 3270 Batch simulator for IDMS rel... IDMS/ADSO 1
Search our Forums:

Back to Top