|
Pretty sure there is an FAQ entry for this too. On 6/15/05, Dwayne Allison <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > STRQMQRY QMQRY(*LIBL/ACTCLMTQ) OUTPUT(*OUTFILE) + > QRY > QMFORM(*QMQRY) OUTFILE(*LIBL/ACTCLMTQ) + > QRY > ALWQRYDFN(*ONLY) SETVAR((FDATE &FDATE) + > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of > MWalter@xxxxxxxxxxxxxxx > Sent: Wednesday, June 15, 2005 10:38 AM > To: Midrange Systems Technical Discussion > Subject: Re: Passing parm to query > > > You could convert the query to a QMQRY and use the STRQMQRY command with > paramters. > > Thanks, > > Mark > > Mark D. Walter > Senior Programmer/Analyst > CCX, Inc. > mwalter@xxxxxxxxxx > http://www.ccxinc.com > > > > pnelson@xxxxxxxxx > m > Sent by: To > midrange-l-bounce Midrange Systems Technical > s@xxxxxxxxxxxx Discussion > <midrange-l@xxxxxxxxxxxx> > cc > 06/15/2005 11:31 > AM Subject > Re: Passing parm to query > > Please respond to > Midrange Systems > Technical > Discussion > <midrange-l@midra > nge.com> > > > > > > > > If you do this a lot, look into SEQUEL/Viewpoint from ASC > (www.asc-iseries.com). They've got this function built in to the software. > My clients use this 6 ways from Sunday. > -- > > Paul Nelson > Arbor Solutions, Inc. > 708-670-6978 Cell > pnelson@xxxxxxxxxx > > > > > -----midrange-l-bounces@xxxxxxxxxxxx wrote: ----- > > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > From: "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > Date: 06/15/2005 11:20AM > Subject: Passing parm to query > > Is there a way to pass a parm to the "Select Records" section of a query > & run in batch (example below): > > RUNQRY QRY(GALP/IIQ90MP) OUTTYPE(*PRINTER) + > OUTFORM(*DETAIL) PRTDFN(*NO) + > PRTDEV(*PRINT) FORMSIZE(200 200) + > OUTFILE(*RUNOPT *FIRST *RPLFILE) > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.