RE: Trigger pgm - SQL errors

[Malcolm Westley <mwestley@xxxxxxxxxxx>]

   Pete,

   This error occurs when a trigger program calls itself, usually by tryin= g
   to re-access another record in the same file. From your description= ,
   it sounds as though another trigger program is involved; one that use= s
   SQL. Is there another trigger program on gelmas?

   Malcolm

   > date: Wed, 18 Jun 2003 06:12:03 -0700 (PDT)
   > from: Pete Olshavsky <polshavsky@xxxxxxxxx>
   > subject: RE: Trigger pgm - SQL errors
   >
   > Basically the joblog pointed to error message CPF523D Too many <br= > >
   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 [ma= ilto: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 th= e
   > GELMAS file. We discussed on this thread about using AS400 secur   ity.
   > But the feeling I came away with was... Be careful be very v= ery
   > careful. And be afraid.
   > So the route we decided was to put a *read trigger on the gelmas <= br>
   > file. Which seems to be working perfectly. Whenever anyone rea= ds
   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 ledge= r
   > I get SQL trigger in failed SQLCODE SQLSTATE.
   > I can barely spell SQL. So I really don't understand the error <= br>
   > 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 re= ally
   > do nothing more than cancel if the user is QUSER.
   > Is there a way to tailor SQL to slow down without affecting the <b= r> >
   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