The RPG programm should act as a part of a transaction. That means, do some update via JDBC, call RPG, do some more updates via JDBC. Then do a commit or rollback that should affect all the updates from JDBC *AND* from the RPG program.Is there a possible way to do this?

sepp muegeli

One way I've found is:

1. Use commitment control from JDBC as usual ( auto-commit off, transaction isolation level != none ).
2. Use the keyword "COMMIT" in the file specification section in the RPG program.
3. Create the ILE-RPG program with activation group *CALLER

The stored procedure should now run under the commitment control of the calling JAVA program.