RE: Trigger pgm - SQL errors

Pete,

The description of that error seems more like a circular reference than
a call limit.

Message . . . . :   Too many triggers called.

Cause . . . . . :   The operation being performed on member &4 file &2
in     
  library &3 failed. A trigger program was called as part of the
operation.   
  That trigger program performed an operation which caused another
trigger    
  program (possibly the same trigger) to be called. This continued until
the  
  maximum number of nested trigger calls was reached. This maximum is
200.    
Recovery  . . . :   Use the DSPFD command to see the triggers associated
with 
  the file. Make sure that a trigger program does not perform an
operation on 
  the same file which would cause the same trigger to be called again.
This   
  can result in a series of trigger calls which will cause this error.

 

Does AM+ have any triggers on GELMAS as well? 

Or the trigger pgm causes a file operation that causes the same trigger
to be fired that causes the trigger to fire until 200 nested calls are
reached.

Konrad


-----Original Message-----
From: Pete Olshavsky [mailto:polshavsky@xxxxxxxxx] 
Sent: Wednesday, June 18, 2003 9:12 AM
To: MAPICS ERP System Discussion
Subject: RE: Trigger pgm - SQL errors


Basically the joblog pointed to error message CPF523D Too many triggers
called. Max 200. 


Dave Lauderdale <DLAUDERDALE@xxxxxxxxxxxxxx> wrote:
Pete,

What did the joblog tell you? I checked the message and it says to refer
to the joblog for additional information. 

David

-----Original Message-----
From: Pete Olshavsky [mailto:polshavsky@xxxxxxxxx]
Sent: Wednesday, June 18, 2003 6:43 AM
To: mapics-l@xxxxxxxxxxxx
Subject: Trigger pgm - SQL errors [bcc][faked-from][mx]


Morning list,
I have a customer that wanted to put some kind of security over the
GELMAS file. We discussed on this thread about using AS400 security. But
the feeling I came away with was... Be careful be very very careful. And
be afraid. So the route we decided was to put a *read trigger on the
gelmas file. Which seems to be working perfectly. Whenever anyone reads
the file. Like a G/L audit. INquiry into an acct, Query the file, Dfu
the file. Program works like I want it to. 
Now the Problem. 
If I go to AM+ in the browser and click the icon for General ledger I
get SQL trigger in failed SQLCODE SQLSTATE. 
I can barely spell SQL. So I really don't understand the error message..
But the best that I can tell and that Mapics support can tell is that
SQL is reading records faster than the AS400 trigger pgm can process,
and end. I have even tried to setup my CL to really do nothing more than
cancel if the user is QUSER. 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?????

I am not at that account today so I don't have the ability to test
anything. 
TIA
Pete Olshavsky
Ind Mapics Programmer/Systems Analyst


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
_______________________________________________
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.

_______________________________________________
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.


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
_______________________________________________
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.