|
Pete, It appears that is still the top level message. The actual data contains the issue it found (in detail) we hope. So the 1, 2, 3, 4 and 5 values are the issue(s) it found. Message ID . . . . . . . . . : SQL0723 Message file . . . . . . . . : QSQLMSG Library . . . . . . . . . : QSYS Message . . . . : SQL trigger &1 in &2 failed with SQLCODE &3 SQLSTATE &4. Cause . . . . . : An error has occurred in a triggered SQL statement in trigger &1 in library &2. The SQLCODE is &3, the SQLSTATE is &4, and the message is &5. Regards Konrad -----Original Message----- From: Pete Olshavsky [mailto:polshavsky@xxxxxxxxx] Sent: Wednesday, June 18, 2003 8:27 AM To: MAPICS ERP System Discussion Subject: RE: Trigger pgm - SQL errors Konrad the SQL error that popped up when I was trying to get into the G/L was SQL0723... What the program is suppose to do. Whenever anyone except a couple of managers readsthe gelmas file it logs the user, the pgm the acct#and the date to a log/audit file. Pete, The one about SQL being too fast is funny. What exactly was the message? SQL0000? That usually points out the problem or at least points in the direction of a correct diagnosis. Also what did or does the trigger program do? Regards Konrad -----Original Message----- From: Pete Olshavsky [mailto:polshavsky@xxxxxxxxx] Sent: Wednesday, June 18, 2003 7:43 AM To: mapics-l@xxxxxxxxxxxx Subject: Trigger pgm - SQL errors 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.
As an Amazon Associate we earn from qualifying purchases.
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.