Record already locked by the job

Hello,

I have a trigger program doing the following:

- open physical file under commitment control (fully procedural with add)

- open logicals based on same file in input only

- search for record to update in the file using the logicals

- if no such record found, create a new record

- if such a record found, chain on the file using the physical and update
the said record

- close files

The commit (or rollback) is issued by the program that caused the trigger to
be called. Several calls to the trigger may happen within one commit cycle.

Unfortunately, a crash occurs on the update statement. The message is
"record already locked to job".

Is this happening because the program is called as part of a trigger? Is it
because I am closing and re-opening the files? Why is the crash detected by
the update and not the chain?

Best regards

Pascal

The opinions expressed within this email represent those of the
individual and not necessarily those of Gullivers Travel Associates (GTA).

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify postmaster@xxxxxxxxxxxxxx

Should you wish to use email as a form of communication, GTA are unable to
guarantee the security of email content outside of our own computer systems.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________