IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    IT32991

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-05-27

  • Closed date

    2020-10-19

  • Last modified date

    2020-10-19

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
20 October 2020