IV48023: COM.IBM.MQETCLIENT.JAR IS OMITTED FROM THE WMQ 7.0.1.10 RESOURCE ADAPTER

Fixes are available

APAR status

Closed as program error.

Error description

The Websphere MQ Resource Adapter (wmq.jmsra.rar) v7.0.1.10
inadvertently omitted the com.ibm.mqetclient.jar file required
for XA transactions.

Local fix

Problem summary

****************************************************************
USERS AFFECTED:
Users of the WebSphere MQ Resource Adapter which is deployed
into application servers, who are attempting to make use of
XA functionality provided by the:

WebSphere MQ Extended Transactional Client

This does NOT include the WebSphere Application Server, or any
of the IBM products which are built upon the WebSphere
Application Server platform such as WebSphere Process Server,
which are unaffected by this issue.

Platforms affected:
All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
****************************************************************
PROBLEM SUMMARY:
As of the inclusion of the code fix associated with APAR
IV19480:

http://www.ibm.com/support/docview.wss?uid=swg1IV19480

which was included in the WebSphere MQ fix packs 7.0.1.10 and
7.1.0.3, it was intended that the WebSphere MQ Transactional
Client component was added to the WebSphere MQ Resource Adapter
(WMQ-RA).

To do this, an additional jar file needed to be included within
the WMQ-RA file:

<PRODUCT_INSTALL_LOCATION>/java/lib/jca/wmq.jmsra.rar

where <PRODUCT_INSTALL_LOCATION> is the location where
WebSphere MQ has been installed to.

This additional jar file was the file:

com.ibm.mqetclient.jar

However, despite the APAR being included in the fix packs, the
additional .jar file was not included within the WMQ-RA.

Problem conclusion

The cause of the missing .jar file was attributed to an
omission
in the configuration of the system used to build
WebSphere MQ and package the WebSphere MQ Resource Adapter.

This has now been corrected, and the file is included within the
WebSphere MQ Resource Adapter file:

wmq.jmsra.rar


| MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0010       |
| MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0010       |
| MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0010   |
| MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0010      |
| MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0010     |
| MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0010     |
| MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0010       |
| MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0010 |
| MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0010     |
| MDVPARTL 7.0.1-WS-MQ-Windows-FP0010        |

| MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0011       |
| MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0011       |
| MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0011   |
| MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0011      |
| MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0011     |
| MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0011     |
| MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0011       |
| MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0011 |
| MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0011     |
| MDVPARTL 7.0.1-WS-MQ-Windows-FP0011        |

| MDVPARTL 7.1.0-WS-MQ-AixPPC64-FP0003       |
| MDVPARTL 7.1.0-WS-MQ-HpuxIA64-FP0003       |
| MDVPARTL 7.1.0-WS-MQ-HpuxPaRISC64-FP0003   |
| MDVPARTL 7.1.0-WS-MQ-LinuxIA32-FP0003      |
| MDVPARTL 7.1.0-WS-MQ-LinuxPPC64-FP0003     |
| MDVPARTL 7.1.0-WS-MQ-LinuxS390X-FP0003     |
| MDVPARTL 7.1.0-WS-MQ-LinuxX64-FP0003       |
| MDVPARTL 7.1.0-WS-MQ-SolarisSparc64-FP0003 |
| MDVPARTL 7.1.0-WS-MQ-SolarisX64-FP0003     |
| MDVPARTL 7.1.0-WS-MQ-Windows-FP0003        |

| MDVPARTL 7.1.0-WS-MQ-AixPPC64-FP0004       |
| MDVPARTL 7.1.0-WS-MQ-HpuxIA64-FP0004       |
| MDVPARTL 7.1.0-WS-MQ-HpuxPaRISC64-FP0004   |
| MDVPARTL 7.1.0-WS-MQ-LinuxIA32-FP0004      |
| MDVPARTL 7.1.0-WS-MQ-LinuxPPC64-FP0004     |
| MDVPARTL 7.1.0-WS-MQ-LinuxS390X-FP0004     |
| MDVPARTL 7.1.0-WS-MQ-LinuxX64-FP0004       |
| MDVPARTL 7.1.0-WS-MQ-SolarisSparc64-FP0004 |
| MDVPARTL 7.1.0-WS-MQ-SolarisX64-FP0004     |
| MDVPARTL 7.1.0-WS-MQ-Windows-FP0004        |

---------------------------------------------------------------
The fix is targeted for delivery in the following PTFs:

Version    Maintenance Level
v7.1       7.1.0.5
v7.0       7.0.1.12

The latest available maintenance can be obtained from
'WebSphere MQ Recommended Fixes'
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037

If the maintenance level is not yet available information on
its planned availability can be found in 'WebSphere MQ
Planned Maintenance Release Dates'
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
---------------------------------------------------------------

Temporary fix

Comments

APAR Information

APAR number
IV48023
Reported component name
WMQ LIN X86-64
Reported component ID
5724H7230
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-09-10
Closed date
2013-09-13
Last modified date
2013-11-06

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

Fix information

Fixed component name
WMQ LIN X86-64
Fixed component ID
5724H7230

Applicable component levels

R701 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022

Tips

IV48023: COM.IBM.MQETCLIENT.JAR IS OMITTED FROM THE WMQ 7.0.1.10 RESOURCE ADAPTER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R701 PSY

Document Information

Share your feedback

Need support?