IZ80146: UA METAFILE USING REGEX MAY CRASH ON 64BIT O/S PLATFORMS

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• When a UA metafile that uses 'REGEX' is run, the kuma620 process
  may crash on 64 bit systems.
  This could occur on any 64-bit Unix system.
  
  Logs with the following tracing:
  ERROR (UNIT:kumamain ALL) (UNIT:kum0regx ALL) (UNIT:kumpdsat
  ALL) (UNIT:kumpdpda ALL)
  
  show messages similar to:
  -------------------------
  
  (4C35EE57.0037-23:kumpmdua.c,448,"KUMP_MoveDataUseAttributeDelim
  iters") Setting *Rptr to Bptr @NULL
  (4C35EE57.0038-23:kumpcapf.c,337,"KUMP_CheckAttributesPassFilter
  s") Data <SmallBusiness> AttrName <CacheName> failed Match
  filter 1: <Statements>
  (4C35EE57.0039-23:kumpcapf.c,337,"KUMP_CheckAttributesPassFilter
  s") Data <SmallBusiness> AttrName <CacheName> failed Match
  filter 2: <AcctInfo>
  (4C35EE57.003A-23:kumpcapf.c,337,"KUMP_CheckAttributesPassFilter
  s") Data <SmallBusiness> AttrName <CacheName> failed Match
  filter 3: <Domain>
  (4C35EE57.003B-23:kumpcapf.c,337,"KUMP_CheckAttributesPassFilter
  s") Data <SmallBusiness> AttrName <CacheName> failed Match
  filter 4: <Rates>
  (4C35EE57.003C-23:kumpcapf.c,337,"KUMP_CheckAttributesPassFilter
  s") Data <SmallBusiness> AttrName <CacheName> failed Match
  filter 5: <User>
  (4C35EE57.003D-23:kumpcapf.c,566,"KUMP_CheckAttributesPassFilter
  s") 1st Pass set to NO for AttrName <CacheName> SEptr @110FE4110
  (4C35EE57.003E-23:kumpfile.c,564,"KUMP_FileServer") IOptr
  @110FE45B0 BHptr @110FCAD10 Mode T RecCount 2 Control 0011
  -------------------------
  
  The backtrace on the crash is something like this:
  
  -----------------------
  
  Segmentation fault in
  validateRE__FPC18URegularExpressionP10UErrorCodeSc
  at 0x900000001e74238
  0x900000001e74238
  (validateRE__FPC18URegularExpressionP10UErrorCodeSc+0x6c)
  e8630002
  (dbx) t
  validateRE__FPC18URegularExpressionP10UErrorCodeSc(0x10fcb1b0,
  0x1111e47c4, 0x0) at 0x9000000
  uregex_pattern_3_2(0x10fcb1b0, 0x0, 0x1111e47c4) at
  0x900000001e76328
  KUM0_IsRegExPatternMatch(0x10fcb1b0, 0x110fca10d, 0x0,
  0x1111e70b8) at
  0x9000000022dd760
  KUMP_CheckAttributesPassFilters(0x11024a7f0, 0x110fc0bd0) at
  0x900000003b08500
  KUMP_MoveDataFromBufferToAttr(0x11024a7f0, 0x110fc1070,
  0x110fab1b0) at
  0x900000003b0e6f0
  KUMP_FileServer(0x110dc78f0) at 0x900000003b8247c
  kumptask.Task(0x110dc78f0) at 0x900000003ac5db4
  (dbx)
  ------------------------
  
  Related files and Output:
  
  Logs:
  
  /ecurep/pmr/1/4/14468,487,000/2010-07-08/14468.487.000kum-logs-0
  708.tar_unpack/ITM/logs
  
  Core file/Snapcore:
  /ecurep/pmr/1/4/14468,487,000/2010-07-08
  

Local fix

Problem summary

• A UA metafile using a regular expression may terminate
  abnormally on 64-bit platforms.
  
  
  When using multiple sources for an attribute group that has at
  least one attribute with a REGEX type filter on a 64-bit
  platform, it is possible that 64-bit address for RegEx object is
  deprecated to a 32-bit address, susbsequently causing UA to
  abend.   This was due to a missing "extern" declaration in a
  function signiature.
  

Problem conclusion

• The UA was re-compiled with the extern declaration in place,
  thereby preserving the 64-bit address values.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0003
  

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

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R622 PSY

     UP