Troubleshooting
Problem
You receive Resp 16 and Resp2 107 when using the CICS Transaction Server for z/OS (CICS TS) application programming interface (API) command EXEC CICS INVOKE WEBSERVICE. You are using SOAP version 1.1.
Cause
Content-Type = TEXT/PLAIN was specified in the HTTP header in the response from the Webservice. However, SOAP V1.1 is based on XML specification. So, this causes a mismatch between the charset value in HTTP header and the SOAP Envelope encoding type.
The following descriptions of RESP16 and RESP2 107 values can be found under INVOKE SERVICE in the CICS TS documentation:
RESP : 00000016 means INVREQ
RESP2: 00000107 means Either the generated SOAP request message was not a valid SOAP message, or the SOAP response message was not a valid SOAP message.
The following descriptions of RESP16 and RESP2 107 values can be found under INVOKE SERVICE in the CICS TS documentation:
RESP : 00000016 means INVREQ
RESP2: 00000107 means Either the generated SOAP request message was not a valid SOAP message, or the SOAP response message was not a valid SOAP message.
Diagnosing The Problem
Capture a dump of the failing transaction with internal trace started, at least a 4K internal trace table size and all components set to standard level 1 tracing except EI, PG, PI, SO, and WB which should be set to 1-2. After running the failing transaction use CEMT P SNAP to take a dump of CICS.
Format the dump with IPCS command VERBX DFHPDxxx 'TR=2' where xxx is 660 and 670 for CICS TS V4.1 and V4.2 respectively, and 680, 690, and 700 for CICS TS V5.1, V5.2, and V5.3 respectively. You can see the response coming back into CICS in the socket function(receive) trace entry:
0202 SOCK EXIT - FUNCTION(RECEIVE) RESPONSE(OK) RECEIVE_BUFFER(25788000 , 0000070B , 00001000)
Looking at the data coming in you see the following:
*HTTP/1.1 200 OK..Date: Mon, 03 A*
*ug 2009 15:08:56 GMT..Server: IB*
*M_HTTP_Server/6.0.2.25 Apache/2.*
*0.47 (Unix)..Cache-Control: max-*
*age=28800..Expires: Mon, 03 Aug *
*2009 23:08:56 GMT..Keep-Alive: t*
*imeout=10, max=100..Connection: *
*Keep-Alive..Transfer-Encoding: c*
*hunked..Content-Type: text/plain* <-Should be Text/XML
*; charset=ISO-8859-1..Content-La* <-Should be UTF-8
*nguage: en-US....5ae..<?xml vers*
*ion="1.0" encoding="UTF-8"?>.<so* <-SOAP Envelope Encoding
*apenv:Envelope xmlns:soapenv="ht*
Format the dump with IPCS command VERBX DFHPDxxx 'TR=2' where xxx is 660 and 670 for CICS TS V4.1 and V4.2 respectively, and 680, 690, and 700 for CICS TS V5.1, V5.2, and V5.3 respectively. You can see the response coming back into CICS in the socket function(receive) trace entry:
0202 SOCK EXIT - FUNCTION(RECEIVE) RESPONSE(OK) RECEIVE_BUFFER(25788000 , 0000070B , 00001000)
Looking at the data coming in you see the following:
*HTTP/1.1 200 OK..Date: Mon, 03 A*
*ug 2009 15:08:56 GMT..Server: IB*
*M_HTTP_Server/6.0.2.25 Apache/2.*
*0.47 (Unix)..Cache-Control: max-*
*age=28800..Expires: Mon, 03 Aug *
*2009 23:08:56 GMT..Keep-Alive: t*
*imeout=10, max=100..Connection: *
*Keep-Alive..Transfer-Encoding: c*
*hunked..Content-Type: text/plain* <-Should be Text/XML
*; charset=ISO-8859-1..Content-La* <-Should be UTF-8
*nguage: en-US....5ae..<?xml vers*
*ion="1.0" encoding="UTF-8"?>.<so* <-SOAP Envelope Encoding
*apenv:Envelope xmlns:soapenv="ht*
Resolving The Problem
Specify TEXT/XML for Content-Type when using SOAP 1.1. Charset value in HTTP header should match SOAP Envelope Encoding.
[{"Type":"MASTER","Line of Business":{"code":"LOB70","label":"Z TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"ARM Category":[{"code":"a8m3p000000LRasAAG","label":"CICS Transaction Server"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"5.2.0;5.3.0;5.4.0;5.5.0;5.6.0;6.1.0;6.2.0"}]
Product Synonym
CICS/TS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
24 August 2026
UID
swg21398010