sql and commitment control

I code an SQL procedure that runs 3 steps:
- create schema
- create table in schema
- insert data into table in schema

I run STRSQL. Then CALL procedure. Check that the data exists in the
table. Then I sign off the job. Sign back on and the schema and table are
gone.

Is this some sort of commitment control requirement?

Is there some way on the IBM i that I can tell the OS to let me use SQL
without journaling and commitment control?

Here is the SQL procedure:

CREATE OR REPLACE procedure reptestp1
( )
language sql
MODIFIES SQL DATA
SET OPTION COMMIT = *NONE
BEGIN atomic

declare vSqlCode decimal(5,0) DEFAULT 0 ;
declare sqlCode int DEFAULT 0 ;

create schema steve ;
create table steve/srcdata (
srcseq decimal(6,2),
srcdta char(132),
srcdat decIMAL(6,0)) ;

insert into steve/srcdata ( srcseq, srcdta, srcdat )
select a.srcseq, a.srcdta, a.srcdat
from qrpglesrc a ;

END

and I create the procedure:

RUNSQLSTM SRCFILE(QRPGLESRC) SRCMBR(REPTESTP1) COMMIT(*NONE)
( same results with COMMIT(*ALL) )