IT39876: IBM MQ client connection on Linux causes internal error (Probe ID ZD061030)

APAR status

• Closed as program error.

Error description

• An inbound IBM MQ client connection causes an
  internal error.  The agent process (amqzlaa0) creates an
  FFST with the following details:
  
  Probe Id          :- ZD061030
  Component         :- zruNotifyObject
  
  MQM Function Stack
  zlaMainThread
  zlaProcessMessage
  zlaProcessSPIRequest
  zlaSPIAdoptUser
  zsqSPIAdoptUser
  kpiSPIAdoptUser
  kqiRegisterApplGrpConn
  kqiLocateApplGrpConn
  zruNotifyObject
  xcsFFST
  
  Another symptom of this problem is incorrect partial application
  paths being displayed in administrative tools such as
  runmqsc or the IBM MQ Explorer.
  

Local fix

• Modify the client so that it uses a non-blank application name.
   A C client, for example, can use the prctl() call to modify its
  name and so this type of code should be reviewed for
  correctness.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the Perl PAR-Packer tool may be particularly affected
  by this problem.  Users who have applications that use APIs such
  as prctl() may also be affected.
  
  
  Platforms affected:
  Linux on zSeries, Linux on x86-64, Linux on x86, Linux on Power,
  Linux on S390, IBM iSeries
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  IBM MQ uses information from the /proc/PID/status file to
  determine the name of the client application.  If this is set
  incorrectly by the application then it is possible that IBM MQ
  will report a blank name for the application, which leads to the
  FDC reported by this APAR.
  
  One known vector that causes this problem is the Perl PAR-Packer
  tool.
  

Problem conclusion

• The IBM MQ C client code has been changed so that it will now
  use the name "**UNKNOWN**" for an application if the application
  name is determined to be blank or empty.
  
  If /proc/PID/status contains a technically valid application
  path then it is accepted by IBM MQ as the application name.  It
  is the responsibility of the application to ensure that this
  data is correct.
  
  The IBM MQ server code for version 9.2 and above has been
  modified so that an administrator can inhibit the creation of
  ZD061030 FDCs in the event that they are unable to easily
  upgrade the client application.  The following environment
  variable, if set to any value, will disable the ZD061030 FDC
  which reports a blank application name:
  
  AMQ_IGNORE_BLANK_APPNAME
  
  There may be other unknown side-effects caused by the queue
  manager accepting a blank application name and so it is
  recommended that the client be corrected as soon as possible and
  the environment variable be used only as a temporary measure.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.17
  v9.0 LTS   9.0.0.13
  v9.1 LTS   9.1.0.12
  v9.2 LTS   9.2.0.6
  v9.x CD    9.3.0.0
  
  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