PK41963: CICS SUCCESSFULLY SENDS A WSAT TRANSACTION TO WAS 6.1 BUT GETS ABENDAPIP WHEN IT SENDS REGISTERRESPONSE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An application issues EXEC CICS INVOKE-WEBSERVICE then CICS
  sends WSAT transaction to WAS. WAS sends a register message,
  then CICS sends a RegisterResponse to WAS and finally CICS
  recieves HTTP/1.1 500 Internal Server Error. This causes an
  abendAPIP at the CICS end. WAS recieves WSWS3277E.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICS does not interoperate correctly    *
  *                      with WebSphere 6.1 when using Web       *
  *                      services Atomic Transactions (WS-AT).   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CICS TS V3.1 will not interoperate with WebSphere 6.1 when
  using Web Services Atomic Transactions.  There are several
  problems:
  
   o WebSphere 6.1 uses a <wsa:ReferenceParameters> element which
     CICS does not recognise or process.
   o CICS generates an invalid XML message. The </wsa:To> closing
     element is missing and this leads to a parsing error in
     WebSphere.
   o CICS uses a SOAPAction of "Registered" instead of
     "RegisterResponse" when replying to a "Register" request.
   o On some messages the SOAPAction has a trailing space. This
     then doesn't match the <wsa:Action> element within the XML.
     WebSphere rejects such messages.
   o SOAP Faults being returned due to errors processing Register
     messages did not have the correct SOAPAction.
   o CICS changes its <wsa:ReferenceProperties> element during
     Prepare and Commit processing. WebSphere only uses the
     element from the registration exchange. This means messages
     from WebSphere cannot be matched to waiting tasks in CICS.
  
  Additional Keywords: ReferenceParameters ReferenceProperties
  

Problem conclusion

• CICS WS-AT support has been enhanced to interoperate with
  WebSphere 6.1.  This APAR resolves issues with normal
  transaction flows. See also PK42688 which resolves problems
  relating to system or region failure.
  
  The CICS Transaction Server for z/OS Version 3 Release 1 CICS
  Trace Entries manual (SC34-6443-03) will be updated as follows:
  
  Add the following new trace entries to the end of Chapter 28
  'Pipeline manager domain trace points'
  
  Point ID  Module   Lvl   Type           Data
  PI 1800   DFHPIIM  PI 2  Create token   1 - Token
                                          2 - Object Address
  PI 1801   DFHPIIM  PI 2  Lookup token   1 - Token
                                          2 - Object Address
  PI 1802   DFHPIIM  PI 2  Update token   1 - Token
                                          2 - Object Address
  PI 1803   DFHPIIM  PI 2  Destroy token  1 - Token
  

Temporary fix

•             *********
              * HIPER *
              *********
  FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  UK26251 UK26252

Modules/Macros

•    DESPIAT  DESPIDC  DESPIIM  DESPIRE  DESPIRM
  DESPIRS  DESPITRI DFHPIAT  DFHPIATC DFHPIDCC DFHPIDCD DFHPIIMC
  DFHPIIMI DFHPIRE  DFHPIRM  DFHPIRS  DFHPITRI DFHPIXC  DFHPIXC@
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK26251

     UP07/06/22 P F706

• R402 PSY UK26252

     UP07/06/22 P F706

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.