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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.