IBM Support

PM28319: DFHPI0002 A SEVERE ERROR (CODE X'0507') HAS OCCURRED IN MODULE DFHPITH.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • An E.C INVOKE WEBSERVICE fails with 'DFHPI0002 A SEVERE
    ERROR (CODE X'0507')' if the proxy is not properly
    configured. Message and dump is too severe for this problem.
    A suitable RESP and RESP2 value should be returned to the
    application instead.
    Trace shows:
    PI 0500 PITH  ENTRY CONVERSE
    WB 0700 WBCL  ENTRY PARSE_URL
    WB 0701 WBCL  EXIT  PARSE_URL/OK
    WB 0700 WBCL  ENTRY OPEN_SESSION          HTTPS,26DFCF20 ,
    WB 0713 WBCL  EVENT HOST_FOR_XWBOPEN_EXIT
    WB 0714 WBCL  EVENT PROXY_SET_BY_XWBOPEN  EXIT
    WB 0701 WBCL  EXIT  OPEN_SESSION/EXCEPTION PROXY_ERROR,
    PI 0507 PITH  *EXC* WB_CLIENT_SUPPORT_FAILURE CONVERSE
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message DFHPI0002 code x'0507' issued   *
    *                      unnecessarily.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application issued an EXEC CICS INVOKE WEBSERVICE command,
    this failed because there was a problem with the proxy server.
    CICS issued message DFHPI0002 indicating a severe error and
    a system dump was taken. This action was inappropriate and
    provided poor diagnostics to identify the underlying cause.
                                                                   .
    DFHPITH does not handle a number of 'soft' errors that may get
    returned by DFHWBCL. Had it done so, CICS could have issued
    message DFHPI0400 that is more specific in identifying the
    underlying cause of the problem.
    
    Keywords: FINFIX PK67227
    

Problem conclusion

Temporary fix

  • FIX TOO LARGE FOR RETAIN, THE FIX MAY BE AVAILABLE IN DLL
    

Comments

  • DFHPITH has been modified to handle a greater range of soft
    errors and issue DFHPI0400.  The invoking of the Web Services
    command will return invreq with resp2=23.
    
    
    The following documentation change will be made to the CICS
    Transaction Server for z/OS Messages and Codes manual
    ( GC34-6827-03 ), message DFHPI0400 will now read thus:
    
    DFHPI0400  DATE TIME APPLID TRANID  THE CICS
              PIPELINE HTTP TRANSPORT MECHANISM FAILED TO SEND A
              REQUEST BECAUSE  {THE REQUEST WAS USING AN
              INVALID HOST CODEPAGE |   THERE WAS A SOCKET
              ERROR |   THE URL WAS INVALID |   THE
              CONNECTION WAS CLOSED |   A SOCKET REQUEST
              TIMED OUT |   A PROXY ERROR WAS DETECTED |
               THERE WAS AN HTTP ERROR |   AN INVALID
              MEDIA TYPE WAS USED |   THERE WAS AN
              AUTHORIZATION PROBLEM |   THERE WAS A PROBLEM
              WITH THE CLIENT CERTIFICATE |   THERE WAS A
              URIMAP PROBLEM |   SSL IS NOT SUPPORTED IN
              CICS |   THERE WAS A ERROR WITH EXIT XWBAUTH |
                THE URIMAP IS DISABLED} .
    
    EXPLANATION:  The CICS pipeline HTTP transport mechanism
    was unable to successfully handle the outbound request
    because of one of the following reasons:
    
    o   The transport mechanism encountered a socket error.
    
    o   The connection that the request was trying to use was
        closed.
    
    o   A socket request timed out.
    
    o   A write request failed because an invalid codepage was
        used.
    
    o   The URL being parsed was invalid because an invalid
        escape character was encountered on the URI specified as
        input.
    
    o   There was a problem communicating with the HTTP proxy.
    
    o   There was an HTTP protocol error.
    
    o   An invalid media type was encountered.
    
    o   The current user is not authorized to submit the
        request.
    
    o   There was a problem with the client SSL certificate.
    
    o   The URIMAP that was used cannot be found or is invalid.
    
    o   SSL has not been enabled for CICS.
    
    o   There was a problem with global user exit XWBAUTH.
    
    o   The URIMAP that was used is disabled.
    
    SYSTEM ACTION:  The request is not sent. Error processing
    will continue.
    
    USER RESPONSE:  Depending on the error indicated in the
    message, ensure the host codepage you are using is correct
    or check for any socket errors indicated by examining any
    exception trace entries issued from sockets (SO) domain, or
    check that the URI specified as input does not contain any
    invalid characters or null delimiters, or check the XWBAUTH
    user global exit program for problems handling this request.
    
    DESTINATION:  CPIO
    
    MODULE:  DFHPITH
    
    XMEOUT PARAMETERS: date, time, applid,
    tranid, {1=the request was using an invalid host
    codepage, 2=there was a socket error, 3=the URL
    was invalid, 4=the connection was closed, 5=a
    socket request timed out, 6=a proxy error was
    detected, 7=there was an HTTP error, 8=an
    invalid media type was used, 9=there was an
    authorization problem, 10=there was a problem with the
    client certificate, 11=there was a URIMAP problem,
    12=SSL is not supported in CICS, 13=there was a
    error with exit XWBAUTH, 14=the URIMAP is disabled}
    
    
    The following documentation change will be made to the CICS
    Transaction Server for z/OS Application Programming Reference
    manual ( SC34-6819-03 ). A new RESP2 of 23 will be added for
    a returned condition of RESP INVREQ for command INVOKE
    WEBSERVICE.
    
    23 An unspecified transport or link failure occurred when
       attempting to use the pipeline. CICS issues a message to
       document the specific problem.
    

APAR Information

  • APAR number

    PM28319

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED UR3

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-07

  • Closed date

    2011-02-11

  • Last modified date

    2011-03-02

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

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

    UK64770 UK64771 UK64772

Modules/Macros

  •    DESEIPI  DESPICDU DESPIIS  DESPIIW  DESPIPM
    DESPITH  DFHEIPI  DFHMEPIC DFHMEPIE DFHMEPIK DFHPIAP  DFHPIISC
    DFHPIISI DFHPIIW  DFHPIIWA DFHPIIWM DFHPIIWT DFHPIPM  DFHPIPMA
    DFHPIPMM DFHPIPMT DFHPITGA DFHPITGM DFHPITGT DFHPITH  DFHPIUCC
    DFHPIUCD DFHPIUCL DFHPIUCO DFH28319
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK64770

       UP11/02/16 P F102

  • R501 PSY UK64771

       UP11/02/16 P F102

  • R502 PSY UK64772

       UP11/02/16 P F102

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

Document Information

Modified date:
02 March 2011