Re: z/OS Client Web Enablement Toolkit
Hi Mark, I saw you were on copy to the response I gave to Dan Kelosky, pointing to the new toolkit github repo: https://github.com/IBM/zOS-Client-Web-Enablement-Toolkit But to address the shipped samples question, OA57475 is currently open and will be used to ship the re-worked samples. Galina -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS Client Web Enablement Toolkit sample
Hi Steve, I'm one of the developers working on z/OS Client Web Enablement Toolkit. The updated connection URI is https://soa.smext.faa.gov and the updated request URI is /asws/api/airport/status/jfk The connection type has been upgraded from HTTP to HTTPS. If you do not utilize AT-TLS, or if there is not a AT-TLS policy enabled for the connection to this FAA server, you may need to set additional SSL/TLS support options in your application. These options include turning on SSL/TLS, and telling toolkit the location of your certificate store (HWTH_OPT_USE_SSL, HWTH_OPT_SSLKEY, HWTH_OPT_SSLKEYTYPE options). See this link for more details: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieac100/ieac1-cwe-http-options.htm We understand that having a working sample is a priority to you and we are working on getting the sample updated as soon as we possibly can. We hope to have something shipped very soon. Galina Gorelik -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
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: HWTJSRCHSEARCHSTRINGADDRPTRDS 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
