IV50760: PROVIDE NEW SITUATION TO MONITOR SITUATIONS FOR FILTER OBJECT TOO BIG CONDITIONS

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
IBM Tivoli Monitoring 6.2.3 Fix Pack 4 (6.2.3-TIV-ITM-FP0004)

APAR status

• Closed as program error.

Error description

• A large % of PMRs are caused by situations which, after
  compilation, are too large and cause the TEMS to consume
  excessive CPU or crash.
  
  This APAR will add a new product-provided situation to monitor
  other situations for too big filter objects.
  
  This situation will monitor the TEMS log files for specific
  messages.  The alerts will be reflected as a light on the
  Enterprise node in TEP.
  

Local fix

Problem summary

• New situation named TEMS_Alert will monitor for situations that
  may cause performances issues on the monitoring server.
  
  
  A new situation named TEMS_Alert has been added to monitor for
  other situations that may cause performances issues on the
  monitoring server.  When some poorly constructed situations are
  started at the monitoring server, for example ones whose
  predicates are too large, the situations start but never go
  true.  The TEMS_Alert is intended to watch for these types of
  situations and warn the operator that the offending situation
  should be refactored.
  
  Install Actions:
  In order for the situation to be automatically distributed one
  of the following two options must be used:
  
  a)  When seeding the monitoring server during installation,
  select the first option for the product provided situations to
  be distributed.
  
     1) ALL - This option adds the default managed system groups
        to all the applicable situations. Note that not all
        situations have the default managed group setting. For
        some, you might need to manually define the distribution
        in the Tivoli Enterprise Portal due to the specific
        content of the agent support package.
  
  or
  
  b) After installation, if the TEMS_Alert situation is not
  distributed, the portal client situation editor can be used to
  modify the situation and set the distribution to *ALL_CMS.  Once
  set, click on Apply/OK to have the situation distributed.
  

Problem conclusion

• The TEMS_Alert situation provides proactive insight into poorly
  constructed situations which may ultimately impact performance
  at the monitoring server.  Note that this cannot be seeded
  directly on z/OS, only from distributed monitoring servers.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.3-TIV-ITM-FP0004
    | fix pack | 6.3.0-TIV-ITM-FP0002
  

Temporary fix

• None.  Currently you would have to search the management server
  RAS1 logs to find these types of errors.
  

Comments

APAR Information

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

  IV46572

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

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R623 PSY