scottklement.com

Looking at the sample data it looks as if an easy approach would be to use DATA-GEN with the YAJL generator to place the json in a varchar variable, then add the CR/LF (or whatever you need) and write it out to the IFS. Could easily buffer it in a large varchar field.

Basically you will need to use http_xproc to declare the procedure to add the custom headers. This is called _before_ you call the http_... function to invoke the web service. The http API will then call your routine while building the request. Here's a snippet of what I use to invoke Zoom APIs. htt...

Your option 1 includes an incorrect assumption. You CAN have the same name in multiple DS you just have to specify them as qualified. In fact that is exactly the way I have handled this scenario in the past.

This is what I've been using with the Zoom APIs. Simple but it does the job. // DSs for re-mapping of Zoom timestamp to RPG compatible format // Initial format is yyyy-mm-ddThh:mm:ssZ (e.g. 2020-05-08T19:41:44Z) // which appears to be ISO 8601 Dcl-ds zoomTimestamp Qualified; date char(10); *n char(1...

I notice that you are still specifying to copy in the YAJL header files and referencing the binding directory. Can't think why that would cause issues but ...

Sorry - off the top of my head I have no clue. Will try to take another look at it later on.

Just out of interest, what happens if you just call YAJLINTO from the command line? Can the system find it then?

If you are not that familiar with the workings of YAJL then why not make life simpler for yourself and use DATA-INTO with the YAJLINTO parser? You've already got the DS (or close to it) so it should be easy. If you are not familiar with DATA-INTO I have written several articles on the topic and most...