IZ55790: RECORDSET KEYWORD NOT WORKING WHEN USING TO DETECT RECORDS BY A STRING.

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

• Severity:         2
  Approver:        BEH
  Reported Release:620
  Compid:          5724K1000 Tivoli Universal Agent
  Abstract:        UA RECORDSET 'delimiter_pattern' is not working
  .
  Environment:
  The customer was running ITM 6.2 on a Windows box.  I have also
  re-created the problem on ITM 6.21 on a Windows box.
  Problem Description:
  The RECORDSET feature is not working when it is looking for a
  string in the file.  If you use the RECORDSET for a fixed amount
  of rows that is working fine.
  Detailed Recreation Procedure:
  Create an input file that contains a string which represents the
  end of a record.  Then code the RECORDSET keyword in an MDL file
  with the string taht you are using.  When you run the
  application it breaks the data up on a variable amount of
  records.  The variable amount of records is the amount that it
  takes to fill a buffer which will then be processed against the
  MDL file.
  Related Files and Output:
  Full details are in the PMR and ECUREP.
  

Local fix

• If it is possible change the RECORDSET parameter to look
  for a fixed amount of records.
  

Problem summary

• Universal Agent RECORDSET 'delimiter_pattern'
  is not working for releases 6.2 FixPack 2 or later.
  
  When using 'delimiter_pattern' form of RECORDSET clause in
  metafile, resulting data rows appear incorrectly in Tivoli
  Enterprise Portal display with one or more data rows showing a
  skewing effect which results in incorrect column (attribute)
  values.
  

Problem conclusion

• IZ26083 attempted to enchance RECORDSET
  'delimiter_pattern' behavior for case where file records are
  being read in sporadically (with delay between arrival of file
  records). The compound conditional statement to determine when a
  RECORDSET 'delimiter_pattern' was complete was incorrectly an
  'OR' condition when it needed to be an 'AND' condition.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | interim fix pack | 6.2.0.3-TIV-ITM-IF0002
  

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

• R620 PSY

     UP