RE: Sanity check

[Colin Williams <Williamsc@xxxxxxxxxxxxxxxxx>]

Have you tried running Performance Explorer over the program, to
pinpoint exactly which statements are causing the problem?

-----Original Message-----
From: Roger Boucher [mailto:RBoucher@stanpac.com]
Sent: Monday, July 26, 1999 6:57 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: Sanity check


Thanks Chuck.  The file size is not growing at all, and the program is
doing
a READE after the SETLL.  In debug, about 90% of the time the program
takes
to run seems to all be coming from that one SETLL statement.  Any other
thoughts?


-----Original Message-----
From: Chuck Lewis [mailto:CLEWIS@IQUEST.NET]
Sent: Friday, July 23, 1999 7:39 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Sanity check


Roger,

If it used to work fast, then this wouldn't explain it BUT if you aren't
sure it
could be that the file has REALLY grown in size (?) and a poorly written
program
is doing a SETLL and READ rather than a SETLL & READE to the key and
kicking
out
?

Chuck

Roger Boucher wrote:

> I have a user (controller) who swears up and down that an invoice
inquiry
on
> our legacy system (an old AS/400 kept around for inquiry purposes
only) is
> taking much longer than it used to.  I tested it and found that it
works
> quickly if record is found and takes about 30 seconds when record not
found.
> The problem point (debug) seems to be a SETLL statement on a
multi-record
> format LF38.  The logical is not damaged, the physicals on which it is
based
> are not damaged.  The Edit Rebuild of Access Paths screen shows
nothing
> pending.
>
> Does anyone know anything else to look for?
> Or Is this just a case of selective memory on the part of our friendly
> neighborhood user?
>
> Any help would be appreciated...
> Thanks.
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---