Re: edit a *QRYDFN query outside of WRKQRY interface?

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Dan

If you have interactive SQL, you also have Query Manager. This is a front 
end to QMQRYs, and it can be run in a mode that seems a lot like Query/400. 
Or it can be run something like interactive SQL - same prompting.

The biggest gotcha when converting Query/400 to QMQRY is joins - the only 
one that comes through correctly is a type 1.

<commercial>

We have a product called query/CONVERTER that takes IBM's RTVQMQRY up a 
notch. It lets you do multiple QRYDFNs, and it puts the various message 
output from the retrieve into the source member generated.

</commercial>

Vern

At 09:43 PM 6/26/2003 -0400, you wrote:

> Dan,
>
> Yeah, I agree ... this has always been one of my pet peeves too.
>
> Have you considered converting (some or all of) your *QRYDFN objects to
> *QMQRY objects instead?  You can use the RTVQMQRY command with the
> ALWQRYDFN(*YES) keyword to create *QMQRY source members containing an SQL
> statement in each.  This gives you the freedom to use WRKMBRPDM using
> option 2 to edit the SQL statement in the source member, option 14 to
> create the *QMQRY object.
>
> Note that the report output might need some work via *QMFORM's since the
> default generic report style for *QMQRY's can be a bit simplistic.  But if
> you REALLY hate being forced to use WRKQRY to get into *QRYDFN's, *QMQRY
> might help you feel better!  (We aim to please!)
>
> Bill