APAR status
Closed as documentation error.
Error description
strmqm with the -c option will recreate the default objects, with the default attributes. i.e any manual changes to the default objects will be undone. . New default objects are created automatically when a queue manager is first started following an upgrade. Migration of existing objects occurs automatically at first reference following an upgrade. New attributes of existing objects should assume default values at this time. . There should be no need to explicitly run strmqm -c unless you explicitly want to reset/recreate the default objects. . WebSphere MQ 7.1.0>WebSphere MQ>Migrating and upgrading>Planning V7.0.1 to V7.1 migration by platform Additional Symptom(s) Search Keyword(s):
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users migrating to MQ V7.1 Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The V7.1 infocenter suggests that it is normal to run "strmqm -c" as part of a migration to MQ V7.1. strmqm -c should only be run if the customer wants to reset the attributes of the MQ default objects, it should NOT normally be run as part of a migration. The MQ V7.5 and MQ V8.0 infocenters do not include this incorrect advice.
Problem conclusion
The advice in the MQ V7.1 infocenter, to run "strmqm -c" as part on a migration to V7.1, should be removed. This section of the V7.1 infocenter should be more similar to the V7.5 infocenter. The section to be removed starts Refresh the queue manager. Use the -c option to start the queue manager, redefine and replace system objects, and stop the queue manager. An example can be found at http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ _7.1.0/com.ibm.mq.doc/mi77117_.htm.
Temporary fix
Comments
APAR Information
APAR number
IT03453
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
710
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-29
Closed date
2014-08-20
Last modified date
2014-08-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"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.1"}]
Document Information
Modified date:
09 March 2021