Re: QMQRY single vs double quotes/num vs char

["Jim Essinger" <dilbernator@xxxxxxxxx>]

Frances,

I picked this up from this list (I think).  What I do is to pass the &APOST
as a paramater to the QMQRY, and put it on either side of the character
variables.

For example, if the QMQRY was something like

Update FileName
Set ChgField = &APOST&NewValue&APOST
 where KeyField1 = &APOST&CharKey&APOST
     and KeyField2 = &NumKey

ChgField is character as is Keyfield1.  Keyfield2 is numeric.

Then my CL would look like;

           DCL        VAR(&APOST) TYPE(*CHAR) LEN(1) VALUE('''')

            STRQMQRY   QMQRY(QUERYNAME) SETVAR( ( CharField +
                       &CharField) (NumKey &SOME_NUM) +
                       (NewValue &CHARFIELD ) (APOST &APOST ) )

That way I worry only about what needs aposts in the qmqry, and not how to
get the value to the qmqry correctly.

In your example, the value SETVAR((INNEG 24.90) has no apost, and so should
not with your
statement;

CHGVAR     VAR(&INNeg) VALUE(&NegAmt)

The value in &NegAmt needs to be character, but don't put quotes around it.


HTH

Jim

On Dec 20, 2007 3:36 PM, Frances Denoncourt <
Frances.Denoncourt@xxxxxxxxxxxxxx> 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