× 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 use the CL: in source files that are used for RUNSQLSTM

when running multiple SQL statements i do end each with a ";"
I also have *SYS naming, although I do use a dot between library.file and mostly force commit to *none

and I have been using this one, it seems to help depending on record length, MARGINS(*SRCFILE)
this is a v7.4(ptf SI78431) and v7.5(ptf SI78487).

Bryan


Charles Wilt wrote on 8/26/2024 1:15 PM:
What error?

What does your CL: command look like?

Charles

On Mon, Aug 26, 2024 at 11:30 AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Thanks Rob, Paul

Using / instead of . did not help

But, I toyed around with the SQL script and got it working after a fashion
table VRSISRCF was created alright..
turned out that some remarks were no properly marked with -- and
it played havoc with RUNSQLSTM (seemingly)

Now how do excecute CL CMDs in this SQL source :
the CL: prefix throws an error .

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.