×
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.
I had an issue with that once with several parms that was a bear to get right. The CL was not something I would want to troubleshoot.
I ended up exporting the parms to the environment (QSHPARM01, QSHPARM02....) and referenced them in the script $QSHPARM01.......
The complexity of the call, as well as my stress level, went down exponentially.
Just another viewpoint.
Roger Harman
COMMON Certified Application Developer – ILE RPG on IBM i on Power
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Patrik Schindler
Sent: Tuesday, August 18, 2020 6:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: Calling QSH with variables from CL
Hello Peter,
Am 19.08.2020 um 02:35 schrieb Peter Dow <petercdow@xxxxxxxxx>:
Try
CHGVAR VAR(&QSHDOIT) VALUE('echo' *BCAT &MYSTR *CAT '; echo $?')
Thanks a lot! That's what happens when you use SEU and F4 Prompting: Automatic insert of Quotes all around the complete VALUE(). :-D Sometimes I feel blind…
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
https://www.pocnet.net/poc-key.asc
midrange.com
