IBM Support

OA41804: TEMS WON'T START PROPERLY WITH MSG_MODE=KMS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION:
    
    If the new logging facility is enabled (MSG_MODE=kms), then
    "itmcmd server start xxxx" times out. The TEMS processes are
    actually running, but itmcmd is unable to detect the server
    started properly.
    
    TEMS logs shows many message like the following...
    (Saturday, November 10, 2012,
    21:13:15-{8}kolopslog.c,239,"itmOpsLogMsg") Calling CCgLogInfoVA
    with rbpath /opt/IBM/ITM/rb/ascii-little/KMSMSENU and key
    KO41041.
    
    
    RECREATE INSTRUCTIONS:
    1. Install the TEMS.
    2. Configure the TEMS.
    3. Enable the new logging facility by setting MSG_MODE=kms:
       - CANDLEHOME/config/<hostname>_ms_<temsname>.config
       - CANDLEHOME/config/kbbenv.ini
       (Refer to the ITM Troubleshooting Guide for details.)
    4. Attempt to start the TEMS.
    

Local fix

  • Do not enable the new logging facility.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TEMS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: TIVOLI ENTERPRISE MONITORING SERVER     *
    *                      WILL NOT START PROPERLY WITH            *
    *                      MSG_MODE=KMS.                           *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    If the new logging facility is enabled (MSG_MODE=kms), then
    "itmcmd server start xxxx" times out.  The Monitoring Server
    processes are actually running, but itmcmd is unable to
    detect the server started properly.
    

Problem conclusion

  • Code changes were made to allow the itmcmd command to
    properly determine that the Monitoring Server processes are
    up and running.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA41804

  • Reported component name

    MGMT SERVER DS

  • Reported component ID

    5608A2800

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-29

  • Closed date

    2013-04-25

  • Last modified date

    2013-05-03

  • APAR is sysrouted FROM one or more of the following:

    IV23038

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • KDSMAIN
    

Fix information

  • Fixed component name

    MGMT SERVER DS

  • Fixed component ID

    5608A2800

Applicable component levels

  • R623 PSY UA68938

       UP13/04/30 P F304

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSRJ5K","label":"Tivoli Management Server for Distributed Systems on z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"623","Edition":"","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}}]

Document Information

Modified date:
03 May 2013