MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2008

Re: SQL in REXX problem



fixed

The WITH isolation level clause is for the DML; in this case, the SELECT. However the WITH isolation-clause may not even be valid for the AS select-statement; not noted as one of the prohibited clauses however. Presumably it would be moot, as the CREATE TABLE would still be under the default isolation of *CHANGE; and the subquery inserted data as well.? There is no WITH isolation level clause for the DDL; in this case, the CREATE TABLE. You will want to use the SET OPTION or SET TRANSACTION to set the isolation level for the REXX SQL.

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/db2/rbafzmstisol.htm
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/db2/rbafzmsthctabl.htm

Regards, Chuck

David FOXWELL wrote:

I've been using a REXX procedure for updating with SQL by simply
passing the SQL that I want to execute. Now I want to use it to
execute CREATE TABLE, but I get the message

Table REFER00001 de QTEMP incorrecte pour cette opération.

I think there's something up with the commitment control. I usually
just put with NC on the end but here there's already _With Data_ in
my command.

What's the syntax for using SET in the REXX procedure ?


Here's my call to REXX :

STRREXPRC SRCMBR(EXECSQL) SRCFILE(QREXSRC)
PARM('create table mytable as
( SELECT * from myothertable ) with data with nc')





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact