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
