IT34233: FDC generated when the MQExplorer is started with the runwithtrace command.

APAR status

• Closed as program error.

Error description

• When the MQ Explorer is started using the runwithtrace command,
  an FDC is generated in the same directory as the trace files.
  The FDC contains the information shown below:
  
  +---------------------------------------------------------------
  ---------------+
  |
  | IBM MQ First Failure Sympton Report
  | =========================================
  |
  ...
  | Probe id        :- 10
  | Component id    :- 65
  | Function id     :- 776
  | Reason code     :- 50050
  | ot a valid update group and has not been defined in the
  UpdateGroup.xml file
  | Comment2        :- DmQueueManager
  |
  +---------------------------------------------------------------
  ---------------+
  
  Java function stack
  com.ibm.mq.commonservices.internal.trace.Trace.getJavaStack(Trac
  e.java:2247)
  com.ibm.mq.commonservices.internal.trace.FFST.generateStack(FFST
  .java:362)
  com.ibm.mq.commonservices.internal.trace.FFST.writeFFST(FFST.jav
  a:274)
  com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1
  705)
  com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1
  911)
  com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1
  841)
  com.ibm.mq.explorer.core.internal.parser.DmXmlParser.generateUpd
  ateGroupHashMap(DmXmlParser.java:616)
  com.ibm.mq.explorer.core.internal.objects.TableFactory.getConfig
  HashMap(TableFactory.java:214)
  com.ibm.mq.explorer.core.internal.objects.DmObjectWithConfig.ini
  tConfigTable(DmObjectWithConfig.java:142)
  com.ibm.mq.explorer.core.internal.objects.DmQueueManager.staticI
  nit(DmQueueManager.java:1384)
  com.ibm.mq.explorer.core.internal.base.DataModel.commonInit(Data
  Model.java:392)
  com.ibm.mq.explorer.core.internal.base.DataModel.init(DataModel.
  java:266)
  com.ibm.mq.explorer.ui.internal.base.UiPlugin.delayedStartup(UiP
  lugin.java:607)
  com.ibm.mq.explorer.ui.internal.base.UiPlugin.access$0(UiPlugin.
  java:579)
  com.ibm.mq.explorer.ui.internal.base.UiPlugin$2.run(UiPlugin.jav
  a:565)
  org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the IBM MQ Explorer who are asked to
  collect a trace of the user interface by IBM Support.
  
  
  Platforms affected:
  Linux on x86-64, Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  In order to support the new "automatic configuration of the
  qm.ini file" functionality that was first introduced in MQ 9.1.4
  CD, the MQ Explorer's internal data model was updated to include
  two additional attributes. The attributes were defined as being
  part of a new update group.
  
  The data model did not contain an explicit definition for the
  new update group, and so the MQ Explorer created it when it
  started up. However, in addition to this, if the MQ Explorer was
  started with trace enabled (using the runwithtrace command), it
  would generate an FDC in the same directory as the trace files,
  to indicate that the update group did not exist. The top section
  of the FDC looked like this:
  
  +---------------------------------------------------------------
  ---------------+
  |
  | IBM MQ First Failure Sympton Report
  | =========================================
  |
  ...
  | Probe id        :- 10
  | Component id    :- 65
  | Function id     :- 776
  | Reason code     :- 50050
  | ot a valid update group and has not been defined in the
  UpdateGroup.xml file
  | Comment2        :- DmQueueManager
  |
  +---------------------------------------------------------------
  ---------------+
  

Problem conclusion

• The MQ Explorer has been updated so that it no longer generates
  an FDC if it finds attributes within its data model that belong
  to an update group that has not been defined.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.2
  v9.x CD    9.2.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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels