APAR status
Closed as program error.
Error description
An administrator makes a change to qm.ini, inadvertently adding some bad syntax in the CHANNELS or SSL stanzas. After restarting the queue manager, because of the error in qm.ini, the cluster component of the queue manager does not initialize its data properly in relation to locally-defined cluster channels. As a result, no CLUSRCVR or locally-defined CLUSSDR channels are returned from DISPLAY CLUSQMGR(*) on the local queue manager. Cluster capability of the queue manager mostly ceases to function because of the above. For example, applications calling MQOPEN or MQPUT1 for cluster queue names that are not yet known on the local queue manager fail with 2189 MQRC_CLUSTER_RESOLUTION_ERROR. Also, channels do not start outbound from the local queue manager, so messages remain on the cluster transmission queue(s). Non-clustered channels also do not start. FDC records are written with the following details: Probe Id :- RM241000 Component :- rrmUpdateClqMgr Major Errorcode :- rrcE_UNEXPECTED_TOKEN Probe Description :- AMQ9224: Unexpected .ini file entry. MQM Function Stack rrmMain rrmRepository rrmGetMsg rfxReconcile rfxReconcileCLQMGR rrmRecoClqMgr rrmUpdateClqMgr xcsFFST Error logs have both of the following entries : AMQ9224, AMQ9419. (Note that the appearance of AMQ9419 in other circumstances will be correct, in the case that the user has failed to create the correct CLUSRCVR channels with the correct parameters. In this case, though, the user had done this, but the qm.ini mistakes caused the queue manager to believe there were no CLUSRCVRs): AMQ9224: Unexpected .ini file entry. EXPLANATION: The entry with name '' in stanza '' in .ini file '' is either not a valid keyword or has an invalid value. ACTION: Correct the .ini file and retry the operation. AMQ9419: No cluster-receiver channels for cluster 'MYQM' EXPLANATION: The repository manager has received information about a cluster for which no cluster-receiver channels are known. ACTION: Define cluster-receiver channels for the cluster on the local queue manager. The following FDC might also be seen: KN051002
Local fix
Correct the qm.ini file and restart the queue manager.
Problem summary
**************************************************************** USERS AFFECTED: Users who edit their qm.ini file, and mistakenly save it including typos in the CHANNELS or SSL stanzas. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Because of the errors in qm.ini, the cluster component of the queue manager did not initialize properly in relation to locally-defined cluster channels. The FDC records are not required to diagnose this problem. Instead a better error message was needed from the strmqm program, to alert the administrator to the fact that this problem is happening, before they allow applications to start, and suffer errors such as 2189 MQRC_CLUSTER_RESOLUTION_ERROR.
Problem conclusion
The strmqm program has been changed so that it checks the syntax in the CHANNELS and SSL stanzas early on, before starting the queue manager fully. If an error is found, strmqm now outputs an AMQ9224 error message, describing the full details of the position of the error in qm.ini. It also ends immediately without starting the queue manager. This makes it much easier to see what is wrong, and correct it quickly. The text of AMQ9224 is also amended to include the line number of the error within qm.ini. The RM241000 FDC will no longer appear in this particular case. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.5 7.5.0.9 v8.0 8.0.0.8 v9.0 CD 9.0.4 v9.0 LTS 9.0.0.2 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
IT20323
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7241
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-22
Closed date
2017-08-10
Last modified date
2017-08-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI85740
Fix information
Fixed component name
WMQ BASE MULTIP
Fixed component ID
5724H7241
Applicable component levels
[{"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.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023