|
>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. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.