IT04580: ABILITY TO SET DISABLECLIENTAMS TO YES IN THE MQCLIENT.INI FILE FOR C CLIENT.

Fix Pack 8.0.0.2 for WebSphere MQ V8.0

APAR status

• Closed as program error.

Error description

• MQ v7.5 client connects to legacy queue manager such as MQ
  v7.0.1 or MQ v7.1 and it attempts to open the
  SYSTEM.PROTECTION.POLICY.QUEUE and reports
  MQRC_UNKNOWN_OBJECT_NAME error. MQRC_UNKNOWN_OBJECT_NAME (2085)
  error is reported each time the application tries to open a
  SYSTEM.PROTECTION.POLICY.QUEUE queue.
  
  Similar to APAR IC94205, this APAR is to allow the setting of
  DisableClientAMS to Yes|No in the mqclient.ini file for C
  clients.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of WebSphere MQ 7.5 or V8 C Client
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Advanced Messaging Security (AMS) is automatically enabled in
  WebSphere MQ client at v7.5, hence it, by default tries to check
  the security policies for objects at the queue manager. When a
  v7.5 client connects to a queue manager such as v7.1 or v7.0.1,
  since AMS is enabled in v7.5 client by default, it attempts to
  open the SYSTEM.PROTECTION.POLICY.QUEUE at the queue manager.
  However v7.1 or v7.0.1 do not have Advanced Messaging Security
  (AMS) enabled and hence do not have a
  SYSTEM.PROTECTION.POLICY.QUEUE. This causes 2085
  (MQRC_UNKNOWN_OBJECT_NAME) error to be reported when
  SYSTEM.PROTECTION.POLICY.QUEUE is opened.
  
  APAR IC94205 introduced an environment variable
  AMQ_DISABLE_CLIENT_AMS to disable AMS at the client side. Create
  and set the environment variable AMQ_DISABLE_CLIENT_AMS to TRUE
  in the environment where the MQ 7.5 client is running to disable
  AMS at the client side.
  
  However APAR IC94205 didn't have the ability to disable AMS
  using "mqclient.ini" configuration file. IT04580 APAR adds the
  ability to configure this behaviour from the mqclient.ini file
  used by C Client application.
  

Problem conclusion

• The AMS behaviour can now be controlled using the mqclient.ini
  file, using the property name "DisableClientAMS" under the
  "Security" stanza.
  
  For example, to disable or to enable AMS behaviour (and prevent
  the client application attempting to open the
  "SYSTEM.PROTECTION.POLICY.QUEUE" queue), you could add the
  following text to the mqclient.ini file used by the C Client
  application:
  
  Security:
    DisableClientAMS = No|Yes
  
  Disables AMS in Client side
  Security:
    DisableClientAMS=Yes
  
  Enables AMS in Client side
  Security:
    DisableClientAMS=No
  
  Please Note: Environment variable 'AMQ_DISABLE_CLIENT_AMS' is
  applicable only in case of MQ 7.5. MQS_DISABLE_ALL_INTERCEPT
  should be used in case of MQ 8.0 clients.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.5
  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

  5724H7241

Applicable component levels

• R750 PSY

     UP