Re: QMQRY single vs double quotes/num vs char

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I did that a few times way back when, and I always had the same problem.
I think what you need to do is set the value to (INPARCEL
'''''B018001304'''''). That's two "'" characters for every one that
works in the interactive command, plus one to enclose the whole mess. I
think what happens is that CL looks at it and interprets each pair of
"'" characters as a literal "'", then STRQMQRY does the same thing. So,
if you start with (INPARCEL '''''B018001304'''''), CL will see (INPARCEL
'''B018001304'''), and STRQMQRY will see (INPARCEL 'B018001304'), and
treat the value ->B018001504<- as a literal character constant. At least
that's my theory.

Pete Hall
pbhall@xxxxxxxxxxxxx


Frances Denoncourt wrote:
> I've looked through the archives and don't see anything that matches exactly my problem. I can get numeric data passed to the query - but, for some dumb reason, the character field not happening.
>
> Calling the query manager interactively works:
>
> STRQMQRY QMQRY(TRSFDD/TX_OVRPQ1X) ALWQRYDFN(*YES) SETVAR((INNEG 24.90) (INPOS 24.90) (INPARCEL '''B018001304'''))
>
> But am having difficulty with the parms in a CL
>
> DCL VAR(&PARCEL) TYPE(*CHAR) LEN(10)
> DCL VAR(&INPARCEL) TYPE(*CHAR) LEN(12)
>
> DCL VAR(&APOST) TYPE(*CHAR) LEN(1) VALUE('''')
> CHGVAR VAR(&INNeg) VALUE(&APOST *CAT &NegAmt +
> *CAT &APOST)
> CHGVAR VAR(&INPos ) VALUE(&APOST *CAT &PosAmt *CAT +
> &APOST)
> CHGVAR VAR(&INParcel ) VALUE(&APOST *CAT &Parcel *CAT +
> &APOST)
>
> This does not work because I need more quotes around the character field (parcel).
> I've tried several different ways to get it to work to no avail.
> Tried these among others: /* CHGVAR VAR(&INPARCEL) VALUE(&PARCEL) */ including adding a zillion quotes.
>
> Thanks for your help.
>
>
> Fran Denoncourt
> Sr. Programmer/Analyst
> Pinal County Treasurer's Office
> Florence, AZ 85232
> (520) 866-6404