Fixes are available
APAR status
Closed as program error.
Error description
On a WebSphere MQ Server for Windows system an existing queue manager could not be started and a new queue manager can not be created. An error is reported, and the following is an extract of the corresponding FDC entry: Operating System :- Windows Server 2003, Build 3790: SP2 PIDS :- 5724H7220 LVLS :- 7.0.1.9 Product Long Name :- WebSphere MQ for Windows Vendor :- IBM Probe Id :- XC207001 Application Name :- MQM Component :- xxxInitialize SCCS Info :- lib/cs/amqxxinc.c, 1.54.2.1 Line Number :- 301 Build Date :- Jul 18 2012 CMVC level :- p701-109-120718 Build Type :- IKAP - (Production) UserID :- MUSR_MQADMIN Process Name :- C:\PROGRA~1\IBM\WEBSPH~1\bin\amqmsrvn.exe Addressing mode :- 32-bit Process :- 00001560 Thread :- 00000001 UserApp :- FALSE Last HQC :- 0.0.0-0 Last HSHMEMB :- 0.0.0-0 Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Minor Errorcode :- OK Probe Type :- MSGAMQ6119 Probe Severity :- 2 Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred (WinNT error 234 from RegQueryValueEx.) FDCSequenceNumber :- 0 Comment1 :- WinNT error 234 from RegQueryValueEx. Comment2 :- More data is available. . MQM Function Stack xcsInitialize xxxInitialize xcsFFST . MQM Trace History ...
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere MQ on windows platform. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: MQ processes failed to start up due to an error while initializing the common services. Due to this problem none of the MQ commands could run. FDCs with probe id XC207001 were reported by the MQ function xxxInitialize that reads the registry key HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\NLS\CODEPAGE\OEMCP to get the default codepage of the system. The registry API RegQueryValueEx rarely fails with windows error 234 (More data is available) even if the buffer is large enough to hold the value of the registry key.
Problem conclusion
The code is modified to dynamically allocate the buffer based on the length of the registry value and the API RegQueryValueEx is called with the exact length of the data. --------------------------------------------------------------- The fix is targeted for delivery in the following: v7.0 Platform Fix Pack 7.0.1.11 -------- -------------------- Windows 7.0.1.11 v7.1 Platform Fix Pack 7.1.0.4 -------- -------------------- Windows 7.1.0.4 Version v7.5 -------- -------------------- Fix available in: 7.5.0.3 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
IC93032
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
2013-06-13
Closed date
2013-06-27
Last modified date
2013-08-14
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
[{"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.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023