IJ12656: EIF EVENT SLOTS MISSING OR MIS-NAMED

IBM Application Performance Management 8.1.4.0 core framework IF09 8.1.4.0-IBM-APM-CORE-FRAMEWORK-APM-IF0009
IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 1 (6.3.0.7-TIV-ITM-SP0001)

APAR status

• Closed as program error.

Error description

• Environment:   ITM agent
  Version: 6.3.0 FP3 - FP7
  
  Background: EIF events contain slots with names and values.
  Some slots contain agent-neutral information about the
  event--these slots have reserved names that are common across
  all events. The other slots contain data from attributes in the
  attribute group row that caused the event to be
  generated--these slots have names that are the similar to the
  attribute names. If an attribute has the same name as a
  reserved slot, then the corresponding slot name should be
  formed by joining the agent product code, an underscore, and
  the attribute name.
  
  Problem Description: EIF event slots that correspond to
  attributes whose name is the same as a reserved slot are no
  longer added to the event, or in some cases are added to the
  event but without adding the product code to the slot name.
  
  Detailed Recreation Procedure: In ITM 6.3.0 FP7, create a
  private situation whose condition will evaluate to true on at
  least one row on an attribute group containing an attribute
  with one of these reserved slot names (without respect to
  case): acl, adapter_host, administrator, appl_label,
  cause_date_reception, cause_event_handle, class, cms_hostname,
  cms_port, collection, credibility, date, date_reception,
  dispatcher, distrib_admin, duration, effective_value,
  event_handle, fqhostname, hostname, info, integration_type,
  master_reset_flag, monitor, msg, msg_catalog, msg_index,
  num_actions, origin, probe, probe_arg, prev_value, relation,
  relation_delta, repeat_count, response_level, server_handle,
  server_path, severity, situation_displayitem,
  situation_eventdata, situation_fullname, situation_group,
  situation_name, situation_origin, situation_status,
  situation_time, source, status, sub_source, sub_origin, tmr,
  ttid, units, value. The resulting EIF event will not contain a
  slot with a name in the form kpc_attributename.
  
  Related Files and Output:
  Messages found in logs etc
  No error messages, just missing or mis-named slots
  

Local fix

Problem summary

• EIF events contain slots with names and values.  Some slots
  contain agent-neutral information about the event--these slots
  have reserved names that are common across all events.  The
  other slots contain data from attributes in the attribute group
  row that caused the event to be generated--these slots have
  names that are the similar to the attribute names.  If an
  attribute has the same name as a reserved slot, then the
  corresponding slot name should be formed by joining the agent
  product code, an underscore, and the attribute name.
  
  
  EIF event slots that correspond to attributes whose name is the
  same as a reserved slot are no longer added to the event, or in
  some cases are added to the event but without adding the product
  code to the slot name.
  

Problem conclusion

• Modify the processing to join the agent product code together
  with an underscore character (_) followed by the attribute name
  for attributes that have the same name as the reserved slot.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0001
     | interim fix  | 6.3.0.7-TIV-ITM_TEMA-IF0008
  

Temporary fix

Comments

APAR Information

• 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

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels