I if we start the process in another job, it gives us under 6 second response time. So your description fits the problem.

Vern Hamberg wrote:
The first time, none of the resources needed by the program are in memory. It has to initialize things. This is a common syndrome, sometimes called least-most-recently-used - I think you'd see something similar when the program has not been used for a long time - the system swaps resources out of memory so other jobs can use the space.

Now if you start the process up in one job, does it take the same long time in another job to do the same thing? That'd be a different issue, then.

HTH
Vern

Booth Martin wrote:
This doesn't make sense to me.
Here is what we're doing: We are running a program with this H-spec: H option(*nodebugio) dftactgrp(*no) actgrp(*new)

The first session runs for about 4 minutes before displaying data. Every session after that, whether from the same user or another user, displays the same data in under 6 seconds. Even if all instances of the program are ended, restarting a session is under 6 seconds.

30 to 40 spool files are generated by the process.
What could possibly be different between the first time and the subsequent times?






------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.56/2302 - Release Date: 08/14/09 06:10:00



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].