IBM Support

OA06124: REMOVE DEPENDANCY FROM HEALTH MONITOR FOR RKILL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The health Monitor at present is dependant on Microsoft's
    RKIll.  Microsoft has acknowledged a problem with that code, but
    it is not a supported API and will not be fixed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TBSM 2.1.1 users.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Listener column in the MVS Status   *
    *                      window in the HealthMonitor client      *
    *                      does not display the correct            *
    *                      information.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The HealthMonitor scripts run rkill commands to verify that the
    ASIMVSIPOSListener process is active on the EventHandler server.
    The problem is that the RemoteKill service is not very reliable
    and tends to shut down on its own at times when the server it
    is running on is very active. This is fairly common on the
    EventHandler server if a customer has many OS's. If the
    RemoteKill service is not running when the HealthMonitor scripts
    are run by the HealthMonitor, the MVS Status window will show
    incorrect status.
    

Problem conclusion

  • MKS Toolkit 8.6 introduced a parameter for the "ps" command
    that allows it to run against remote servers, which is exactly
    what was needed to remove the HealthMonitor script dependency
    on rkill - a tool that can list processes on a remote server.
    The HealthMonitor scripts have been modified to use the ps
    command if MKS 8.6 is installed.
    
    NOTE: MKS Toolkit for System Administrators 8.6 is required
          for this fix.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | LA interim fix | 2.1.1-BSM-0011-E55
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA06124

  • Reported component name

    TIVOLI BSM OS/

  • Reported component ID

    5698BSM00

  • Reported release

    21E

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2004-01-07

  • Closed date

    2004-05-04

  • Last modified date

    2004-05-04

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

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

Fix information

Applicable component levels

  • R20D PSN

       UP

  • R21D PSN

       UP

  • R21E PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTG3D","label":"Tivoli Business Systems Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"21E","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 May 2004