× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Passing Parameters to Query -- format problems
  • From: "Peter Dow" <pcdow@xxxxxxxxx>
  • Date: Thu, 17 Feb 2000 11:51:20 -0800

Thanks Joel. Actually, you can use STRQM and get pretty much the same stuff
you do with WRKQRY. I was trying to avoid that, since it's a user at a
client maintaining the query, and using STRQM would entail retraining said
user.

BTW, to all on the group, I accidentally posted this request again under a
different subject - please ignore the post.

Thanks,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


----- Original Message -----
From: Joel Fritz <JFritz@sharperimage.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, February 17, 2000 10:53 AM
Subject: RE: Passing Parameters to Query -- format problems


> Unfortunately, no.  There's an appendix to the QMQRY manual that goes into
> great detail on incompatibilities between Query400 and QMQRYs.  You can do
> darned near anything you want with the printed output if you learn how to
> code QMFORMS.  It's all documented in (at least the US manual) in a
language
> that bears a deceptive resemblance to English.  Don't look to SEU for any
> help.
>
> I pretty much use them for output to a file.
>
> > -----Original Message-----
> > From: Peter Dow [mailto:pcdow@yahoo.com]
> > Sent: Wednesday, February 16, 2000 5:52 PM
> > To: MIDRANGE-L@midrange.com
> > Subject: Passing Parameters to Query -- format problems
> >
> >
> > I finally had the opportunity to use the method described at
> >
> > http://as400service.rochester.ibm.com/s_dir/slkbase.NSF/$searc
> > hform?Open&vie
> >
> > (search for "Passing Parameters to a Query/400 Query").
> >
> > This method works fine as far as the parameters are concerned.
> >
> > However, there are drawbacks. QM query manager does a poor
> > job of importing
> > the report formatting of the Query/400 query. It loses edit codes for
> > numeric fields, column spacing for all fields, standard
> > headers are lost,
> > and the report width is not used to automatically override
> > the QPQXPRTF
> > printer file - instead it will either leave lots of blank
> > space to the right
> > (if the data is smaller than the printer file page width) or
> > create multiple
> > spool files with different horizontal sections of the report
> > (if the data is
> > larger than the page width).
> >
> > To get the QM query to look like the Query/400 output
> > requires more work
> > than expected based on this document.
> >
> > Am I missing something?
> >
> > Peter Dow
> > Dow Software Services, Inc.
> > 909 425-0194 voice
> > 909 425-0196 fax
> >
> >
> >
> >
> +---
> | 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
> +---


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.