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



I just ran this successfully. It mimics your pattern. Semicolon wasn't needed.

SQLTEST
----------
CREATE TABLE QTEMP.TEST01 AS (
SELECT CUSNUM, LSTNAM
FROM QIWS.QCUSTCDT A) WITH NO DATA

Ex:
RUNSQLSTM SRCFILE(QGPL/QTXTSRC)
SRCMBR(SQLTEST)
NAMING(*SQL)

Maybe try *NONE for commitment control.

And definitely check the joblog for errors.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
 
----------------------------------------------------------------------

message: 1
date: Mon, 26 Aug 2024 07:44:04 -0700
from: Peter Dow <petercdow@xxxxxxxxx>
subject: Re: Create table as and RUNSQLSTMS

Hi Gad,

I think you need a semicolon after "with no data".

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx
pdow@xxxxxxxxxxxxxx

/
On 8/26/2024 4:05 AM, Gad Miron wrote:
Hello guys

I need some help sleuthing the following:
the following SQl statement runs fine in RUNSQL or STRSQL

create table DCMTLIBD.VRSISRCF as (
select LNGCDE,WRKNBR, VRSION, ISRC, A.USER AS CHGUSER
from QTEMP.GPLREFF A) with no data

However, when the same statement is included in a source member and
trying RUNSQLSTMT , like RUNSQLSTM SRCFILE(IN0003/QDDSSRC)
SRCMBR(VRSISRCF_) COMMIT(*NONE)
NAMING(*SQL)

it fails with several CPD0044 Positional value cannot follow keyword
parameter.

Could not wrap my head around it.

Any idea will be received thankfully.

Gad

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.