This happens not often, but this time I agree with Dieter.
Create a view based on the complete select statement (with the exact field selection you need and including all Common Table Expressions, Joins, Group Bys, Nested-Sub-Selects etc. - without the Order By).
The view cannot only be used for accessing the data, but it can be included as external data structure.
In your program you define the view as external data structure.
In the Declare Statement you specify a simple SELECT * FROM VIEW (may be with several additional WHERE conditions and an ORDER BY clause).
In your FETCH statement you fetch the data directly into the external data structure.
No need to create an additional file with all the fields or a data area or what ever.
BTW a view is never keyed, it is nothing else than a stored select statement. In this way you theoretically can have thousands of views on the same table without any performance impact.
... and a view can be used where ever you use a table or physical file, e.g. embedded SQL, ODBC, JDBC, Download to Excel, WebQuery and even Query400 etc.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.