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



My script looks like this:
find ${1} -mtime +${2} -exec rm -d {} \;

My CL looks like this:
chgVar &cmd +
('/home/myDir/myScript.qsh' |> &path |> &days)
strQsh cmd(&cmd)

The variables &path and &days come from a database file. &PATH is *CHAR
200. &DAYS is *CHAR 5.

thanks,
Lorne.



"Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx> wrote in message
news:<mailman.4224.1261166102.31599.midrange-l@xxxxxxxxxxxx>...
Hi Lorne,

My suggeston is to use quotes to preserve the whitespace... but, it
looks like you've done that in your e-mail message (you have " before
and after your string.) But, then, your call to STRQSH is also
invalid
CL syntax. So I'm thinking your e-mail may not accurately reflect
your
program code.

So... put double quotes around the variable contents. If you're
already
doing that, then post some actual code so we can examine what you
might
be doing wrong.

Good luck


Lorne Sturgeoff wrote:
Do anybody know how to specify a CL variable which contains white
space when
invoking a Qshell script from a CL program?

For example, &PATH contains the following, "/My directory/My file".

I want to do something like STRQSH CMD('/home/mydir/myscript.qsh'
&PATH).

Thanks.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.