Yes MIchael:
OptionValueAddr is a pointer to the request
OptionValueLen is the request length.


El jue, 20 ago 2026 a las 16:17, Schmitt, Michael (<
[email protected]>) escribió:

> Does that mean that for this setting, the OptionValueAddr is the (address
> of) the address of the buffer, not the (address of) the address of the
> address of the buffer?
>
> For example:
>
> Option_value_pointer usage pointer
>
> Set option_value_pointer to address of buffer_area
> Call HWTHSET using option_value_pointer
>
> If so that would explain why the length is the buffer length, not 4.
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of salva
> Sent: Thursday, August 20, 2026 12:58 AM
> To: [email protected]
> Subject: Re: CWET with HWTH_OPT_REQUESTBODY
>
> Michael, setting  OptionValueLen = length of post body request, works for
> me.
>
> El jue, 20 ago 2026 a las 0:20, Schmitt, Michael (<
> [email protected]>) escribió:
>
> > Has anyone used the z/OS Client Web Enablement Toolkit with sending (e.g.
> > POST) body data in a single buffer, not using streaming?
> >
> > The documentation for doing so just says to set HWTH_OPT_REQUESTBODY to
> > the address of the buffer
> >
> >
> >
> https://www.ibm.com/docs/en/zos/3.1.0?topic=enabler-sending-data-server-non-rexx
> >
> >
> >
> https://www.ibm.com/docs/en/zos/3.1.0?topic=rexx-buffer-hwth-opt-requestbody-option
> >
> > So how does CWET know the LENGTH of the buffer?
> >
> > When I ask AIs, their first answer is to set a non-existent
> > HWTH_OPT_REQUESTBODY_LEN option.
> >
> > Their next answer is that it is set on the HWTHSET call itself. The
> > arguments to the call are:
> >
> > - ReturnCode
> > - ConnOrReqHandle
> > - Option (i.e. HWTH_OPT_REQUESTBODY)
> > - OptionValueAddr (address of the buffer)
> > - OptionValueLen
> > - DiagArea
> >
> > OptionValueAddr is always the address of the option value field or
> > structure. Which means that in linkage it is an address of an address.
> >
> > OptionValueLen is the length of that option value field or structure.
> >
> > AI says that the buffer length would be OptionValueLen, but the
> > documentation for HWTHSET specifically says " If the specified option is
> an
> > address or an SLST, the optionValueLen must be 4."
> >
> >
> >
> https://www.ibm.com/docs/en/zos/3.1.0?topic=enabler-hwthset-set-http-connection-request-options
> >
> >
> > You can set a content-length header, but there's nothing that indicates
> > CWET itself would be parsing the header you set. So I don't know how it
> can
> > build the body into the packet.
> >
> >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
> >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to