Re: How to retrieve second level text from message in SQL stored procedure

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Agreed, Peter. Still, I'm not convinced that the DB2_TOKEN_STRING or 
even the DB2_ORDINAL_TOKEN_n array (my interpretation) map reliably to 
MSGDTA. I mean, one of the tokens is the qualified file name. I might 
play with Marco's approach, with more substitution variables. I don't 
know if I can reproduce Dan's scenario.

*Regards*

*Vern Hamberg*

IBM Champion 2025 <cid:part1.IHYe2CSl.KtB0ualw@centurylink.net> CAAC 
(COMMON Americas Advisory Council) IBM Influencer 2023

On 6/13/2025 4:45 PM, Peter Dow wrote:
> Re (1), RTVMSG
>
> "is used in a CL program or REXX procedure to retrieve a specified 
> predefined message from a message file and to copy it into CL 
> variables. Substitution values can be specified in the MSGDTA 
> parameter (as a single character string containing one or more 
> concatenated message data fields) to replace the substitution 
> variables in the predefined message text."
>
> --
> *Peter Dow* /
> 909 793-9050
> petercdow@xxxxxxxxx
> /
>
> On 6/13/2025 8:15 AM, James H. H. Lampert via MIDRANGE-L wrote:
> > I may be sucking antimatter on this, but as I recall,
> >
> > (1) there are CL commands and/or system APIs to retrieve messages 
> > from the job's message queue, including the second-level text, and
> >
> > (2) SQL stored procedures don't *have* to be pure SQL.
> >
> > --
> > JHHL