<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1523" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=139242217-09122005><FONT face=Arial color=#0000ff size=2>The
first thing to do would be to check the access into the various tables/views to
see if there is any sequential access going on. Use
"$DEFINE RDMS$DEBUG_FLAGS SO" to setup the display, then run this process and
log the access display as it comes up on the screen. Look for
"sequential" or "[0:0]" which will indicate a problem. </FONT></SPAN></DIV>
<DIV><SPAN class=139242217-09122005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=139242217-09122005><FONT face=Arial color=#0000ff size=2>Also,
run the rdb monitor to check for locks "$RMU/SHOW STAT sql$database", then
use commands D, I, A to get to the lock screen.</FONT></SPAN></DIV>
<DIV><SPAN class=139242217-09122005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=139242217-09122005></SPAN> </DIV>
<DIV><SPAN class=139242217-09122005><FONT face=Arial color=#0000ff size=2>good
luck</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
powerh-l-bounces+harold.a.johnson=gov.bc.ca@lists.sowder.com
[mailto:powerh-l-bounces+harold.a.johnson=gov.bc.ca@lists.sowder.com]<B>On
Behalf Of </B>John Stires<BR><B>Sent:</B> 2005 December 9 9:15
AM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> Quick
Procedures<BR><BR></FONT></DIV>
<DIV id=RTEContent>I am working on a rather complex screen. Those
working on this screen before me have pretty well disabled and/or misused all
of the default procedures so there is very little left to Powerhouse
to handle on its own.</DIV>
<DIV> </DIV>
<DIV>My question is this, there is a PUSH UPDATE in one of the designer
procedures. When this happens, does it automatically initial the
PREUPDATE first and then go to the UPDATE procedure or does it go straight to
the UPDATE procedure bypassing the PREUPDATE.\We are having big time response
problems with this program, a very good likely hood this is caused by
deadlocks. A user update to this screen is now 45 minutes to 1
1/2 hours. Not very good.</DIV>
<DIV> </DIV>
<DIV>All of the code that should be in the PREUPDATE procedure is currently
located in the UPDATE procedure. There are PUTs sprinkled through all of
this code making this a time consuming process. I ! am looking to reduce
the time spent in the UPDATE procedure by moving much of this code to the
PREUPDATE procedure. I am very sure there are many other things to be
done as well.</DIV>
<DIV> </DIV>
<DIV>The second issue with this screen is how it handles the detail file
updates. The screen defines a cluster, but uses temp items, named after
the fields in the real record. The file statement looks like:</DIV>
<DIV> </DIV>
<DIV>file OBLIGATION_TRANS in CARS_DB designer noitems need all
&<BR> transaction query for query, process &<BR>
transaction update for update<BR></DIV>
<DIV>with the field statements looking like:</DIV>
<DIV> </DIV>
<DIV>cluster at 19,1 occurs 5</DIV>
<DIV>field
T_REMAIN_AMT
&<BR> label "
"
&<BR> hidden
nochange
&<BR> pic "^^^,^^^,^^^.^^" bwz signif
4</DIV>
<DIV>field
T_POSTBACK_BALANCE
&<BR> upshift
required
&<BR> values "Y","N"</DIV>
<DIV>field
T_DTL_REASON_CODE
&<BR> hidden required upshift</DIV>
<DIV>field
T_DTL_REASON_DESC
&<BR> display</DIV>
<DIV>field
T_TRANS_AMT
&<BR> entry if T_POSTBACK_BALANCE = "N"
&<BR> pic "^^^,^^^,^^^.^^" bwz input scale 2
signif 4</DIV>
<DIV>cluster</DIV>
<DIV> </DIV>
<DIV>In the UPDATE procedure, there is a FOR structure using 5 as its
limit. The users get "reasonable response time", 5 minutes, if they only
enter up to 5 entries in these fields. When they enter more than 5,
their response time goes to over 45 minutes.</DIV>
<DIV> </DIV>
<DIV>Needles to say I am under some serious pressure here to make some big
improvements.</DIV>
<DIV> </DIV>
<DIV>We are running on VMS 6.2, Powerhouse vers! ion 7.10e6, and DEC RDB, I
think version 6.1.</DIV>
<DIV> </DIV>
<DIV>Thanks for any good impute,</DIV>
<DIV> </DIV>
<DIV>John Stires</DIV></BLOCKQUOTE></BODY></HTML>