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
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.