Re: sql and commitment control

I think the issue is the ATOMIC .... I believe that starts a commit
definition implicitly. As there's no way for the DB to do guarantee
consistency otherwise.

try changing ATOMIC to NOT ATOMIC...

Or have your PHP function issue a COMMIT after the call and before it
disconnects.

Charles



On Wed, Mar 14, 2018 at 1:09 PM, Steve Richter <stephenrichter@xxxxxxxxx>
wrote:

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) )
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD