IZ67731: The LogmonX trap does not identify the substring that matched th e regular expression.

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• When the logmonx trap is sent there is nothing that identifies
  either the regular expression or the substring match. This makes
  is problematic to efficiently deduplicate the events reliably.
  
  If the substring that matched the expression gets highlighted in
  the history row then this can be extracted to deduplicate the
  events
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  LogMonX on all platforms.
  ****************************************************************
  PROBLEM DESCRIPTION:
  The LogmonX trap does not identify the substring that matched
  the regular expression. This makes it difficult for users to
  verify that their regular expression matching is operating as
  expected.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 9 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• A new object "Brackets" has been added to the end of the
  logmonx control table (or "logmonx brackets=..." in config
  files). If brackets is set then the first matching substring of
  each line will be bracketed, as documented in logmonx-mib.mib.
  For example:
  
  filter: "the only"
  brackets: "{{{,}}}"
  log file: "this will be the only line in this log file"
  logmon reports: "this will be {{{the only}}} line in this log
  file"
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0009
  

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

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSN

     UP