IT32991: CLARIFY IN KC THAT A SECURED QUEUE MANAGER CANNOT BE USED FOR THE DEFAULT LOCAL QUEUE MANAGER

APAR status

• Closed as documentation error.

Error description

• An integration node can have an associated default queue
  manager, connections to the local queue manager always use local
  bindings and cannot be configured to specify any security
  credentials. As such it is not possible to use a queue manager
  that requires authentication for local connections. The
  knowledge center article entitled "Connecting to a secured IBM
  MQ queue manager" (ah09090_) should be updated to reflect this.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10 and IBM App Connect
  Enterprise v11 wishing to use a secured queue manager as the
  default local queue manager.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  An integration node can have an associated default queue
  manager. Connections to a local queue manager always use local
  bindings and cannot be configured to specify any security
  credentials. As such it is not possible to use a queue manager
  that requires authentication for local connections. The
  knowledge center article entitled "Connecting to a secured IBM
  MQ queue manager" (ah09090_) should be updated to reflect this.
  

Problem conclusion

• The Knowledge Center article has been updated to clarify this
  restriction.
  

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

Applicable component levels