IJ07905: SITUATION DATA ROWS EXCEED RPC TRANSPORT LIMIT

6.3.0.7-TIV-ITM_TEMA-IF0007

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

• When a Situation goes from Autonomous Mode to TEMS Connected
  Mode  the Situation processing should retrieve the cached data
  for the situation and copy it to a new buffer.  The buffer is
  returned to the caller where data from the current sample  is
  appended to this new buffer, and sent back to the TEMS. The new
  buffer must be large enough to hold both the cached data and
  the  current sample data. For this problem the test to
  determine if the buffer is sufficient size to accommodate is
  incorrectly made, which results in the following error message
  reported in the TEMA log file
  <Situation Name> saved situation data rows exceed RPC transport
  limit, truncated!
  As a result the last Situation data row is not returned to the
  TEMS.
  RECREATE INSTRUCTIONS:
  Install ITM 630 FP3 TEMS/TEPS/Linux Log File  Agent
  Configure KLO Agent FMT and CFG files to collect Log File data
  Enable the KLO Agent to collect log file data.
  Run KLO Agent and allow connection to  TEMS
  Stop TEMS
  Allow KLO Agent to run in Autonomous Mode for a day
  Start  TEMS
  Observe error message  "<Situation Name> saved situation data
  rows exceed RPC transport limit, truncated!" in the TEMA log
  file when the KLO Agent attempts to upload its cached Situation
  data to the TEMS.
  Approver Initials:    RL
  

Local fix

• Reduce the amount of attribute data that is gather by the
  Situation.  Implement a Secondary TEMS in the Agent's
  configuration such that when the Agent loses connectivity with
  the Primary TEMS, the Agent does not have to cache as much data
  during its Autonomous Mode period.
  

Problem summary

• The last row of Situation data may be incorrectly truncated.
  The maximum size of Situation data that is retained on an Agent
  is 16MB.  If the last collected sample data size by the
  Situation equals this maximum value, the last collected sample
  'row' is not returned to the Monitoring Server.
  
  
  When a Situation goes from Autonomous Mode to Monitoring Server
  Connected Mode  the Situation processing should retrieve the
  cached data for the situation and copy it to a new buffer.  The
  buffer is returned to the caller where data from the current
  sample  is appended to this new buffer, and sent back to the
  Monitoring Server.  The new buffer must be large enough to hold
  both the cached data and the  current sample data.  For this
  problem the test to determine if the buffer is sufficient size
  to accommodate is incorrectly made, which results in the
  following error message reported in the Agent's log file
  
  <Situation Name> saved situation data rows exceed RPC transport
  limit, truncated!
  
  As a result the last Situation data row is not returned to the
  Monitoring Server.
  

Problem conclusion

• Change the comparison logic to copy Situation sample data that
  is less than or equal to the maximum cache memory size.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0001
  

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:

  OA56399

Fix information

• Fixed component name

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels