Re: SQL multi-row FETCH

[Booth Martin <booth@xxxxxxxxxxxx>]

Your example offered me some good ideas.  Thank you.  They added to the 
solution and I appreciate that.

As to what/why I want to do this, if you look at the coding on my 
website you will see I really like adding a heading to each screen that 
is more than the usual three-line Company, Division, description.
(see http://martinvt.com/Code_Samples/Misc_/Figlet/figlet.html )

So I am creating a process that is a utility for allowing it to be done 
easily, and be maintained by non-programmers.  The DSPF uses a CNTFLD() 
to keep everything lined up, so yes, in the end I am interested in a 
continuous field which would easily be several hundred columns in length.

(I hard-wired the 3 rows by 120 columns for the question because I 
wanted to lessen the number of places I could make a typo.  In fact, 
they are variables.)



On 9/28/2015 1:36 PM, CRPence wrote:
>    Although the SQL could be used to return the three rows as one row of
> contiguous\concatenated data {as Buck had responded
> [http://archive.midrange.com/rpg400-l/201509/msg00192.html] though with
> no mention of using an OLAP query}, there seems little advantage in
> doing so.  As Buck alludes in that reply, any changes to the database
> likely would require recompiling the HLL program [as that into which
> "you're stuffing the results"], irrespective any encapsulation of the
> SQL [e.g. in a VIEW, UDT, or UDTF] done outside of the HLL.