IBM Support

PH14650: OUTBOUND CICS WEBSERVICE REQUEST RECEIVES 500 INTERNAL ERROR AFTER MIGRATING TO CICS TS 5.5.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After migrating from CICS TS 5.4 to CICS TS 5.5 outbound CICS
    Webservice Request receive a 500 Internal Error response.  In
    CICS TS 5.4 a 200 OK response was received.
    .
    In 5.5 with IPCS:
    0700 WBCL  ENTRY - FUNCTION(WRITE_REQUEST)
                       METHOD(POST)
                       SESSION_TOKEN(3A77F000 , 00000368)
                       PATH(3AD280F5 , 0000000F)
                       BODY(3A96D998_0000059A ,
                            00000000_00000000 ,
                            40404040_40404040)
                       MEDIATYPE(TEXT/HTML)
                       CHARSET(iso-8859-1)
    .
    2-0000  61D69989 87899581 A39699C4 81A381
            * /OriginatorData                 *
    .
    0700 CCNV  ENTRY - FUNCTION(VERIFY_IANA_CCSID)
                       IANA_CCSID(iso-8859-1)
    .
    .
    .
    In 5.4 with IPCS:
    0700 WBCL  ENTRY - FUNCTION(WRITE_REQUEST)
                       METHOD(POST)
                       SESSION_TOKEN(3A75F000 , 00000248)
                       PATH(3AC280F5 , 0000000F)
                       BODY(3A97E988 , 0000059A , 00000000)
                       MEDIATYPE(TEXT/HTML)
                       CHARSET(iso-8859-1)
    .
    2-0000  * /OriginatorData                 *
    3-0000  *<?xml version="1.0" encoding="UT*
      0020  *F-8" ?><SOAP-ENV:Envelope xmlns:*
      0040  *SOAP-ENV="http://schemas.xmlsoap*
      0060  *.org/soap/envelope/" xmlns:msg="*
    ...
      0580  *Body></SOAP-ENV:Envelope>       *
    .
    4800 CCNV  ENTRY - FUNCTION(VERIFY_IANA_CCSID)
                       IANA_CCSID(iso-8859-1)
    .
    In TS 5.5, the actual message you are trying to send isn't
    in the WRITE_REQUEST while it is in 5.4.
    .
    .
    This results in:
    .
    *nv:Body>.<env:Fault>.<faultstrin*
    *g><!.CDATA.dp:parse() error: Inc*
    *omplete markup or missing docume*
    *nt element at offset 0 .        *
    *                Original Message*
    *:..></faultstring></env:Fault>< *
    * /env:Body></env:Envelope>      *
    .
    Additional Symptom(s) Search Keyword(s): KIXREVBDB
    

Local fix

  • DFHWBCLI is still using 31-bit addresses and lengths so
    when it populates the WBCL_BODY parameter it copies data
    into the wrong offsets.  This causes the actual body data
    to not be sent.
    .
    Web Client Applications should really be updated to use EXEC
    CICS WEB commands.  If the applications were using the WEB
    API commands then they would not be exposed to this problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Request body can not get properly sent  *
    *                      out when using DFHWBCLI to send a POST  *
    *                      request.                                *
    ****************************************************************
    An application is using DFHWBCLI to send a POST request with a
    request body to a remote server. The address and length of the
    request body which are supplied by DFHWBCLI are 31-bit pointer
    and length, they are copied into internal variables as 31-bit
    values. But the DFHWBCL parameter BODY is a buffer made up of
    64-bit values. This results in the values ending up in the wrong
    fields in the DFHWBCL parameter BODY when DFHWBCL WRITE_REQUEST
    call is made. Accordingly, the request body does not get sent.
    

Problem conclusion

  • DFHWBCL has been changed to make sure the request body can be
    properly copied from DFHWBCLI to DFHWBCL work area and sent.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH14650

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-18

  • Closed date

    2019-08-16

  • Last modified date

    2019-09-01

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

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

Modules/Macros

  • DFHWBCL  DFHWBCLI
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R200 PSY UI64784

       UP19/08/17 P F908 ¢

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

Document Information

Modified date:
01 September 2019