|
We have a program called FIRSTTOUCH that we run after an IPL that touches
all programs. We were getting a performance hit on first use otherwise.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
"Crispin Bates" <cbates@xxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
08/14/2009 12:27 PM
Subject:
Re: slow response time for first, and only first time program is run.
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
I have seen this (on a V5R4 570 MMA). It was reported by our QA staff. The
first time a screen is accessed it takes way longer than subsequent acces,
even from different jobs. I have speculated that the access plan is being
cached somehow, even though this is native access. Not bothered to
investigate further...
----- Original Message ----- From: "Booth Martin" <booth@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, August 14, 2009 12:06 PM
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?
--
---------------------------------
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.