RE: RPG programs as external stored procedures...

I saw your post about commit boundaries. When I think of external stored procedures, I think of ODBC/JDBC callers. In those cases, I think a named activation group would be fine, since every call would have the same activation group. I guess I could see issues if the caller was ILE and you wanted to share a commit between the calling ILE and the external stored procedure. Although, that sounds incredibly rare to me, and I'm not even sure how that would even work.



-----Original Message-----
From: D*B [mailto:dieter.bender@xxxxxxxxxxxx]
Sent: Monday, February 19, 2018 8:31 AM
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Subject: RE: RPG programs as external stored procedures...

<Justin>
" Best practice is to let your user programms run in *CALLER (otherwise you would loose transaction safety!)"

Can you explain? That's the first time I've ever heard *CALLER being a best practice for programs. I can see it for service programs, but not programs.
</Justin>

... that's related to the discussion "RPG programms as external stored procedures" only. Maybe it would be more precise to say: Best practice is to let stored procedures run in the Activationgroup of its caller.

D*B