×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Just wondering if there is a relatively easy way to retrieve the message "Cause" from within the RPG program?
The "Cause" is usually where the issue is described - "the exact subfield for which the error was detected is..."
I would like to use this as output in my text logs.
Example:
Additional Message Information
Message ID . . . . . . : RNX0356 Severity . . . . . . . : 50
Message type . . . . . : Escape
Date sent . . . . . . : 07/16/19 Time sent . . . . . . : 11:35:04
Message . . . . : The document for the DATA-INTO operation does not match
the RPG variable; reason code 4.
Cause . . . . . : While parsing a document for the DATA-INTO operation, the
parser found that the document does not correspond to RPG variable "json"
and the options do not allow for this. The reason code is 4. The exact
subfield for which the error was detected is
"json.orders(1).promotions.applied_promotions". The options are "doc=file
case=convert allowextra=yes countprefix=count_". The document name is
/apis/Mirakl/046/GetOrdersReady_Response_0.json; *N indicates that the
document is not an external file. The parser is 'YAJLINTO'. *N indicates
that the parser is a procedure pointer.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
