...Nothing takes more resources and time than creating and deleting
jobs on the AS/400.
Opening and closing files much can be a drag on performance.
Using a data queue server is always a good idea.
I once did like Alan and Chuck and others have said, set up a data queue
NEP, where it was real slow, an early model AS400, small company, small
machine, and there was one program call that just returned customer file
data for the key values). Same job for each interactive, but it was
program initiation, open the customer file, move fields to return
parameters, close file, exit back and close the program. Slow, slow.
So I set up a data-queue based arrangement where a data queue was
created an *INIT time in the caller program, and instead of the program
call, I changed it to shoot off a data queue entry to a NEP job's data
queue. The NEP received the entry, and fetched the data (from the
customer file that stayed open), and returned the data to the other
program.
It was like bam! Even though disk use hovered around 80 percent plus,
doing it that way seemed like lightning fast in comparison.
Of course that was long, long, ago, and we've come a long way baby, :)
but IMO faster is better! As we progress into new ways of doing things,
too, like talking a lot to other machines, then there will be other
things that can drag us backwards and eat up cycles enough.
--Alan
midrange.com
