Re: slow response time for first, and only first time program is run.

I think it has to do with caching.

When a first job initialize the objects required they are added to the
cache. Other jobs use that cache as well, not the initialization of the
first job.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 14-8-2009 at 14:22 Booth Martin wrote:

Narrowed down further. Here is the command:

WRKOUTQ OUTQ(QUSRSYS/PRT01) OUTPUT(*PRINT)

10,000 spoolfiles are in this queue.

Run from the command line = 2+ minutes.
Run again immediately, = 3 seconds
Run again 5 minutes later = 3 seconds


Nathan Andelin wrote:

From: Vern Hamberg
The first time, none of the resources needed by the program
are in memory.

Well, that's a generalization, but it seems to me that Booth needs to

narrow it down even further. I have trouble seeing a 4-minute
initialization subsequently dropping to 6 seconds, except in a case where
a job is having trouble allocating a particular resource the first time.

-Nathan.





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


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

--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.54/2300 - Release Date: 08/13/09
06:11:00