Re: Standards for handling SQLCOD<>0

["Andrew Lutz" <alutz@xxxxxxxxxxxx>]

Not what you are asking for BUT, I recommend that you check SQLSTT instead it 
will catch more errors.....

I think the answer to your question would vary depending on: Interactive, batch 
and etc...

You can build the message with:

     Message ID: SQL + the positive value of SQLCOD
     Message Data: SQLERM

Retrieve message from QSQLMSG



>>> rob@dekko.com 03/15/02 01:20PM >>>

I've got many sql statements in one program.  I did something stupid.  I
checked SQLCOD after every statement and just returned blanks.  Now I'd
like to find out where I am getting this message:
Token / was not valid. Valid tokens: , FROM INTO.
You see, I do a lot of PREPARE's.  I'll probably run this through the
debugger, however is there a suggested routine to do upon SQLCOD being
improper?  Like display an error message id and pass it variables SQL...,?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.