I'm not sure what you mean, but AFAIK the Run SQL Scripts just replaces
those CL: with a call to QCMDEXC, so I'm not sure how it would be any
different.
The only thing I could think of is using QSYS.QCMDEXC instead of
QSYS.QCMDEXC.
----- Original message -----
From: dlclark@xxxxxxxxxxxxxxxx
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: RE: CL Commands in SQL
Date: Mon, Mar 4, 2019 1:09 PM
"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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
--
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: [1]
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 [2]
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: [3]
https://amazon.midrange.com
References
Visible links
1.
https://lists.midrange.com/mailman/listinfo/midrange-l
2.
https://archive.midrange.com/midrange-l
3.
https://amazon.midrange.com/
midrange.com
