EIBRESP=16 EIBRESP2=107 from EXEC CICS INVOKE WEBSERVICE

Question & Answer

Question

An EXEC CICS INVOKE WEBSERVICE command in a new requestor type webservice application returns EIBRESP 16 and EIBRESP2 107. I turned on CICS auxtrace with components EI=(1-2), AP=(1-2), PI(1-2), SO(1-2), and WB (1-2) using CETR and the programmer ran the transaction. I found the following exception trace entry:

 PI 0601 PIIW EXIT  - FUNCTION(INVOKE_WEBSERVICE) RESPONSE(EXCEPTION)
 REASON(UNEXPECTED_NORESP) SOAP_FAULT_RESP1(3) SOAP_FAULT_RESP2(6B)

Why does CICS Transaction Server for z/OS (CICS TS) consider the XML to be non-SOAP compliant and why does it seem to be making a "NORESP" (no response?) claim? There was definitely a response, as evidenced by the contents of DFHRESPONSE.

Answer

The SOAP_FAULT_RESP1(3) SOAP_FAULT_RESP2(6B) is usually caused by an invalid MEDIATYPE in the soap response received from the server.

Trace shows:

 WB 0701 WBCL  EXIT - FUNCTION(READ_RESPONSE) RESPONSE(OK) 
 SET_BUFFER(00000000 , 000000000 , 00000100) MEDIATYPE(application/xml)
 CHARSET(UTF-8)

The trace eyecatcher shows:

 *....application/xml
 *
 *    UTF-8
 *    ....Unsupported Media Type

For SOAP 1.1: MEDIATYPE must be text/xml

For SOAP 1.2: MEDIATYPEmust be application/soap+xml

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Web Services","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Was this topic helpful?

Document Information

Modified date:
13 November 2017

UID

dwa1410774

Tips