Re: RPG programs as external stored procedures... -- RPG400-L

× 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.

<Justin>
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.
</Justin>

... a stored procedure doesn't know, where it is called from (and it
shouldn't care about). A named ACTGRP could work in server mode (for example
called from ODBC/JDBC) as expected (I'm a little bit unsure, if the commit
would have to be wrapped in a stored procedure), but it would behave very
diffrent in the AS/400 native environment (pending record locks, changes
could disappear at end of ACTGRP...). Sharing a commit between a native
programm and a stored procedure is working like any other commit: Running
the slave in *caller, the commit will free all resources and make the
changes permanent, Running the slave in a diffrent ACTGRP, the commit will
only work for the ACTGRP, where it was issued.

D*B

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.