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

There was a mistake:

AND MESSAGE_ID = :wMsg;

About the token string, this is from IBM docs:

DB2_TOKEN_STRING
Returns a X'FF' delimited string of the tokens for the specified diagnostic.

So, once you have the single tokens in an array just split the single
tokens and use them in reverse order.

I don't think IBM is doing something very diffrent when populating job log.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno sab 14 giu 2025 alle ore 00:33 Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> ha scritto:

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.