RE: CL Commands in SQL

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/04/2019
04:37:18 PM:

FYI, all RSS does is convert the CL:FOO... to CALL

QSYS2.QCMDEX('FOO...')

so I'm not sure what's different for you when you do it manually.

Either you misunderstand or I have confused the issue. I'm
talking about using the QCMDEXC stored procedure in a compound statement
within Run SQL Scripts vs. using the CL: prefix a line at a time within
RunSQL Statements. Run SQL Statements apparently executes the prefixed
line interactively using the same job environment in which Run SQL
Statements is running. If I simply change the CL: prefix to call QCMDEXC,
myself, then I get the same results. However, Run SQL Statements does not
execute the compound statement interactively. It compiles it into a
temporary object and apparently executes it in a new (or second level) job
environment and that apparently does not handle the internal QCMDEXC calls
the same way as when Run SQL Scripts executes QCMDEXC interactively.


Sincerely,

Dave Clark