Hello Galina, I am reading IBM manuals for about 40 years, and it is hard to understand the flow of the interface calls from the manual. I first wrote a rexx program just to understand the flow. It also helped me to understand why assembler calls are not executing well. I am not sure this is a proper tool for parsing a complex, array structured JSON. But,... I already mastered the service. a sample for the next users may help them.
Best, ITschak On Wed, Aug 22, 2018 at 4:42 AM Doug <dsh...@bellsouth.net> wrote: > Galina, > Yes, it would be worth providing sample code for batch assembler, CICS > assembler, CICS COBOL , CICS REXX , TSO REXX and ‘how to’ direction for > Liberty and eclipse. Sorry if I missed some, feel free to chime in. > By sample code we mean fully functional examples not a small KC tribute to > a hint and click for KC to direct us to yet another tiny hint. > Just my 2cents.. > Most of us are swamped with day to day problems and don’t have the extra > band width to explore as we did in days gone by. > Best Regards, > Doug > > . > > On Aug 21, 2018, at 15:08, Galina Gorelik <gore...@us.ibm.com> wrote: > > Hi ITschak, > > I’m part of the team that develops the z/OS JSON parser. From your > previous post, it appears you have resolved the issue you were experiencing. > As you pointed out, we do not provider assembler samples, so you have to > connect the dots between the following three things: > 1. IBM Knowledge Center, z/OS JSON parser: Description of > HWTJ_SEARCHTYPE_GLOBAL that distinguishes between the REXX and non-REXX > parameter content: for the first “name” that exactly matches the > SearchString for REXX or the string pointed to by the SearchStringAddr > parameter for non-REXX. > 2. IBM Knowledge Center, z/OS JSON parser: Linkage considerations for > assembler language programming that specifies: Register 1 must contain the > address of a parameter list that is a list of consecutive words, each > containing the address of a parameter to be passed. > 3. HWTJIASM macro: HWTJSRCH input parameters section where the > HWTJSRCHPARMLIST DSECT shows that these are all pointers to the parameters, > in the case of the SearchStringAddr parameter, the DS indicates that this > is a pointer to the address: HWTJSRCHSEARCHSTRINGADDRPTR DS A Address > of SearchStringAddr > > Is there additional information that can be added that would have helped > more? Or verbiage that should be altered? > > Galina > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
