IBM Support

PK49879: INVOKE WEBSERVICE DOES NOT LOCATE URIMAP WHEN TARGET URL CONTAINS EXPLICIT PORT NUMBER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If EXEC CICS INVOKE WEBSERVICE is used to request a webservice
    whose URI contains an explicit port number, the corresponding
    URIMAP with USAGE(CLIENT)  is not located. The LOCATE_URIMAP
    function of DFHWBCL does not support a PORT parameter to
    distinguish the correct URIMAP. Furthermore, DFHWBCL
    OPEN_SESSION does not allow its parameters (such as SCHEME,
    HOST, or PORT) to override those obtained from the URIMAP.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: EXEC CICS INVOKE WEBSERVICE command     *
    *                      fails to locate the correct URIMAP.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a WEBSERVICE is deployed with a URI that contains a
    specific port number (separated from the hostname by
    a colon), and a URIMAP exists that corresponds to that URI,
    the EXEC CICS INVOKE WEBSERVICE command does not successfully
    locate the URIMAP.
    Therefore the INVOKE command does not merge any attributes
    (such as CIPHERS or CERTIFICATE) from the URIMAP into the HTTP
    request sent to the web service.
    The DFHWBCL PARSE_URL function used by the pipeline HTTP handler
    splits the specified URI into its constituent parts, so it
    removes the colon-delimited port number from the hostname and
    saves it in a different output parameter. But the DFHWBUR
    LOCATE_URIMAP function does not contain an input parameter in
    which the port number can be specified, so the port number is
    ignored and the correct URIMAP is not found.
    
    Additional Keyword: wbur_not_found not_found
    

Problem conclusion

  • DFHWBUR has been changed to accept a port number as input, and
    DFHPITH has been changed to pass the port number obtained from
    the specified URI in the new parameter.
    The formatted dump of a URIMAP specified with USAGE(CLIENT) now
    displays the port number.
    
    The CICS Transaction Server for z/OS Version 3 Release 2,
    Supplementary Data Areas manual, GC34-6864-00 has been updated
    to add a new field, ume_portnumber, to the URI_MAPPING_ELEMENT
    (UME) structure as follows - the 3 character 'reserved' field
    at offset X'44' (following the existing field
    'ume_certificate_label_ptr') has been replaced by the following:
    Offset  Type          Len   Name (Dim)          Description
     Hex
    (44)    UNSIGNED      2     ume_portnumber      Port number
    (46)    UNSIGNED      1     *                   reserved
    
    The CICS Transaction Server for z/OS Version 3 Release 2,
    Diagnosis Reference manual, GC34-6862-00 has been updated
    to add the PORT parameter to the list of WBUR optional
    input parameters for LOCATE_URIMAP.
    On page 1713 ('WBUR gate, LOCATE_URIMAP function') the PORT
    parameter has been added, after the HFSFILE parameter, as
    follows:
    
    Input Parameters
      HOST
      PATH
      HFSFILE
         Optional Parameter
      PORT
         Optional Parameter
      REDIRECTION_LOCATION
         Optional Parameter
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK49879

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-27

  • Closed date

    2007-09-20

  • Last modified date

    2007-10-02

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

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

    UK29471

Modules/Macros

  •    DESEIQWB DESEIWB  DESPICDU DESPILSQ DESPISC
    DESPITH  DESPIWR  DESSOIS  DESWBAP  DESWBCL  DESWBDM  DESWBRP
    DESWBRQ  DESWBRQF DESWBSR  DESWBUR  DESWBXM  DFHAMWB  DFHEIQWB
    DFHEIWB  DFHPILSQ DFHPISC  DFHPITGA DFHPITGM DFHPITGT DFHPITH
    DFHPIWR  DFHSOIS  DFHWBAP  DFHWBAPF DFHWBCL  DFHWBCLA DFHWBCLB
    DFHWBCLJ DFHWBCLM DFHWBCLT DFHWBCLV DFHWBDM  DFHWBDUF DFHWBRP
    DFHWBRQD DFHWBRQS DFHWBSR  DFHWBUR  DFHWBURA DFHWBURC DFHWBURM
    DFHWBURT DFHWBXM
    

Publications Referenced
GC34686200GC34686400   

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK29471

       UP07/09/27 P F709

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 October 2007