×
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.
"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
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
