IBM Support

IZ45161: KMQ AGENT CANNOT BE STARTED OR STOPPED BY BATCH MTEMS FOR ITM 6.2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • Severity: 3
    Approver: CM
    Compid:   5608A41CI Distributed Installer
    Abstract: KMQ Agent cannot be started or stopped by batch MTEMS
    for
              ITM 6.2
    
    Environment:
    This error only occurs on ITM 6.2 (GA +) and only for KMQ Agent.
    During install the Agent will not start and cannot be stopped by
    MTEMS in batch mode.  The only agent effected is KMQ and only on
    release 6.2 GA through the fixpack where the bug is corrected.
    The error does not occur for ITM 6.1 or ITM 6.2.1.  This error
    may also effect the starting and stopping of the KMQ Agent via
    TEPS or the Command Line Interface, tacmd.
    
    Problem Description:
    In scanning the services to start or stop, a null pointer
    resulted and when the KMQ agent was being processed the null
    pointer was used.  This use of the null pointer caused an
    addressing exception for MTEMS.  The error only occurs on ITM
    6.2 GA+ when OMEGAMON for Messaging is installed.  After
    install, the agent should start and stop through the MTEMS GUI,
    only batch mode is incorrect.  The error was corrected in
    release ITM 6.2.1.  Symptoms include:  1.  After installing
    OMEGAMON for Messaging the WebSphere MQ Monitoring Agent is not
    started as part of the install.  It must be started manually by
    MTEMS in the GUI after the install completes.  2.  The tacmd may
    not start or stop the KMQ Agent.  NOTE:  Instances of the KMQ
    agent are not effected but this APAR.
    
    Detailed Recreation Procedure:
      To recreate:
      1. Install OMEGAMON for Messaging 7.0 pristine.
      2. After the Configuring and Starting Agents popup another
         popup will appear.
      3. Tivoli Service Manager has encountered a problem and needs
         to close.
      4  Also, after the install completes, the WebSphere MQ
         Monitoring Agent will is not running as it should be.
    
    Related Files and Output:
    Duplicated problem locally to isolate and identify offending
    code.
    

Local fix

  • Workaround:
    After the install completes the Agent can be started via the
    MTEMS GUI.  Batch mode is the only area effected by the error.
    Both batch Start and batch Stop are effected, but only for the
    KMQ Agent.  All other agents start and stop as they should.  If
    batch start and stop are required use the net start and net stop
    commands to start and stop the KMQ agent.  The service name is
    KMQIRA_Primary.  The start command would be net start
    KMQIRA_Primary The stop command should be:  net stop
    KMQIRA_Primary.
    

Problem summary

  • Code was tested on ITM 6.2.1 and the desired function was
    working as it should.
    

Problem conclusion

  • Anyone who needs this fix, should upgrade to ITM 6.2.1
    

Temporary fix

  • Stop the agents manually throught the
    net stop command, or through the MTEMS
    GUI.
    

Comments

APAR Information

  • APAR number

    IZ45161

  • Reported component name

    OMEG DIST INSTA

  • Reported component ID

    5608A41CI

  • Reported release

    620

  • Status

    CLOSED UR3

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-04

  • Closed date

    2009-04-06

  • Last modified date

    2009-04-06

  • 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