Requires Free Membership to View
When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by IT professionals today working with data center technologies.
Margie Semilof, Editorial DirectorYou are quite correct in saying that you have to use the MVS sockets interface to get TCP/IP traffic out of CICS.
However, you are quite lucky in that the SOAP SupportPac (available from the CICS Web page) may offer some assistance. Why is this you might well ask?
The way outbound SOAP (from CTS 2.2 only) flows from CICS is via an HTTP flow, and so we have externalized a SMALL part of some of the CICS internal functions, just enough to get this function working. This is via a Commarea module (DFHWBCLI) that has a defined interface of minimal function but it might well do what you want. An early version of this module is in the SupportPac but the final version will be available in APAR PQ72017 when it will be fully supported.
This interface might be enough for you to supply a properly formatted HTTP flow and get back a properly-formatted response (the length of which will be governed by the relevant HTTP header setting). You use DFHWBCLI and its Commarea via an XC LINK and there are some structures in the SupportPac that detail this layout.
Don't use the SupportPac version of DFHWBCLI for real, wait until the final version is available via the APAR before moving into production.
Robert Harris
Inventor
CICS Technical Strategist -- CICS expert at Search390.com
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.
This was first published in May 2003
Data Center Strategies for the CIO