I've copied this WSDL to a file in the HFS and tried to run DFHWS2LS, but it fails with an error DFHPI9523E (see details below). The only success I've had with DFHWS2LS is with a test service I found at
I note that all the Web Assistant examples that I've seen assume a single operation at the service, but the WSDL standard allows any number of operations and my SOATesting service currently has two. I'm trying to access operation SOATest1, but I can't see anywhere where the operation is specified in the DFHWS2LS parameters. Yet how can it create a binding file without knowing this?
Can anybody with experience linking CICS and ASP.NET services help? I don't want to believe that IBM programs cannot talk to Microsoft's major platform. There MUST be a parameter that I don't understand.
Details of the error: -
DFHPI9523E An unexpected error occurred whilst processing file "/u/ibmuser/manajazz/WST1.wsdl". The problem is: "WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'http://www.jazzsoftware.co.nz/SOATesting/Service1.svc?xsd=xsd1', relative to '/u/ibmuser/manajazz/WST1.wsdl'.: java.net.UnknownHostException: www.jazzsoftware.co.nz".
Joined: 20 Oct 2014 Posts: 8 Location: Auckland, New Zealand
I did eventually succeed in communicating between CICS and Microsoft, although not without a lot of technical help from IBM support. Have a look at
particularly Appendix E.
If not sure if this will address your need to send a CICS screen to one of your portals. If the introductory document above looks interesting, then you may want to delve into more detail about Web Services/Service Oriented Architecture at
This is part of the documentation of MANASYS Jazz. If you need more information on this project, look at
Along the way we found various faults in my zOS set-up that had to be fixed: these details are not published in the above documents, but I'd be happy to discuss what we found if you contact me directly. My email is
[e-mail removed to avoid spamming. Use private message for initial communication]