IBM Support

PH10484: JMS CONNECTIONS TO MQ FAIL WITH BIP4648E ON Z/OS ON 10.0.0.16

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as requirement.

Error description

  • When connecting to an MQ JMS provider on z/OS using fixpack
    10.0.0.16, connections will fails with the following error
    message in the joblog:
    
    09.41.07 STC20315  +BIP4648E (Msg 1/1) MQ20BRK EG3 45
    JMSCLIENT.'Broker 'MQ20BRK'; Executi  281 on Group 'EG3';
    Message Flow 'SimpleJMSFlow'; Node
    'ComIbmJMSClientInputNode::JMS Input::ComIbmJMSClientInputNode'
    ' THE CONNECTION WITH THE  JMS PROVIDER COULD NOT START, OR HAS
    CLOSED FOR INITIAL CONTEXT FACTORY
    'com.sun.jndi.fscontext.RefFSContextFactory'. THE NODE WILL TRY
    TO RE-ESTABLISH THE CONNECTION.
    
    Trace shows that the root cause of the error is an MQRC 2058
    (MQRC_Q_MGR_NAME_ERROR) being issued from the MQ client.
    
    The issue is caused by a z/OS only regression in the MQ JMS
    libraries shipped with IBM Integration Bus 10.0.0.16.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0.0.16 who use JMS Nodes on
    z/OS where IBM MQ V9.1 is the JMS provider.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When connecting to an MQ JMS provider on z/OS using fixpack
    10.0.0.16, connections will fail with the following error
    message in the joblog:
    
    09.41.07 STC20315  +BIP4648E (Msg 1/1) MQ20BRK EG3 45
    JMSCLIENT.'Broker 'MQ20BRK'; Executi  281 on Group 'EG3';
    Message Flow 'SimpleJMSFlow'; Node
    'ComIbmJMSClientInputNode::JMS Input::ComIbmJMSClientInputNode'
    ' THE CONNECTION WITH THE  JMS PROVIDER COULD NOT START, OR HAS
    CLOSED FOR INITIAL CONTEXT FACTORY
    'com.sun.jndi.fscontext.RefFSContextFactory'. THE NODE WILL TRY
    TO RE-ESTABLISH THE CONNECTION.
    
    Trace shows that the root cause of the error is an MQRC 2058
    (MQRC_Q_MGR_NAME_ERROR) being issued from the MQ client.
    
    The issue is caused by a z/OS only regression in the IBM MQ JMS
    libraries shipped with IBM Integration Bus 10.0.0.16.
    

Problem conclusion

  • The problem is addressed by IBM MQ APAR IT28660 which should be
    applied to IBM MQ PTF level CD 9.1.3,  LTS 9.1.0.3
    
    Please see
    https://www-01.ibm.com/support/docview.wss?uid=swg1IT28660, for
    more details.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH10484

  • Reported component name

    IIB Z/OS

  • Reported component ID

    5655AB100

  • Reported release

    A00

  • Status

    CLOSED REQ

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-02

  • Closed date

    2019-09-30

  • Last modified date

    2019-09-30

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQH8","label":"IBM Integration Bus for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 September 2019