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



CPD0044 is a CLP error, not an SQL one.

So there's nothing wrong with the SQL statement, there's something wrong
with the command.

I'd suggest doing a CHGJOB LOG(4 0 *SECLVL) LOGCLPGM(*YES)...

Then running your command, look in the log to see what's actually being
done.

Charles


Charles


On Mon, Aug 26, 2024 at 5:06 AM Gad Miron <gadmiron@xxxxxxxxx> 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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



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