×
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.
Sheri Rowe System i Administrator
Thank you Sharon, Jim and Chuck!!!!
My problem was the case of the variable. I did not even think to look
at that, as I didn't realize it would be case sensitive.
OK, 2 days to trouble shoot a case sensitive problem. I won't forget
this any time soon.
Thanks again!!!
Sheri
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: January 9, 2009 2:48 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Dumb question about STRQMQRY passing parms
I did not see this posted yet on the correct group\list, so I will
respond here.
I do not think this is a problem with quoting; the logged CL request
from the CLP should /look just like/ what was specified on a command
line for a successful invocation. In this case, the QMQRY source was
compiled referencing &fromdate, *however* the SETVAR() is passing a
literal assignment for the variable &FROMDATE. Recreate the QMQRY from
source which has changed to use\name the variable name &FROMDATE instead
of &fromdate, and try the CLP again.
http://www.google.com/search?hl=en&q=qmqry+upper+case+variable+name+v5r4
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/books/sc4157
03.pdf
Regards, Chuck
midrange.com
