×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
... create procedure creates a programm with embedded SQL, running in ACTGRP
*caller. specifying a commit option <> *NONE results in starting commit for
this ACTGRP, if not already started. If you don't commit in your procedure,
it is running as commit slave and everybody calling this procedure is
reponsable for commit/rollback. If this is not working in your case, there
are two possibilities:
- your description what's happening is not what is really happening
- you have a software defect!!!
a minimalized example:
CREATE or replace PROCEDURE dsternb1.fool()
LANGUAGE SQL
MODIFIES SQL DATA
set option commit = *chg
BEGIN atomic
create table dsternb1.fool as (
select * from covelenz) with data;
END
is working as it should, regardless wether your STRSQL session is running
commit *NONE or any other setting, the end of job will send a rollback if
there was not issued commit and the table will disappear. If you send a
commit before ending from inside STRSQL or coming back to commandline, the
table will persist.
D*B
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: commit inserts made in SQL procedure, (continued)
This mailing list archive is Copyright 1997-2024 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.
midrange.com
