RE: CL Commands in SQL

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/04/2019
12:55:59 PM:

"CL:" is ONLY valid within Run SQL Scripts tool. All other places
you have to revert back to QCMDEXC().

The problem I have with using the stored procedure is that it
creates another execution level. That would be fine, except that the
second CL command I have to run is dependent upon the environment created
by the first CL command. In Run SQL Scripts, the two CL commands execute
in the same environment.

CL: CALL PGM(UTSETLLCL) PARM('00203');
CL: IMIOVEVAL CMDUSE(*MONTHEND);

Using the stored procedure they do not. Is there a solution that
does not require having to reprogram the second command? ...or having to
write the two commands into yet another CL to call by itself?

call qsys2/qcmdexc('CALL PGM(UTSETLLCL) PARM(''00203'')');
call qsys2/qcmdexc('IMIOVEVAL CMDUSE(*MONTHEND)');


Sincerely,

Dave Clark