IBM Support

IT41985: The character set used in the error logs for an RDQM Queue Manager changes depending on how the queue manager is started

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 generates logs messages in different CCSIDs
    depending on how it is started(e.g.the queue manager started by
    the user manually in command line or started by pacemaker in a
    RDQM environment).
    
    For example, when starting a RDQM queue manager manually with
    locale "LANG=ja_JP.utf8",  the queue manager generates message
    on the same local language .
    $ echo $LANG
    ja_JP.utf8
    
    $dspmq
    QMNAME(PJM)
    STATUS()
    QMNAME(QM999)
    STATUS()
    
    However, if the same queue manager when started under Pacemaker
    control, EUC-JP is used in the error log which is wrong.
    $ export LC_ALL=C
    $ echo $LANG
    ja_JP.utf8
    $ dspmq
    QMNAME(PJM)
    STATUS()
    QMNAME(QM999)
    STATUS()
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users running QM in an environment which use multibyte
    codepages/CCSIDs like <span
    style="background-color:#ffffff">954.</span>
    
    
    Platforms affected:
    Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the pacemaker libraries started the queue manager LC_ALL=C
    was incorrectly set for the queue manager's environment. In some
    cases this environment setting was not compatible with the
    expected system codepage/CCSID.
    

Problem conclusion

  • MQ code has been modified to ensure LC_ALL=C is not set on the
    environment used to run RDQM queue managers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.20
    v9.3 LTS   9.3.0.10
    v9.x CD    9.3.4
    
    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

    IT41985

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-09-08

  • Closed date

    2023-08-02

  • Last modified date

    2023-08-02

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

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

Document Information

Modified date:
16 August 2023