|
Hi Crispin,
Sorry for any confusion - as per the end of my note, I was not
commenting on the original posters question or whether or not RPG
blocking was causing the problem (although I would be amazed if you
could specify BLOCK(*YES) for a file with a trigger).
I simply wanted to clarify that RPG has it's own blocking mechanism.
Regards
Paul Tuohy
ComCon
www.comconadvisor.com
www.systemideveloper.com
Crispin Bates wrote:
Paul,--
How does my RPG Program know which record(s) failed because a Trigger
stopped them from being written, when a block of 100 [for the sake of the
question] records is passed from the RPG Buffer to the DBMS?
How should I code to handle the individual records that failed, when the
failure from the trigger does not happen until the block is written?
Am I completely missing something here? I thought the DBMS made the trigger
calls, not the RPG runtime.
Thanks.
----- Original Message ----- From: "Paul Tuohy" <tuohyp@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, December 03, 2010 12:09 PM
Subject: Re: FILE TRIGGER
Duane,
Ken is referring to blocking in RPG - and this is something RPG can do
all by itself, especially if a file is open for output.
i.e. RPG can block a number of records in a buffer before handing them
over to the DBMS for processing.
Check out the BLOCK keyword for F specs for details.
BTW - not sure if this is the issue with the OPs trigger delay - just to
clarify what Ken was referring to.
Regards
Paul Tuohy
ComCon
www.comconadvisor.com
www.systemideveloper.com
This is the RPG programming on the IBM i / System i (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 mailing list archive is Copyright 1997-2025 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.