RE: QM/400 Conversion

This isn't as simple as it seems, but the short answer is:  you can send the
output of a QMQRY to a file (*OUTFILE) and you can set up your selection
criteria to accomodate parameters with a little modification of your source
and use of the SETVAR parameters on the command.  The annoying part is the
syntax of the single quotes.  You can spend many happy hours with that. <G>
Anything in your query source preceded by an ampersand is considered a
variable and will represent any text string you assign to it in the setvar
corresponding to it.

eg:

select * from &file 
&where

That's a bit more generic than you might want, but in this one you can
substitute a file name and a logical condition every time you run it.

-----Original Message-----
From: Dennis Munro [mailto:DMunro@badgerminingcorp.com]
Sent: Tuesday, June 13, 2000 8:55 AM
To: 'MIDRANGE-L@midrange.com.'
Subject: QM/400 Conversion


I have gone throught the 28 (as of today) Query/400 queries that are run as
part of the end of month process & converted them to QM/400 objects.  It
wasn't as bad a job as I was fearing based on comments on this list but it
wasn't a piece of cake either.

The major dilema now is what to do with those queries (6) that create a
file?  For the present, I just run the Query/400 versions & use QM/400 for
the reporting function.  

What I would like to know is what options I have because these 6 queries
have variables that change (from/thru dates, accounting period, etc.) with
each running?  

/* Big Snip                                   */
+---
| 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
+---