Re: is there a way to let the record lock (R I D C) error stay at the program that do the CHAIN

There are two problems here.

1)  Some operation has a lock on a file, probably longer than is needed.
2)  Program B does not properly handle a chain with a lock.

First, find out who has the lock.  Was it your new program?  If so, stop 
locking the record.  If it was elsewhere, either fix that program to stop 
locking the record so long or shoot the operator that left the locked 
record on the screen while they went out to a meeting.

Secondly, Change program B to handle the lock.  You may override the file 
with a much shorter wait time.  Instead of CHAIN use CHAIN (E).  Test the 
status.  If it was because of a record lock, use the file information data 
structure and/or some api's to determine who has the lock and report this 
so that corrective action may be taken, (see First section above).

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)