RE: After Read trigger fires multiple times

Jerry,

See what happens if you do OVRDBF  SEQONLY(*NO).

That should turn blocking off.

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
> GKern@xxxxxxxxxxxxxxxx
> Sent: Thursday, February 24, 2005 4:01 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: After Read trigger fires multiple times
> 
> 
> More tidbits...
> 
> I did more testing and found out the following things are happening...
> 
> Regardless of whether I use *LOVAL or a key to SETLL, the 
> setll does cause 
> the trigger to fire. Under this circumstance, a do loop of 10 reads 
> results in the trigger firing 11 times.
> 
> If I don't setll and just do the read, the trigger fires 
> multiple times 
> even though only one read operation occurred. I think the DB 
> manager is 
> doing some blocking type stuff that is causing the 'read' 
> type activity. 
> One read caused the trigger to fire 36 times. The subsequent 
> nine reads 
> (in the do loop) didn't fire the trigger.
> 
> I did one other test, not doing the setll, and I took the K 
> off of the f 
> spec so that it would read in arrival sequence and the 
> trigger fired 39 
> times...
> 
> Regards, Jerry
> 
> Gerald Kern
> IBM Certified AS/400 RPG IV Developer & RPG IV Programmer
> MIS Project Leader, Lotus Notes/Domino Administrator
> The Toledo Clinic, Inc.
> 4235 Secor Road
> Toledo, OH 43623-4299
> Phone 419-479-5535
> gkern@xxxxxxxxxxxxxxxx
> 
> *****
> This email message, including any attachments, is for the 
> sole use of the intended recipient(s) and may contain 
> confidential and privileged information. Any unauthorized 
> review, use, disclosure or distribution is prohibited. If you 
> are not the intended recipient, please contact the sender by 
> reply email and destroy all copies of the original message.
>