SQL has been a major game changer in the RPG programming world.
I first played with SQL back the golden days of RPG3 and RPG400 when we were all wrapped up in using Commitment Control. Journalling files and making changes to data in our RPGSQL programs before issuing a COMMIT or ROLLBACK was exciting and new. Roll forward a few years and database access times have massively increased and the entire concept of commitment control is not something we focus on so much in the RPG programming world.
Because of this history, in modern RPG4 SQL programs, we still have to tell the program not to use commitment if we don't want to use it. This also means you can use embedded SQL in RPG4 programs without journaling your files.
COMPILE TIME PARAMETER
The easiest way is to enter the create parameter of COMMIT(*NONE) thing so it turns it off after the first commit without the isolation level nonsense.