RE: AS400 Query - Passing info from CL program? -- MIDRANGE-L

>> SNIP
>> Query/400 does not support any form of parameters.
>> ENDSNIP

>> WRONG!!!  This is their point.  Read it again.

Ok, you are right and I am wrong. (What's the shortcut for ouch.) Had to
read it several times. Should have followed the link immediately. That is
what I get for being in a hurry. O'well, my first for the decade, mistake
that is. <g>

-----Original Message-----
From: Rob Berendt [mailto:rob@dekko.com]
Sent: Wednesday, November 24, 1999 1:08 PM
To: MIDRANGE-L@midrange.com
Subject: RE: AS400 Query - Passing info from CL program?


SNIP
Query/400 does not support any form of parameters.
ENDSNIP

WRONG!!!  This is their point.  Read it again.




Alan.Campin@CaseLogic.com on 11/24/99 02:52:56 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        RE: AS400 Query - Passing info from CL program?

Are you confusing the WRKQRY product (Query/400) with STRQM (AS/400 Query
Manager)? You would have AS/400 Query Manager only if you bought the SQL
package. Query/400 does not support any form of parameters.

-----Original Message-----
From: Jim Langston [mailto:jlangston@conexfreight.com]
Sent: Wednesday, November 24, 1999 9:46 AM
To: MIDRANGE-L@midrange.com
Subject: Re: AS400 Query - Passing info from CL program?


You've got to be joking me?  You can pass parameters to
queries?  I've been wanting to do this for YEARS and could
never figure it out.

I read the query manager book pretty much cover to cover
looking for it.  So many times I wound up writing an RPG
report just because I didn't want my users to have to modify
a query to get what they want.

The next best thing to sliced bread, and IBM hides it in an
appendix???

Arrrrrrggggggghhhhhhhhhhhhhhh!

Regards,

Jim Langston

Dan Bale wrote:

> AAAAAAAAAAuuugggghhhhhhhhh!   Where the heck have I been?  Why isn't this
> documented in the Query manual?  You should'a heard the head-banging when
I
> shared this response with the others in our office, which, several months
ago,
> undertook a _major_ project to convert user-written queries with
hard-coded
> selections to QM queries (both *QMQRY & *QMFORM objects).  It got so bad
that I
> ended up scrapping some of the conversions and wrote RPG/CL from scratch;
much
> faster to production.
>
> Well, so, I guess, Thanks for the tip!  Next time..........
>
> If I'm not the only one who didn't know about this (which I suppose _is_
> possible), I think this would be an excellent tech tip in the trade rags.
Per,
> go for it; it might net you $50!
>
> BTW, this technique _does_ do a conversion to *QMQRY, it's just
transparent.
> This is important to know, because there are differences between WRKQRY
output
> and STRQMQRY *QMQRY output.  But it looks much cleaner than the
conversions I
> did in the past.  Oh, and character host variables have to be enclosed in
triple
> single quotes, i.e., SetVar((STATUS '''A'''))
>
> Will sleep better tonight.......
>
> - Dan Bale
>
> Per Nielsen <perni@centrum.dk> wrote:
>
> IBM har written a nice little paper about the subject "Passing Parameters
> to a query"
>
> Click the link below
>
http://as400service.rochester.ibm.com/s_dir/slkbase.NSF/$searchform?Open&vie
> w=wall
> In the search field write :
>
> Passing Parameters to a Query/400 Query
>
> The basic idea of the solution is in the select statement to write in the
> Select part:
>
> DATE      GE   :FROMDAT
>
> // Yes the : has to be there
>
> Save the query as normal i.e. a QRYDFN object.
>
> Run the Query with STRQMQRY and ALWQRYDFN(*YES) and set the variables in
> SETVAR
>
> I.e. in the above case:
>
> StrQmQry QmQRy(yourlib/yourqry) AlwQryDfn(*YES)
>      QmForm(*QMQRY) SetVar((FROMDAT 19991122))
>
> HTH
> Per Nielsen

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---