IBM Support

IT39620: Queue manager fails to start with FDC XY465009 from component xcsCreateSimplePipe

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The Queue Manager is fails to start and generates the following
    failure data capture (FDC) records.
    
    amqzxma0 15842 1 XY465009 xcsCreateSimplePipe
    xecF_E_UNEXPECTED_SYSTEM_RC OK
    amqzxma0 15842 1 ZX001030 zxcCreateECResources
    xecF_E_UNEXPECTED_SYSTEM_RC OK
    
    Probe Id          :- XY465009
    Component         :- xcsCreateSimplePipe
    Program Name      :- amqzxma0
    Thread            :- 1    ECMain
    Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
    Minor Errorcode   :- OK
    Probe Type        :- MSGAMQ6119
    Probe Description :- AMQ6119S: An internal IBM MQ error has
    occurred  (bind())
    
    Arith1            :- 2 (0x2)
    Arith2            :- 8 (0x8)
    Comment1          :- bind()
    Comment2          :-  /var/mqm/sockets/<QM
    Folder>/@qmgr/spipe/<host>/zxc.health
    
    Probe Id          :- ZX001030
    Component         :- zxcCreateECResources
    Program Name      :- amqzxma0
    Thread            :- 1    ECMain
    Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
    Minor Errorcode   :- OK
    Probe Type        :- MSGAMQ6119
    Probe Description :- AMQ6119S: An internal IBM MQ error has
    occurred ()
    

Local fix

  • Remove the ShortSubpoolName stanza in qm.ini.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using a queue manager name with more than 12 characters
    and
    a queue manager directory name with 12 characters or less and
    ShortSubpoolName in qm.ini defined with more than 12 characters
    are likely to be affected this problem.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in subpool name management, resulted in IBM MQ using an
    incorrect name for the subpool.
    This caused a failure at queue manager startup.
    

Problem conclusion

  • The IBM MQ code has been modified to use correct subpool name.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.11
    v9.2 LTS   9.2.0.6
    v9.x CD    9.3.0.0
    
    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 number

    IT39620

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-11

  • Closed date

    2022-02-03

  • Last modified date

    2022-04-13

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
14 April 2022