RE: Trigger pgm - SQL errors

Pete,

Not really sure, but if you can't get a valid customer number to use with
IBM, maybe MAPICS, Inc. could submit the APAR for the entire MAPICS
community, especially since they want customers to be using the Browser
technology. I know they've worked with IBM for past OS fixes when the bug
negatively impacts the MAPICS functionality.

       -- Joan

Joan McCready, IS Manager      phone:  636-479-4499
MetalTek International         fax:  636-479-3399
The Carondelet Division        www.metaltekint.com
8600 Commercial Blvd
Pevely, MO  63070                      


-----Original Message-----
From: Malcolm Westley [mailto:mwestley@xxxxxxxxxxx] 
Sent: Thursday, June 19, 2003 10:27 AM
To: mapics-l@xxxxxxxxxxxx
Subject: RE: Trigger pgm - SQL errors


   Pete,

   I would agree with Konrad that it would be a good idea to do a bit more
investigation, although there is a good case for an os400 bug. *Read= is
   a fairly new trigger program option, and a quick check of the ibm w
ebsite produced the following APAR whereby a decimal data error in Quer= y
   produced the same error you are seeing (the error was incorrectly gen
erated).

   <http://www-912.ibm.com/n_dir/nas4apar.NSF/c79815e083182fec862564
c00079d117/3b3476b7585cad5c86256c22003d4eb8?OpenDocument>

   Another way to test your problem would be to use the STRSQL command, th
en type in the command SELECT * FROM GELMAS and press Enter. If SQL i= s
   causing your error, you should see it crop up.

   As to how to report an APAR, I have not had to do so, but it looks as t
hough you will need a customer number of a customer with a valid servic= e
   contract in order to submit one. Ibm should be able to tell you how= to
   go about it. No doubt the first thing they will want to know is i= f you
   have all the latest fixes installed.

   Good luck,
   Malcolm

   > Pete,
   >
   > I would still rule out an OS/400 bug until you have done a bit mor= e
   > tracing. AM+ could be doing something strange in ODBC that is no
rmally
   > not seen because of the speed of the 400.
   >
   > You may want to look at the stack on the job that is making the re
peated
   > call to see exactly which program / line is creating the issue. = A
   > further step would be to do a normal odbc read of GELMAS and see i= f
   the
   > same issue arises. If it does not, check the ODBC connection par
ameters
   > for the AM+ vs your odbc connection to see if there are difference=
s=2E
   > Finally, if that fails turn on ODBC tracing for the AM+ connection= to
   > see exactly what the application is doing. In that you should se= e
   the
   > connection SQL strings as they get executed.
   >
   > HTH
   >
   > Konrad
   >
   >
   >
   > -----Original Message-----
   > From: Pete Olshavsky [ma= ilto:polshavsky@xxxxx=2Ecom]
   > Sent: Thursday, June 19, 2003 7:17 AM
   > To: MAPICS ERP System Discussion
   > Subject: RE: Trigger pgm - SQL errors
   >
   >
   > Malcolm, I tend to agree with you. I have never done this. Can= you
   > explain how? Also I am an independant programmer. Will I need an= IBM
   > customer no? Thanks Pete
   >
   > Malcolm Westley <mwestley@xxxxxxxxxxx> wrote:
   > Pete,
   >
   > Looks like you found an os400 bug. You should submit an APAR to    ibm.
   >
   > Malcolm_______________________________________________
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.