IT03921: DMPMQCFG command fails to dump authorization records

Fix Pack 8.0.0.2 for WebSphere MQ V8.0

APAR status

• Closed as program error.

Error description

• When issuing the following command to dump the authorization
  information in setmqaut format, no authorization records are
  dumped.
  
  dmpmqcfg -m  -x authrec -o setmqaut -a
  
  The command runs with no errors, but no authorizations are
  dumped.
  
  If the queue manager has a Dead Letter Queue defined, it might
  receive messages from the queue manager's command server
  (amqpcsea) program.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the dmpmqcfg command, who use the -x authrec switch, on
  a queue manager where the Advanced Message Security component is
  not installed. Also, on such a queue manager, any user program
  that uses the MQCMD_INQUIRE_PROT_POLICY, where this command
  fails, will see a bad PCF reply sequence.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Internally the dmpmqcfg program uses a PCF command to ask for
  authorization information from the queue manager. The queue
  manager's command server receives and processes this command,
  and returns the data to the dmpmqcfg program's temporary reply
  queue.
  
  Because the queue manager did not support the Advanced Message
  Security features, it refused to run one of the commands
  (MQCMD_INQUIRE_PROT_POLICY). However the command server reacted
  incorrectly to this condition, and sent incorrect PCF reply
  messages back to the dmpmqcfg program. It sent two reply
  messages, both having MQCFH.Control = MQCFC_LAST. The first
  message should have had MQCFH.Control = MQCFC_NOT_LAST.
  
  Because the MQCFH.Control in the first message indicated that it
  was the last reply message for its command, dmpmqcfg then
  continued to its next command, but then immediately received the
  second reply message for the earlier command and naturally
  interpreted it as the first reply message from its next command.
  
  Externally, therefore, dmpmqcfg displayed incorrect behaviour.
  In fact the real error was not in dmpmqcfg itself, but in the
  underlying PCF reply returned by the command server.
  
  Any user program that uses the MQCMD_INQUIRE_PROT_POLICY, where
  this command fails, will see the same bad PCF reply sequence.
  

Problem conclusion

• The IBM MQ code in the queue manager's command server has been
  corrected.  The first of the two error reply messages from
  MQCMD_INQUIRE_PROT_POLICY now has MQCFH.Control =
  MQCFC_NOT_LAST.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.9
  v8.0       8.0.0.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

  WMQ BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP