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



IDK if you use the same starting position in the line which I did but this
is what I have:
...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6
*************** Beginning of data **************************
create table rob.VRSISRCF as (
select LNGCDE,WRKNBR, VRSION, ISRC, A.USER AS CHGUSER
from rob.GPLREFF A) with no data
****************** End of data *****************************
If something got chopped off at the end, might have this caused the error?
Since you use QDDSSRC that might start in a different position.

And, rob.gplreff was created with:
CREATE table rob.gplreff
(
lngcde *char*(*5*),
wrknbr *char*(*5*),
vrsion *char*(*5*),
isrc *char*(*5*),
*user* *char*(*10*)
);
When I run your statement with errors in runsqlstm it runs successfully
RUNSQLSTM SRCFILE(rob/qsqlsrc) SRCMBR(gad) COMMIT(*NONE) NAMING(*SQL)

Ownership of object VRSISRCF in ROB type *FILE changed.

Is RUNSQLSTM at a command line, in a CL program as normal, or, something
else via QCMDEXC?
Is it dying during compilation, or during execution?
The reason I am asking is the positional vs keyword error.
I am wondering if it is not the sql statement but the RUNSQLSTM in error.

On Mon, Aug 26, 2024 at 7: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.