A fix is available
APAR status
Closed as program error.
Error description
You are using a CICS requester program that calls a service provider to an external platform (Windows). The service on windows is a Windows WCF Services. You want to use WS Atomic transaction (WS-AT) for the use of two Phase commit. The INVOKE SERVICE fails because there is no URI supplied resulting in the DFHPI0505 message. . This request failed due to a combination of several factors. . The first problem is that the namespace prefix used to WS-Addressing in the wsdl is "wsa10". If this prefix was just "wsa" then everything would have worked. This is because when DFHPISH calls DFHWSADH it adds the WS-Addressing namespace to the DFHWS-XMLNS container using a prefix of "wsa". When processing reaches DFHPIA1 it scans through the DFHWS-XMLNS container looking for any addressing namespace and saves the prefix it finds. This prefix is then used to process the endpoint reference that was stored in the WSBIND file. As the wrong prefix is used the endpoint reference is not processed correctly and a corrupted <To> element is created. The DFHWS-URI container is also replaced with an empty URI which causes the INVOKE to fail. Additional Symptom(s) Search Keyword(s): KIXREVDAM
Local fix
Changing the wsdl to specify "wsa" instead of "wsa10" and regenerating the WSBIND file should make things work.
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users * **************************************************************** * PROBLEM DESCRIPTION: DFHWS-URI container was incorrectly * * cleaned and DFHPI0505 occurred when * * CICS acted as a web service requester * * using WS-Addressing in case the * * namespace prefix was not 'wsa' in WSDL. * **************************************************************** * RECOMMENDATION: * **************************************************************** CICS acted as a web service requester to invoke a service using WS-Addressing. The prefix of the namespace for WS-Addressing in WSDL was not 'wsa'. DFHPIA1 was always using 'wsa' as the namespace prefix to search and extract the <Address> element from wsbind file and build <To> element. Due to mismatched prefix used for searching, <To> element was built incorrectly and DFHWS-URI container was cleaned unexpectedly. So the INVOKE SERVICE failed because there was no URI supplied resulting in the DFHPI0505 message. Additional Keywords: DFHPI0997 msgDFHPI0997 msgDFHPI0505
Problem conclusion
DFHPISH has been changed to put the namespace value to a separate container instead of DFHWS-XMLNS container. DFHPIA1 has been changed to abstract <Address> element in a new way which is independent of the namespace prefix and then put the namespace back to DFHWS-XMLNS container in case there is no xmlns definition for 'wsa' is already specified.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI19542
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
Submitted date
2014-06-06
Closed date
2014-09-29
Last modified date
2014-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI24750 UI21835
Modules/Macros
DFHPIA1 DFHPISN
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R700 PSY UI21835
UP14/10/08 P F410
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:
04 November 2014