Archives of the TeradataForum

Message Posted: Thu, 05 Feb 2004 @ 15:25:32 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Thursday, February 05, 2004 10:19 -->

Scott:

I do not know the specifics of your reporting, however if I had time to find the answer, I would pursue the following possibility.

Make the mainframe process a 2 step process. First create a bteq export file including one row for each specific customer to be reported on. Use this file as an IMPORT to a second bteq step. This second step would import the customer file rows one at a time using the .REPEAT command. Set up the .REPEAT command to be done once per imported row. Within the repeat loop you could have 2 SQL statements. The first SQL would create the report heading row using the imported variables. The second SQL would create the data(report) rows for the imported customer using the imported variables in the where condition.

I would then route output to an EXPORT DATA file thereby eliminating the bteq rules enforced under the EXPORT REPORT scenario. My expected results would be one file without REPORT formatting that contains multiple customer rows preceded by one heading row for each customer. I don't know if this would work, but if you are looking for suggestions it might be worth a whirl!

	<Prev	Next>		<<First	<Prev	Next>	Last>>