IT32860: Misleading errors reported by the redistributable client when user does not have write permissions for $HOME

APAR status

• Closed as program error.

Error description

• When an IBM MQ redistributable client application tries to
  connect to a queue manager, the connection fails with MQRC 2009
  if the userid
  running the application does not have write permission to the
  directory set in $HOME, e.g. "HOME=/"
  
  The error messages do not describe the problem and additionally
  MQ commands such as "runmqsc" raise memory faults as a result
  of being unable to write to a directory.
  
  The following is an example when running the AMQSCNXC and
  RUNMQSC sample programs:
  
  $samp/bin/amqscnxc
  Sample AMQSCNXC start
  Connecting to the default queue manager
  with no client connection information specified.
  AMQ6235E: Directory '' missing.
  Memory fault
  ```
  $bin/runmqsc
  AMQ6235E: Directory '' missing.
  Memory fault
  

Local fix

• Set HOME to a directory that the userid running the
  redistributable IBM MQ client application has permission
  to write to.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users with environments where HOME is set to a non-default
  location, such as in a Docker container, may be affected by this
  problem.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the HOME environment variable is set to a location which IBM
  MQ is unable to write to then a misleading error message is
  produced and a SEGV occurs.
  
  The ${HOME}/.mqm directory is created when using
  unregistered/non-installed
  version of IBM MQ such as the redistributable client.
  
  The reason that the directory is created is due to a limitation
  in the
  sun_path length when using sockets:
  
  https://www.man7.org/linux/man-pages/man7/unix.7.html
  
  When IBM MQ can be unzipped to an arbitrary location
  then there needs to be a way for it to reliably access its
  socket files using a path
  which fits within the sun_path length.  ${HOME}/.mqm was chosen
  as it
  should normally fit inside the limitations for sun_path.  IBM MQ
  does not store
  socket files in that directory but creates a symlink to the
  actual
  (potentially longer) socket directory.
  

Problem conclusion

• The IBM MQ code has been modified so that a more appropriate
  error message is displayed if there is a problem writing to
  HOME.  The code path which led to the SEGV failure has also been
  corrected.
  
  The IBM MQ documentation has been updated to mention the
  requirement for IBM MQ to have write access to the HOME
  directory, and to explain the reason that the queue manager
  creates the .mqm directory.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.8
  v9.x CD    9.2.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

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels