×
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.
Mike, not enough info for me...
Some questions for your consideration:
1) Are the ILE RPG "F" spec files defined with the "COMMIT" key word?
2) Is the "external application" sending any commit/rollback parameter to the ILE RPG app?
3) Is the ILE RPG app doing any COMMIT or ROLLBK commands ?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, August 13, 2012 7:03 AM
To: Midrange Systems Technical Discussion
Subject: Mixing SQL and "native" IO in a single task
We have an application running on a Linux server using DB2 in our iSeries as its database. To interface to some of our other systems running on the iSeries we developed some stored procedures using ILE RPG to do some tasks for this external application. The RPG application that has been defined as a stored procedure has no SQL in it, it uses all "F" spec files to access the database and do WRITE/UPDATE commands. The external application has loop process that starts a commit boundary at the start of the loop, calls the stored procedure (the RPG application) for each read of the loop, and they does a commit at the end of the loop. Or a rollback if something fails in the middle of the loop. Does anyone know if the WRITES/UPDATES done from the RPG application are rolled back if the external application does a rollback or are the WRITES/UPDATES outside that commitment control since it is not done using SQL?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.