RE: Trigger pgm - SQL errors

Konrad & Malcolm, Thanks for your input. Don't want to beat a dead horse here. 
One more question. Malcolm. Your suggestion about strsql reminded me of 
something else... On the customer that I am trying to do this. I am not able to 
run the strslq command. Also I am not 100% sure about this but if I do a   GO 
CMDSQL ... I only have a couple of menu options. Could something not have been 
ordered on this box? Just installed beginning of the year. Missing a licensed 
product (DB2 Query Mgr and SQL DevKit for AS/400)
Thanks again for input
 
Pete
Malcolm Westley <mwestley@xxxxxxxxxxx> wrote:
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).



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.
> 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@xxxxxxxxx]
> 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 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.





---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!