Re: Query Management Reports Problem

[vhamberg@xxxxxxxxxxx]

Alan

You probably know this - so let this pass through to others!!

There are several things that do not convert nicely when doing the RTVQMQRY - especially the type 2 and 3 JOINs. IBM have chosen not to put in the time to generate the statement that would be equivalent.

There are others - look in the Query Management Programming manual cited in an earlier post - chapter 12 or something - look for Query/400 or something like that.

Query/400 does not use internally any of the QM stuff, that I know of. IBM have simply made it convenient to take the layout information from a *QRYDFN and generate the almost-equivalent *QMFORM source - ugly in the extreme, by the way!

QM is a cross-platform technology - one could be given a QMQRY from a mainframe and import it into the iSeries. It has wonderful capabilities and several oddities to it.

Vern

-------------- Original message -------------- 
From: "Alan Campin" <Alan.Campin@xxxxxxxxxxxxxxxx> 

> I believe [or at least I hope] you have mis-remembered what you were 
> told. The Query/400 report writer is used by the STRSQL, to produce the 
>
> output for non-DRDA interactive SQL requests. The QM report writer is 
> separate. The following thread: 
> http://archive.midrange.com/midrange-l/200708/msg01234.html 
>
>
> Interesting thing is if you do a RTVQMFORM from a QRY/400 and QMQRY 
> object you get the same thing. Same underlying engine or just the same 
> file format? 
>
> Also, when you retrieve the query (RTVQMQRY) what you get back from the 
> QRY/400 object is not necessarily correct which implies that it is just 
> guessing at what the SQL would look like if they were running SQL.