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

Booth,

First, the list is apparently being cached so that subsequent executions don't have as much to consider. Sort of like doing a scan on a source PF in PDM; the first time is relatively slow, but the 2-n scans scream.

Second, is that for a relatively recent period (1-3 days)? I'm with Rob and others on this. Since V5R4 I've always used the EXPDATE/DAYS options on printer files; usually no more than 3 days (to cover weekends). And then set up a job in the scheduler to run the DLTEXPSPLF command shortly before midnight every day.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Friday, August 14, 2009 2:23 PM
To: Midrange Systems Technical Discussion
Subject: Re: slow response time for first, and only first time program is run.

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