× 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.



Hello,

yajl_stdin_load_tree() provides an option that can be used to write it to a file.  This is one of the parmeters you pass to the procedure...

If you want to put it into a variable instead of a file, what you would do is:

1) Read stdin yourself with the QtmhRdStin() API from IBM.   Use this to load it into a variable.

2) Write your variable to the log file.

3) Pass the variable to yajl_string_load_tree (or yajl_buf_load_tree if that works better)

-SK


On 10/15/2020 5:56 PM, Moses Nang (IMS Morton Grove) wrote:
Prior to parsing the json data that is in the stdin using yajl_stdin_load_tree, is there a way for me to move the complete json data (i.e. name/value pairs, curly braces, square brackets, etc.) to one variable before I parse the data into the child nodes. I eventually want to save that "raw" json data to a field in log table.

Thanks,
Moses Nang

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution, or copying of this email or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this email in error, please immediately notify us by calling our Network Operations Center at +1 888 697 2443.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.