RE: Intermittent delay on a table insert.

Pete,

Yes, that is why I am stumped! I do have a game plan today though, I am
simply going to shut down the front end but allow the trigger to continue
firing, they will be waiting for me. If it slows down then I can point to
ODBC and other parts of the workload! In any event it gets the fingers
pointing at something else other than me.

-----Original Message-----
From: Pete Hall [mailto:pbhall@ameritech.net]
Sent: Wednesday, February 05, 2003 7:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Intermittent delay on a table insert.


At 09:30 02/05/2003, Howard Weatherly wrote:
>1. GUI application processes changes against DB2 tables, things are swift
in
>all cases up to the last item which is to insert a row (length 34) into a
>table which has an insert/ after trigger.
>         a. Intermittently this last step takes for-ever! and about 5 or
more
>minutes.
>2. Trigger Program does two things, a. RTVJOBNBR and b. QSNDDTAQ then ends.

That's the only part of your process that occurs synchronously in regard to 
your client program. The rest operates in a separate unrelated job, after 
your client process returns to do other stuff.


Pete Hall
pbhall@ameritech.net
http://www.pbhall.us/

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.