Re: Trigger pgm - SQL errors

[michael.franchino@xxxxxxxxxx]

That's an easy one - that message is issued for a recursive trigger call. 
In other words the trigger program modifies the file that caused the 
trigger to fire which causes the trigger to fire again... and again... and 
again. 

Michael Franchino
Custom Systems Corporation
http://www.cussys.com
(973) 726-0202 X214 (Phone) 
(973) 726-4552 (Fax)




Ron Hankey <Ron.Hankey@xxxxxxxxxxx>
Sent by: mapics-l-bounces@xxxxxxxxxxxx
06/18/2003 11:53 AM
Please respond to MAPICS ERP System Discussion

 
        To:     mapics-l@xxxxxxxxxxxx
        cc: 
        Subject:        Re: Trigger pgm - SQL errors


Is it possible for your trigger to submit a job to batch OR send the entry 

to a data queue to perform the update of the log file?
We use this method quite often to prevent possible trigger failures from 
hanging a job.

Is it possible your trigger is performing some operation to the GELMAS 
file causing it to fire the trigger again?
(From the message it sounds like this is a possibility.)
Are there other triggers on GELMAS other than the one you added?

Is the GELMAS file journaled for both before/after images?
Does AM+ use commitment control?

Since the error only occurs when AM+ is used it's method of accessing the 
file is causing your trigger or another trigger to be invoked multiple 
times until it reaches the 200 invocation limit.

Some good tips for SQL can be found at:  http://www.as400pro.com/tips.htm

Pete wrote:
>Basically the joblog pointed to error message CPF523D Too many triggers 
called. Max 200. 
<SNIP>
>Is there a way to tailor SQL to slow down without affecting the other 
browser apps' or any other tricks not to get >the trigger pgm to fire?????
<SNIP>

Ron Hankey - CPIM
Applications Programmer

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