Yes, I have set verbose on and I see the headers and response.
As I said, it shows the first and last 40 bytes of request body and the 
equivalent in hex.
When I compare the hex values to a 'hex on' listing of the json payload in a 
dataset / USS file, they are identical.
Does this mean the translate of EBCDIC to ASCII didn't work..?

– Vignesh
Mainframe Infrastructure

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
ITschak Mugzach
Sent: 11 June 2019 09:39
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Client Web Enablement Toolkit

If you set verbose mode a trace is written to sysout, so you will be able to 
see the http headers and response.

ITschak

בתאריך יום ג׳, 11 ביוני 2019, 11:29, מאת Sankaranarayanan, Vignesh ‏<
vignesh.v.sankaranaraya...@marks-and-spencer.com>:

> Code order --
>
> ReturnCode = -1
> DiagArea. = ''
> address hwthttp "hwthset ",
>                 "ReturnCode ",
>                 "RequestHandle ",
>                 "HWTH_OPT_REQUESTMETHOD ",
>                 "HWTH_HTTP_REQUEST_POST ",
>                 "DiagArea."
>
> ReturnCode = -1
> DiagArea. = ''
> address hwthttp "hwthset ",
>                 "ReturnCode ",
>                 "RequestHandle ",
>                 "HWTH_OPT_TRANSLATE_REQBODY ",
>                 "HWTH_XLATE_REQBODY_E2A ",
>                 "DiagArea."
>
> ReturnCode = -1
> DiagArea. = ''
> JSONPayload = '{"json":"yes"}'
> address hwthttp "hwthset ",
>                 "ReturnCode ",
>                 "RequestHandle ",
>                 "HWTH_OPT_REQUESTBODY ",
>                 "JSONPayload ",
>                 "DiagArea."
>
>
> - Vignesh
> Mainframe Infrastructure
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On 
> Behalf Of Sankaranarayanan, Vignesh
> Sent: 11 June 2019 09:22
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Client Web Enablement Toolkit
>
> Hi,
>
> It looks like I'm unable to translate the request body from EBCDIC to 
> ASCII (in REXX), when using the HWTH_OPT_TRANSLATE_REQBODY with a 
> value of HWTH_XLATE_REQBODY_E2A .. in the address hwthttp call.
>
> I'm using code based on SYS1.SAMPLIB(HWTHXRX1).
> I see a HTTP 400 error saying Bad request, and in the request body, I 
> see the hex values that were/was sent.
> It looks identical to what I see when I do a 'hex on' in ISPF against 
> the file with the payload (request body) open in 3.17 (USS).
>
> Any thoughts? All returning RC 0...
>
> - Vignesh
> Mainframe Infrastructure
>
>
> MARKSANDSPENCER.COM
> ________________________________
> Unless otherwise stated above:
> Marks and Spencer plc
> Registered Office:
> Waterside House
> 35 North Wharf Road
> London
> W2 1NW
>
> Registered No. 214436 in England and Wales.
>
> Telephone (020) 7935 4422
> Facsimile (020) 7487 2670
>
> www.marksandspencer.com
>
> Please note that electronic mail may be monitored.
>
> This e-mail is confidential. If you received it by mistake, please let 
> us know and then delete it from your system; you should not copy, 
> disclose, or distribute its contents to anyone nor act in reliance on 
> this e-mail, as this is prohibited and may be unlawful.
>
> ----------------------------------------------------------------------
> 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
>

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

Reply via email to