IT13059: FDC WITH PROBE ID ZS086010 AND MQRC_UNEXPECTED_ERROR GENERATED WHEN RUNNING CRTMQM

APAR status

• Closed as program error.

Error description

• When the crtmqm mqm command is run on the MQ Appliance, the
  command never completes and a failure data capture (FDC) file
  with the following information is generated:
  +---------------------------------------------------------------
  --------------+
  |                                       |
  | WebSphere MQ First Failure Symptom Report                  |
  | =========================================                  |
  |                                       |
  | Date/Time     :- <date>                         |
  | UTC Time     :- <time>                         |
  | UTC Time Offset  :- 0 (GMT)                        |
  | Host Name     :- <host>                         |
  | Operating System :- IBM MQ Appliance ()                  |
  | PIDS       :- 5725-S14                        |
  | LVLS       :- 8.0.0.4                        |
  | Product Long Name :- IBM MQ Appliance                    |
  | Vendor      :- IBM                          |
  | O/S Registered  :- 1                           |
  | Data Path     :- /var/mqm                        |
  | Installation Path :- /opt/mqm                        |
  | Installation Name :- MQAppliance   (1)                  |
  | License Type   :- Unknown                        |
  | Probe Id     :- ZS086010                        |
  | Application Name :- MQM                          |
  | Component     :- zsllpiCreateQM                     |
  | SCCS Info     :- /build/slot1/p800_P/src/cmd/zmain/amqzsly0.c,
     |
  | Line Number    :- 2400                          |
  | Build Date    :- Oct 29 2015                      |
  | Build Level    :- p800-WARR-L151029                   |
  | Build Type    :- IKAP - (Production)                  |
  | Effective UserID :- 100 (mqm)                       |
  | Real UserID    :- 101 (mqsystem)                     |
  | Program Name   :- crtmqm                         |
  | Arguments     :- -fs 1024M MQM                     |
  | Addressing mode  :- 64-bit                         |
  | LANG       :-                            |
  | Process      :- 238400                         |
  | Process(Thread)  :- 238400                         |
  | Thread      :- 1                           |
  | QueueManager   :- MQM                          |
  | UserApp      :- FALSE                         |
  | ConnId(1) IPCC  :- 44                           |
  | Last HQC     :- 1.0.0-228096                      |
  | Last HSHMEMB   :- 2.4.4-8448                       |
  | Last ObjectName  :-                            |
  | Major Errorcode  :- MQRC_UNEXPECTED_ERROR                 |
  | Minor Errorcode  :- OK                           |
  | Probe Type    :- INCORROUT                       |
  | Probe Severity  :- 4                           |
  | Probe Description :- AMQ6125: An internal IBM MQ Appliance
  error has    |
  |  occurred.                                 |
  | FDCSequenceNumber :- 0                           |
  |                                       |
  +---------------------------------------------------------------
  --------------+
  
  The same issue may be observed when using queue managers running
  in Windows or UNIX environments.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users creating a queue manager or ending a queue manager very
  soon after starting it.
  
  
  Platforms affected:
  AIX, HP-UX Itanium, IBM iSeries, Linux on Power, Linux on S390,
  Linux on x86-64, Linux on zSeries, Solaris SPARC, Solaris
  x86-64, Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A race condition existed in the queue manager whereby if the
  queue manager was being ended very soon after being started (as
  happens during creation of a queue manager) the queue manager
  would wait for a thread to shutdown, but because the queue
  manager was ending the thread would not start. This caused
  ending of the queue manager to hang and an FDC to be generated.
  The queue manager would have to be killed.
  

Problem conclusion

• IBM MQ has been modified to allow ending of a queue manager to
  occur even when it has not yet been fully initialized.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.5
  
  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

  IBM MQ APPL M20

• Fixed component ID

  5725S1400

Applicable component levels

• R800 PSY

     UP