A fix is available
APAR status
Closed as program error.
Error description
Customer has a CICS web service that uses MTOM and WS-SECURITY. This Web Service works fine with a 'non-java' pipeline. They are trying, now, to use java/axis2 instead. The WS works fine as long as they are not using WS-SECURITY. As soon as they use it, they get AXMU abends. . The problem is in the CICS Java code that interfaces between the Axis2 code and the base CICS pipeline. The WS-Security processing had put the correct 7 byte userid into the DFHWS-USERID container. However, the Java code was obtaining the userid as a minimum of 8 bytes so ended up with one extra garbage byte. This 8 byte value then gets passed in toDFHPIPM and eventually leads to the abend.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: AXMU abend occurs when using Axis2 * * and WS-Security. * **************************************************************** * RECOMMENDATION: * **************************************************************** If WS-Security is enabled and Axis2 pipeline handler is used to process SOAP message, user id is extracted from SOAP header and put into container DFHWS-USERID. Later user id is read from container by Axis2 pipeline handler for transaction attach. According to program logic, even if the user id in the SOAP header is less than 8 bytes, handler will read 8 bytes from container anyway, which contains some extra garbage bytes. When attaching transaction with incorrect user id, AXMU Abend will occur.
Problem conclusion
dfjaxis2.jar has been modified to ensure that user id copied from container DFHWS-USERID is correct.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM72121
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
2012-09-04
Closed date
2012-10-19
Last modified date
2012-12-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK83661
Modules/Macros
DFJ@H340
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R70D PSY UK83661
UP12/11/30 P F211
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 December 2012