IBM Support

IT38696: The Time Format 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 time format in the MQ Error logs is altered when starting a
    RDQM queue manager manually versus through Pacemaker control.
    
    
    <span style="background-color:rgb(255, 255, 255)">when using
    Pacemaker,</span> a 24 hour clock format  is used  as shown
    below.
    
    
    09/21/21 13:32:29 - Process(12345.1) User(mqm) Program(amqzxma0)
                        Host(xxxxxxxx) Installation(Installation1)
                        VRMF(9.2.0.3) QMgr(RDQMTEST)
                        Time(2021-09-21T11:32:29.923Z)
                        CommentInsert3(RDQMHA2)
    
    AMQ8004I: IBM MQ queue manager 'RDQMTEST' ended.
    
    EXPLANATION:
    IBM MQ queue manager 'RDQMHA2' ended.
    ACTION:
    None.
    ----- amqzxma0.c : 2077
    -------------------------------------------------------
    
    
    Then is switches to a 12 hour format  if started manually.
    
    09/21/2021 01:33:52 PM - Process(12346.4) User(mqm)
    Program(amqzmuc0)
                        Host(xxxxxxxx) Installation(Installation1)
                        VRMF(9.2.0.3) QMgr(RDQMTEST)
                        Time(2021-09-21T11:33:52.665Z)
                        ArithInsert2(1)
                        CommentInsert1(LOGGER-IO)
    
    AMQ5051I: The queue manager task 'LOGGER-IO' has started.
    
    EXPLANATION:
    The critical utility task manager has started the LOGGER-IO
    task. This task has
    now started 1 times.
    ACTION:
    None.
    ----- amqzmut0.c : 1772
    -------------------------------------------------------
    

Local fix

  • If running strmqm manually, export LC_ALL=C  from the
    environment used to run strmqm.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users running IBM MQ Queue manager in a RDQM high availability
    setup.
    
    
    Platforms affected:
    Linux on x86, Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Processes started by pacemaker inherit LC_ALL=C in their
    environment. As such, this was set for queue managers under RDQM
    control when started automatically, but not when started
    manually with strmqm, which could result in differing timestamp
    formats being used.
    

Problem conclusion

  • The strmqm command has been modified to set LC_ALL=C when
    starting RDQM HA queue managers manually, for consistency with
    Pacemaker. There is no change to the locale handling for queue
    managers that are not configured for RDQM HA.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.12
    v9.2 LTS   9.2.0.6
    v9.x CD    9.2.5
    
    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

    IT38696

  • 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

    2021-10-13

  • Closed date

    2022-04-01

  • Last modified date

    2022-09-08

  • 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:
08 September 2022