Re: Service Program Overhead

Is the IFS file remain open for all subsequent calls to the subprocedure
that writes data to the ifs file? It is hard to believe that your home
grown code can't beat CPYTOIMPF.


"James Perkins" <jrperkinsjr@xxxxxxxxx> wrote in message
news:<mailman.1121.1258137931.2617.rpg400-l@xxxxxxxxxxxx>...

Hello All,
I had to write a program to write DB data to a stream file in comma
delimited format. No problem, done it many of times. Then I ran into a
problem, running the program seemed to take hours. Well, I determined

that

was a bad subprocedure on my part, so I fixed that and it now takes

only

about 5 minutes to run.

While doing this doing this I tried a couple of other approaches. I

wrote

the data to a table and used CPYFRMIMPF to export it to a CSV, this

took

about 1 minute 40. I also wrote a simple Java program to execute an

SQL

statement and write the results to a stream file, this took about 1

minute

10. ** Note, there was no scientific approach to the time calculation,

just

simple start and end times.

It seems that the invocation of subprocedures in a service program
significantly slows down performance. I invoke 2 subprocedures on each

write

to the stream file, a replace all subprocedure and the write line
subprocedure. So, for the question, what kind of overhead is there

when

invoking subprocedures from a service program? I'm sure there is

information

on this, I just can't seem to find it.

Thanks in advance,
--
James R. Perkins
http://twitter.com/the_jamezp