User space, outfile or workfile

Hi group,

I'm trying to make a general purpose utility which will copy any PF into an
XLS file in the IFS (using some java class behind the screens).  When it's
finished, I will probably make it available to the public on my new website
(yet to be developed).

In order to determine the field types (alpha or numeric) for the XLS, I see
three possibilities:

* Using the QUSLFLD API to a user space, and loop through that for every
record
* Doing a DSPFFD into an outfile in QTEMP and loop through that for every
record
* Using the QUSLFLD API, read it once, write the fieldname and data type to
a workfile in QTEMP, and loop through that for every record

Considering that the files can be rather large (I think I will make the
program automatically create a new sheet when the row counter reaches 65000
or whatever the limit in Excel is), performance may be an issue.

Can anybody tell me which would be the fastest of the 3?

I know I could code the 3 versions and run performance tests, but I'd hate
to hear someone say later on: 'Oh, but I could have told you in advance
that xxx would be much faster.'

Thanks in advance.

Peter Colpaert
Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Belgium
Peter.Colpaert@xxxxxxxxxxxx
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
----------



______________________________________________________________________
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
the entity to whom it is addressed and others authorised to receive it. If
you have received it by mistake, please let the sender know by e-mail reply
and delete it from your system.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or taking any action in reliance of the
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.