Fixes are available
APAR status
Closed as program error.
Error description
After upgrade to V7.0.1.10 or V7.0.1.11, the existing queue manager can not start. Two dmp files were generated together with some FDC files. The FFST summary shows: XC130031 zutQMStatusCallback xecF_E_UNEXPECTED_SYSTEM_RC OK AMQ6109: An internal WebSphere MQ error has occurred. ZX086131 amqzmur0 zrcE_UNEXPECTED_ERROR OK AMQ6125: An internal WebSphere MQ error has occurred. ZX135131 amqzmuf0 zrcE_UNEXPECTED_ERROR OK AMQ6125: An internal WebSphere MQ error has occurred. ZX085131 amqzmuc0 zrcE_UNEXPECTED_ERROR OK AMQ6125: An internal WebSphere MQ error has occurred. XC130031 zutQMStatusCallback xecF_E_UNEXPECTED_SYSTEM_RC OK AMQ6109: An internal WebSphere MQ error has occurred. RM185002 rrmInitRepos rrcE_MQCONN_FAILED OK AMQ9508: Program cannot connect to the queue manager. RM220001 rrmRepository rrcE_MQCONN_FAILED OK AMQ9508: Program cannot connect to the queue manager. The FDC file generated by the process which generated dmp files is: | Probe Id :- XC130031 | Component :- xehExceptionHandler | SCCS Info :- lib/cs/pc/winnt/amqxerrn.c, 1.44.1.1 | Line Number :- 761 | Process Name :- C:\Program Files (x86)\IBM\WebSphere MQ\bin\amqzxm | a0.exe | Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC | Minor Errorcode :- OK | Probe Type :- MSGAMQ6119 | Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. | Comment1 :- Access Violation at address 53203A32 when reading +--------------------------------------------------------------- --------------+ ---> Stack dump for the faulting thread (0x1020) <--- Stack Backtrace: # ChildEBP RetAddr Param#1 Param#2 Param#3 Param#4 Fn-Loc'n : Module!Function+Offset [File Name # Line+Offset @ Address] 00 0017F854 00410245 (0017FA84 00000001 0017F8A4 004480AC) 4F4883BC :<Unknown>!zutQMStatusCallback+0x57c (FPO: [NONE: 4,137,0])<NLN:6>
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of WebSphere MQ 7.0 and later running on Windows platform. Platforms affected: Windows **************************************************************** PROBLEM DESCRIPTION: After upgrading to fixpack 7.0.1.10 or 7.0.1.11 the queue manager fails to start on certain instances of Windows. During the startup the queue manager constructs a platform identification string based on the version of the operating system. In some instances the string was not an appropriate size to hold the information.
Problem conclusion
WebSphere MQ has been changed to correctly handle larger platform identification strings. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.13 v7.1 7.1.0.6 v7.5 7.5.0.5 v8.0 8.0.0.1 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
IT00497
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-21
Closed date
2014-06-26
Last modified date
2014-06-26
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 WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R701 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]
Document Information
Modified date:
24 September 2021