×
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.
Good to know - hmm - stdout for results display - will have to give it a look sometime.
I know I've been advocating for a general-purpose command to run SQL statements, including SELECT, and that is usually done with a QMQRY made up all of substitution variables. You mention reporting - for me, that is not a requirement - if so, I'd say to go all the way and use a purposeful QMQRY with a matching QMFORM, or get one of the reporting products like SEQUEL or NGS-IQ or Clover or Web Query (did I cover them all?).
So the QShell db2 could be good enough for just getting a look at data with full selectivity - above and beyond what RCDSLT on RUNQRY can give you.
Vern
----- Original Message -----
On 03 Jul 2013 06:15, Vernon Hamberg wrote:
<<SNIP>>
If the goal is to _display_ the results, QMQRY is the easiest way,
or maybe the QShell db2 function. I don't know if the db2 function
allows SELECT.
The db2 function of the QSH does support SELECT, but its capabilities
as a report writer are very minimal; report lines are directed to the
StdOut, and unless improved, the feature still does only single-row
FETCH so it likely would be very slow for all but /small/ result sets.
midrange.com
