IBM Support

PK50816: RECEIVING DFHPI0602 THE CICS SOAP HANDLER FAILED TO PARSE A MESSAGE. THE PARSER ERROR CODE IS 128.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • Trying to get a SOAP Requester Pipeline working on CICS 3.1 and
    getting the following error:
    .
    DFHPI0602 The CICS SOAP handler failed to parse a message. The
    parser error code is 128. The DFHPIEP return code is 10. The
    error was found at offset 441 into the message.
    .
    You'll get a INVREQ with RESP = 00000016, RESP2 = 00000006
    .
    The SOAP Fault TEXT will look like the following:
    .
    <SOAP-ENV:Body><SOAP-ENV:Fault xmlns=""><faultcode>SOAP-ENV:
    Server</faultcode><faultstring>Malformed SOAP message
    </faultstring><detail><cics:FaultDetail xmlns:cics=
    "http://www.ibm.com/software/htp/cics/fault"><cics:SoapParsing>
    <cics:PlisaxaRC>00000128</cics:PlisaxaRC><cics:Offset>00000441
    </cics:Offset><cics:PiepRC>00000010</cics:PiepRC>
    </cics:SoapParsing></cics:FaultDetail></detail></SOAP-ENV:Fault>
    </SOAP-ENV:Body>
    .
    The remote server is returning an HTTP 404 not found. This
    suggests that it doesn't recognize the path on the HTTP request
    from CICS (assuming the correct HTTP server is being driven).
    So we don't actually receive a SOAP response and then fail in
    the parsing stage because of this.  Now there is a small defect
    in the URI which is sent out. The target URI on the INVOKE
    WEBSERVICE request is :
    .
    http://99.99.999.99:99/PathName/PathName
    .
    The PATH here is /PathName/PathName. However, the PATH on the
    eventual socket SEND is /PathName/PathName?.  The ? is appended
    because when DFHPITH calls DFHWBCL for function WRITE_REQUEST it
    specifies QUERY_STRING(00000000 , 00000000).  This is a
    zero-length query string.  DFHPITH should not be doing this.
    Some HTTP servers may tolerate this and treat
    /PathName/PathName? as being identical to /PathName/PathName .
    It appears that the remote server does not tolerate this which
    is why it returns the HTTP 404.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHPI0602 when using no querystring.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An EXEC CICS INVOKE WEBSERVICE is issued for a request which
    does not contain a querystring. When the requester pipeline
    sends the request to the server, a question mark "?" is added to
    the request as an indicator that a querystring is to follow. As
    there is no querystring, the result is that the initial request
    is suffixed with the question mark. When the remote server
    processes the request, it is rejected because the request is not
    recognised with the question mark suffix. This results in
    message DFHPI0602 being produced.
    Additional keywords: MSGDFHPI0602 PI0602
    

Problem conclusion

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • Routines dfhpith_converse and dfhpith_send_request have been
    changed to only add the querystring indicator ("?") to the
    request if a querystring exists.
    

APAR Information

  • APAR number

    PK50816

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    400

  • Status

    CLOSED UR3

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-08-10

  • Closed date

    2007-11-29

  • Last modified date

    2008-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK31828

Modules/Macros

  •    DESPITH  DFHPITH
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK31828

       UP07/12/06 P F712

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 January 2008