× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Are you saying that your trigger program does I/O to the file that the trigger 
program is attached to?

You can't do that.

What are you trying to accomplish?

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of
> pascal.jacquemain@xxxxxxxxxxxxxx
> Sent: Wednesday, May 25, 2005 5:16 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: 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 
> ______________________________________________________________________
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.