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.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
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.