×
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.
Rob demonstrated a way to execute a command as a result column. Basically, made a QCMDEXC() scalar function. I think his version named the function the same as the procedure but I fell into problems and named my without the Q.
CL: is not allowed because it is interpreted by the ACS RSS processor where as a compound statement is compiled code.
-Matt
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Monday, March 4, 2019 11:02 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: CL Commands in SQL
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/04/2019
12:57:55 PM:
I have just tested that and it works fine in RUNSQLSTM. I used a
single line of
CL: DSPJOB OUTPUT(*PRINT);
And that worked fine.
Not the answer to your question, but it is another way to execute
scripted SQL.
OK, but try it this way. I need to execute two CL commands in a
REPEAT loop.
Begin
CL: DSPJOB OUTPUT(*PRINT);
End;
Sincerely,
Dave Clark
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.
midrange.com
