×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




created the sql procedure in my current library.

thanks for the answer.


On Wed, Mar 14, 2018 at 3:18 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Steve,

STRSQL
F13=Services
1. Change session attributes
Commitment control

Or execute it in RUNSQLSTM COMMIT(*NONE)
Or RUNSQL SQL(...) COMMIT(*NONE)

Dumb question of the day: You weren't building this in the QTEMP schema,
were you?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Steve Richter <stephenrichter@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/14/2018 03:09 PM
Subject: sql and commitment control
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



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


--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.