RE: Retrieve SQLCODE descriptions programmatically?

The issue I was responding to was his concern that the SQLERRM is not the
right length for the MSGDTA parm of RTVMSG. You don't know what the
structure of the variables is from SQLERRM, do you? SQL0004 has 3 values,
each 10 characters long. SQL0007 has 2, each 1 byte long.

Or can you just get away with tossing in the values from SQLERRM and not
worry about overflow? Just make the variable you use in MSGDTA long enough
for all situations?

At 03:58 PM 4/11/02 -0400, you wrote:

> >I suppose the old standby - DSPMSGD OUPUT(*PRINT), then CPYSPLF, then
> >massage that for the data fields.
>
>
>Vernon
>
>Ah, No,  Do what Walden said,  then do a RTVMSG bring it back
>and substitute your variables for the &1 &2 in the MSGDTA
>using %REPLACE BIF.
>
>Not that hard.
>
>As a Side tip,  DSPMSG is one of the Rare CL commands that you can over
>ride the print file to a PF. Like this;
>
>  OVRPRTF    FILE(QPMSGD) TOFILE(MY_PF)
>
>then do a
>
>DSPMSGD    RANGE(*ALL) MSGF(&MSGFLIB/&MSGF) OUTPUT(*PRINT)
>
>and have the result go directly to a PF that you can look at.
>
>Done that many times.
>
>I have an inquiry where I can search and find out which
>MSGID's have (say)  'Invalid Customer" somewhere in the
>text by doing the above.
>
>
>John Carr
>------------------------------
>
>I suppose the old standby - DSPMSGD OUPUT(*PRINT), then CPYSPLF, then
>massage that for the data fields.
>
>At 02:32 PM 4/11/02 -0400, you wrote:
> >SQLCODE translates to message id's as follows:
> >
> >Take absolute value of SQLCODE
> >Represent that as a 5 digit number
> >If the leading digit is zero change it to an 'L'
> >Prepend 'SQ' and you have the message ID.
> >
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.