IBM Support

IZ73368: MQ AGENT INSTANCE NOT STARTED W/ CONFIGURED TEMS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An mq agent instance can be configured to point to a different
    TEMS than the default. It can also be configured to use a
    different port on that TEMS than the default. However, when the
    agent instance is started, it points to the default TEMS/port
    instead of the one for which it was configured.
    
    
    RECREATE INSTRUCTIONS:
    
    The mq agent is always started using the file
    CANDLEHOME/config/mq.config. The instance configurations
    live in CANDLEHOME/config/.Config/kmqenv. The
    following command sequence demonstrates how only the
    host information from the default instance is used
    in mq.config at agent start time:
    
    # itmcmd config -A mq   (set TEMS==mqtems_default)
    # grep "CT_CMSLIST" /opt/IBM/ITM/config/mq.config
    export CT_CMSLIST='ip.pipe:mqtems_default
    # itmcmd config -A -o inst1 mq   (set TEMS==mqtems1)
    # grep "mqtems" /opt/IBM/ITM/config/.ConfigData/kmqenv
    inst1|HOSTNAME|mqtems1|
    aix523|HOSTNAME|mqtems_default|
    # grep "CT_CMSLIST" /opt/IBM/ITM/config/mq.config
    export CT_CMSLIST='ip.pipe:mqtems1'
    # itmcmd config -A -o inst2 mq   (set TEMS==mqtems2)
    # grep "mqtems" /opt/IBM/ITM/config/.ConfigData/kmqenv
    inst1|HOSTNAME|mqtems1|
    inst2|HOSTNAME|mqtems2|
    aix523|HOSTNAME|mqtems_default|
    # grep "CT_CMSLIST" /opt/IBM/ITM/config/mq.config
    export CT_CMSLIST='ip.pipe:mqtems2'
    # itmcmd agent start -o inst1 mq
    # grep "CT_CMSLIST" /opt/IBM/ITM/config/mq.config
    export CT_CMSLIST='ip.pipe:mtems_default'
    
    Basically, the code needs to build and use an
    instance-specific mq.config each time it starts
    the agent.
    

Local fix

Problem summary

  • An MQ agent instance can be configured to point to a different
    management server  than the default.  It can also be configured
    to use a different port on that management server  than the
    default.  However, when the agent instance is started, it points
    to the default management server and port instead of the one for
    which it was configured.
    

Problem conclusion

  • Modified the installer to point to the management server and
    port from which it was configured.
    
    The fix for this APAR is included in the following maintenance
    vehicle:
        | fix pack | 6.2.1-TIV-ITM-FP0003
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ73368

  • Reported component name

    OMEG DIST INSTA

  • Reported component ID

    5608A41CI

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-24

  • Closed date

    2010-04-28

  • Last modified date

    2010-07-22

  • 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

    OMEG DIST INSTA

  • Fixed component ID

    5608A41CI

Applicable component levels

  • R621 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 November 2022