IBM Support

PI51310: DFHPI0730 AN ATTEMPT TO REGISTER A REMOTE WEB SERVICE AS A PARTICIPANT IN UNIT OF WORK -X'0000000000000000' HAS FAILED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We can see from the web services trace CICS is sending a Web
    Service request containing a WS-AT Coordination context to WAS.
    WAS sends a wscoor Register back to CICS which is a one-way
    request which is sent OK. WAS then carries on processing the
    inbound request. In the meantime, CICS responds back to WAS
    with a SOAP Fault that relates to the Register Request:
    <soap:Fault xmlns=""><faultcode>wscoor:ContextRefused
    </faultcode><faultstring>WSAT Registration Failed</faultstring>
    Before WAS allows the web service request to return it will
    check that the response to the Register has been received and
    will wait for up to 30 seconds.  Since WAS doesn't receive a
    RegisterResponse it throws an exception (after the 30 second
    wait) and results in the WSWS3035E message.
    The reason registration failed is because the instance count
    within the token in the registration message does not match the
    instance count within the block of tokens managed by the PI
    domain. From a CICS standpoint, we can see a long running task
    is issuing INVOKE SERVICE commands. At some point in the past,
    it issued an INVOKE SERVICE command who PIPELINE used WS-AT and
    obtained a context token that is managed by DFHPIIM. The token
    is stored in a small control block addressed by the PI domain
    XM token for the task. The token should get released and
    cleared when syncpoint completes or at the end of the task. It
    appears that the token was been released successfully as the
    token set indicates that particular token has been reused many
    times since it was allocated to this task. What has not
    happened is for the token to be removed from the PI domain XM
    block.
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An INVOKE SERVICE command fails         *
    *                      with DFHPI0730.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A CICS transaction makes an INVOKE SERVICE call to a web service
    on a non-CICS system with WS-AT configured.  No recoverable
    updates are performed by the remote system.
    As a result, when the next CICS syncpoint takes place, the web
    service provider responds to the request to prepare with a read
    only response.  CICS sets the Recovery Manager link as
    unnecessary and clears the information associated with the link
    as it does not need to communicate with the remote system for
    the unit of work again.  However, the context token in the
    Pipeline Domain control block is not cleared.
    If the task makes a subsequent INVOKE SERVICE call to the same
    web service it will use the residual context token, which will
    cause the WS-AT registration to fail as it is no longer valid.
    This causes the INVOKE SERVICE call to fail with an INVREQ
    condition and message DFHPI0730 to be issued with a uowid of
    zeros.
    
    Additional keywords: msgDFHPI0730 PI0730 WSAT
    

Problem conclusion

  • DFHPIRM has been modified to clear the context_token field in
    the pi_tx_control_block in the scenario described above.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI51310

  • 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 / Xsystem

  • Submitted date

    2015-10-27

  • Closed date

    2016-02-24

  • Last modified date

    2016-04-05

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

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

    PI56776 UI35612

Modules/Macros

  • DFHPIRM
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UI35612

       UP16/03/12 P F603

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

Document Information

Modified date:
05 April 2016