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

Booth,

Could be several things.. Is there any SQL in this program? If the
tables used by a SQL statement were changed significantly since the
program last ran, the optimizer might decide to rebuild the access plan
on the first execution of the day.. Or, it could simply be paging data
into a memory pool, and leaving it there for subsequent calls.
SETOBJACC could be used to pre-load data objects into memory, shortening
first-call response time.

-Eric

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

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?