Pat,

I already posted this link that shows using QtmhRdStin and storing the data
in the IFS files.
http://www.fieldexit.com/forum/display?threadid=142

The only thing you need to change is the function that retrieves the
content length (easily done with APIs available, #GetEnv() just a wrapper
to the QthmGentEnv API).

The IFS part where it opens, writes and closes a stream file is also found
online (Scott Klement has some great examples online that a Google Search
will find.)
http://www.scottklement.com/rpg/ifs_ebook/

Hashtags aside (which you can change) it's all there for you.

Brad
www.bvstools.com

On Sat, Aug 1, 2015 at 4:36 AM, pat <p.caroti@xxxxxxxx> wrote:

Henrik Rützou <hr@...> writes:


<at> Bradley

just a little off topic remark.

the use of # and $ in names aren't allowed in RPGLE names in a number
of source file CCSID's since the CCSID 37 hex values equals other
characters
such as Ø and Å in CCSID 277 and the compiler uses the hex value.

Hi Henrik
i saw in your web site that you use YAJL
… I’m looking for a simple example that permit me to read the buffer with
“QtmhRdStin() “ and store in a Ifs file or use “yajl_tree_load_buf()” to
load QtmhRdStin()’s result for store in my db2 tables. Can you help me ?

Thanks
Pat

If also other people have some example that i'm looking for ... i would be
gratefull


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.