Fixes are available
APAR status
Closed as program error.
Error description
A WebSphere MQ v7 Requester-Server channel defined with a security exit will hang if the channel is started from the Requester side of the channel. The Requester channel goes into request state, and the Server channel goes into binding state. If the channel is started from the Server side then the channel goes into RUNNING state. ADDITIONAL KEYWORDS: hangs hanging hung loop loops looping chl status connection RQSTR SVR amqrspin starts startup SVR/RQSTR Requester/Server Server/Requester RQSTR-SVR RQSTR/SVR SVR-RQSTR SCYEXIT
Local fix
Problem summary
**************************************************************** USERS AFFECTED: WebSphere MQ V7 users using security exit on Requester-Server channel pair. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: The requester-server channel pair does not start when defined with security exits. The security exchanges loops infinitely when the channel is started from the requester side. The channel starts fine if started from the server side.
Problem conclusion
The problem was occurring since requester was not sending the STATUS_DATA segment to the server when a exit response of MQXCC_OK is received. As a result of this the security exchange loops through infinitely causing the requester side of the channel to remain in requesting state while the server in binding state. The code is modified to appropriately identify the completion of the security exchange and to start the channel successfully. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.6 -------- -------------------- Windows U200328 AIX U840698 HP-UX (PA-RISC) U841555 HP-UX (Itanium) U841560 Solaris (SPARC) U841556 Solaris (x86-64) U841562 iSeries tbc_p700_0_1_6 Linux (x86) U841557 Linux (x86-64) U841561 Linux (zSeries) U841558 Linux (Power) U841559 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
IC74296
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-02-04
Closed date
2011-03-30
Last modified date
2011-03-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM35926
Fix information
Fixed component name
WMQ WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023