IBM Support

PI71031: WEBSERVICES FAIL WITH MESSAGES DFHPI0401, DFHPI0503, DFHPI0997, AND "BASIC AUTHENTICATION FAILURE" HTTP 401 RESPONSE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running in an environment with both SSL and non-SSL
    webservices, and after application of the PTF UI40033 for APAR
    PI64504, there are failures.  These can present as messages:
    
    DFHPI0401 applid tran The CICS pipeline HTTP transport
       mechanism failed to send a response or receive a request
       because the connection was closed.
    DFHPI0503 applid tran The CICS Pipeline Manager has failed to
       send a response on the underlying transport TRANSPORT: HTTP,
       PIPELINE: PIPE
    DFHPI0997 applid tran PIPE The CICS pipeline manager has
       encountered an error: unidentified problem.
    .
    or with trace entries:
    
    PI 0A27 PIIS  *EXC* TRANSPORT_FAILED
    SO 080C SOSE  *EXC* SYSTEM_SSL_ERROR      GSK_ERR_SOCKET_CLOSED,
       SECURE_SOC_INIT,EXCEPTION,CONNECTION_CLOSED,1A4 (for SSL)
    AP 4522 WBXN  *EXC* RECEIVE_ERROR
    .
    You have configured your webservices with Basic Authentication.
    You are using the string : 'Authorization: Basic
    USERID:PASSWORD' (with the credential string possibly encoded),
    but the trace data shows that you receive a 401 response of
    "Basic Authentication Error".
    
    
    
    
    This also causes a SOAP reponse message to change from
    
    <SOAP-ENV:Envelope
     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP-ENV:Body>
    
          :
          :
          :
          :
    
       </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    
    
    to
    
    
    <soapenv:Envelope
     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
        <SOAP-ENV:Body>
    
          :
          :
          :
          :
    
       </SOAP-ENV:Body>
    </soapenv:Envelope>
    
    
    which wil cause a parsing error on the client.
    
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s): KIXREVDAM
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All CICS Users with APAR PI64504 applied.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Namespace prefix SOAP-ENV is used in                         *
    * XML response messages from CICS without                      *
    * a corresponding namespace definition.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After applying PTF UI40033 for APAR PI64504 various parsing
    errors are seen.
    CICS receives an inbound SOAP message which does not use
    namespace prefix SOAP-ENV. DFHPISN parses the message and
    invokes an apphandler program that causes a context switch to
    occur.
    On return from the apphandler program, DFHPISN recreates
    the DFHWS-XMLNS container with the namespace information
    from the input message.
    CICS builds a response Body element with namespace prefix
    SOAP-ENV. As this is not defined in the DFHWS-XMLNS container,
    CICS creates a response message that is not well formed.
    After the response is sent, the badly formed XML causes errors
    in subsequent processing.
    

Problem conclusion

  • UI40033
    DFHPISN is changed so it does not recreate the DFHWS-XMLNS
    container on return from an apphandler program.
    The XML response message from CICS is well formed with
    namespace prefix SOAP-ENV correctly defined.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71031

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-20

  • Closed date

    2016-11-22

  • Last modified date

    2017-01-26

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

    PI70445

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

    UI42813

Modules/Macros

  • DFHMLJS  DFHMLTF  DFHPIA1  DFHPIAD  DFHPIAT  DFHPICA  DFHPICC
    DFHPIDM  DFHPIDSH DFHPIDUF DFHPIII  DFHPIIW  DFHPIJG  DFHPIJP1
    DFHPIJP  DFHPIJS  DFHPIJW  DFHPILN  DFHPIMM  DFHPIPL  DFHPIPM2
    DFHPIPM  DFHPIPS  DFHPIRE  DFHPIRI  DFHPIRL  DFHPIRM  DFHPIRN
    DFHPIRS  DFHPISC  DFHPISF  DFHPISN  DFHPIST  DFHPITC1 DFHPITC2
    DFHPITC3 DFHPITC  DFHPITE  DFHPITH  DFHPITL  DFHPITQ  DFHPITRI
    DFHPITS  DFHPIUE  DFHPIWR  DFHPIWT  DFHPIXI  DFHPIXM  DFHPIXO
    DFHWSADH DFHWSATR
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI42813

       UP17/01/03 P F612 {

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":"5.3","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":"5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 January 2017