Am 16.05.2022 um 18:39 schrieb Brian Parkins <goodprophet.bp@xxxxxxxxx>:
This is a wild suggestion that will probably be of no help at all.
Would a (physical) file trigger offer a solution? (Whether External or SQL.) You could use CHGPFTRG or ALTER TRIGGER to enable/disable as required. The Trigger Buffer would contain the RRN of the successful insert/after.
On 16/05/2022 17:03, Greg Wilburn wrote:
X2. If anyone knows how to get the RRN for certain, that would solve my issue.
The legacy ERP does not have ANYTHING journaled... the transaction files do not have a unique key on the PF or LF.
I understand what everyone is saying about journaling. No convincing needed. But I cannot simply "turn it on" and risk messages all over the given all the other programs that touch this file.
I'm also concerned about service program procedures (in the same module even) that have COMMIT=*NONE. I'm not sure how to handle that.
If I was certain I could turn journaling on for this file, without creating a host of other issues, I would.
Open to suggestions
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.