× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



   Pete,

   Looks like you found an os400 bug. You should submit an APAR to ibm.

   Malcolm

   > 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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.