PM77833: WSA ACTION FROM WSDL OPERATION IS USED IN CASE OF A WEBSERVICE APPLICATION FAILURE WITH CICS OR USER ABEND

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a CICS WEBSERVICE application abends with CICS or USER abend
    or if an error in PIPELINE processing occurs, then CICS
    generates a SOapFault and uses the fault from WSDL-Operation.
    But wsa action from WSDL Operation is definitely not the right
    action, leading to wrong error handling in client processing.
    For example, after an abend ASRA, the response file contains
    the wsa:action: "http://xml.../FunctionTestService/v03/
    FunctionTestV03/getName/F/Fault/AccessDeniedException".
    But that's wrong, because there has been a CICS abend ASRA,
    not AccessDeniedException .
    CICS should rather send the wsa:action: "http://www.w3.
    org/2005/08/addressing/soap/fault" as recommended in
    WSAddressing specification and should not use a modelled
    fault from WSDL.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: WS-Addressing generates wrong fault     *
    *                      action when Webservice application      *
    *                      fails with CICS or user abend.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When CICS webservice application abends with CICS or User
    abend, or if an error in PIPELINE processing occurs,
    CICS generates a SoapFault and uses the fault action
    from WSDL Operation. The client uses information in
    action-header for further processing, the wrong action leads
    to confusion and to incorrect error handling. For CICS problems
    or User abends, CICS should use a default action
    (http://www.w3.org/2005/08/addressing/soap/fault) described
    in WS-Addressing Specification (http://www.w3.org/TR/
    ws-addr-soap/). But should never use a fault from WSDL.
    

Problem conclusion

  • DFHPISF and DFHPIA1 have been changed to enhance the EXEC
    CICS SOAPFAULT processing so that CICS can detect whether the
    Fault is for a CICS reported problem or not. If it is, the
    subsequent WS-Addressing processing returns the default
    action defined in WSA Specification.
    
    CICS Transaction Server for z/OS Version 4 Release 2
    Web Services Guide, SC34-7191-02 has been altered in
    Chapter 6('Creating the web services infrastructure')
    under the heading of 'Containers used in the pipeline'
    to include a new context container that indicates the
    type of SOAP fault CICS creates.
    
    The description of the new container has been appended
    to the end of section 'Context containers':
    
    "DFHWS-FAULT container
    
    DFHWS-FAULT is a container of DATATYPE(BIT) that holds
    information about the type of SOAP fault CICS generates.
    
    The container holds a binary fullword that indicates the
    fault type that can be used in further processing for a
    web service response:
    
    1
    The most recent SOAP fault was for a CICS fault (for
    example, CICS or user abend).
    
    2
    The most recent SOAP fault was for an application fault.
    
    The container is deleted when you issue the EXEC CICS
    SOAPFAULT DELETE command. If a second or new SOAP fault
    is created, CICS updates the new container appropriately.
    
    You cannot change the contents of this container."
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM77833

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-27

  • Closed date

    2013-05-07

  • Last modified date

    2013-06-04

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

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

    PM82976 UK94182

Modules/Macros

  •    DFHPIA1  DFHPIPM  DFHPISF  DFHPISN
    

Publications Referenced
SC34719102        

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UK94182

       UP13/05/17 P F305

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

CICS Transaction Server

Software version:

4.2

Reference #:

PM77833

Modified date:

2013-06-04

Translate my page

Machine Translation

Content navigation