IBM Support

PH32683: CPIL IS NOT HANDLING THE TRIGGER DATA 21/02/23 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a message arrives on the queue and there is no
    SOAPJMS_targetService or targetService in the message in CICS
    5.2 the trigger data was taken . In CICS 5.5 this isn't the
    case anymore although the documentation says it should ( https:/
    /www.ibm.com/support/knowledgecenter/en/SSGMCP_5.5.0/configuring
    /web-services/dfhws_mq_uri.html ) .
    

Local fix

  • get the trigger data working again for requests that are of
    MQSTR format.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users with APAR PH27735.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: After application of the PTF for        *
    *                      PH27735 inbound web service requests    *
    *                      using IBM MQ may fail with message      *
    *                      DFHPI0112.                              *
    ****************************************************************
    CICS is receiving web service requests using IBM MQ.  These
    requests do not contain targetService or SOAPJMS_targetService
    properties.  In fact they don't contain any properties at all
    and so do not have an RFH2 header.  The messages are of type
    MQSTR instead of MQRFH2.  The expectation is that the target URI
    for the web service is determined by the trigger data set on the
    associated MQ queue.
    
    PH27735 incorrectly changed the code in DFHPILSQ so that CICS
    only used the trigger data as a default when an RFH2 header was
    present.  If the message does not contain an RFH2 header then
    the trigger data is no longer used.  This causes DFHPILSQ to
    fail to find the required URIMAP. Message DFHPI0112 is issued
    and the request is not processed.
    
    Additional Keywords:
    JMS  msgDFHPI0112  PI0112
    

Problem conclusion

  • UI71498 UI72214 UI71497 UI72215
    
    DFHPILSQ has been changed to reinstate the use of trigger data
    as a default value for the target URI for all message types.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH32683

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-15

  • Closed date

    2021-03-03

  • Last modified date

    2021-04-01

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

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

    UI74235 UI74236

Modules/Macros

  • DFHPILSQ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R200 PSY UI74236

       UP21/03/06 P F103 {

  • R300 PSY UI74235

       UP21/03/04 P F103 {

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.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5"}]

Document Information

Modified date:
02 April 2021