IC77793: AGENTCONNECTIONTIMEOUT PARAMETER TREATED AS MILLISECONDS VS SECONDS

IBM Tivoli Storage Productivity Center 4.2.2 GA (October 2011)
4.2.1 Interim Fix 1 (November 2011) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• Increasing the AgentConnectionTimeOut value in the server.config
  file as recommended in TPC Infocenter in order to prevent
  timeouts results in faster timeouts.
  This is because current code treats the value as milliseconds
  instead of seconds.
  The default setting for this parameter is 60000, if not
  specified in the server.config file.
  
  
  RECREATE STEPS:
  Follow recommended actions in TPC Infocenter.
  http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp
  ?topic=%2Fcom.ibm.tpc_V421.doc%2Ffqz0_r_tbs_install_agents_sra1.
  html
  Action
  Increase the AgentConnectionTimeOut value in the server.config
  file. Change the value from 60 to 120 or 180. The server.config
  file is in the following directory:
  
  C:\Program Files\IBM\TPC\data\config (for Windows)
  /opt/IBM/TPC/data/config (for UNIX or Linux)
  
  Stop and restart the Data server.
  

Local fix

• Multiply the recommended values by 1000.
  Change the value from 60000 to 120000 or 180000
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: TPC 4.2.x users adjusting the                *
  *                 AgentConnectionTimeOut value for the         *
  *                 Storage Resource Agents                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the AgentConnectionTimeOut parameter is specified in
  server.config, the values are treated as milliseconds.
  The values specified in the help page (60 to 120 or 180) are
  not converted to milliseconds before use and results in SRA
  deployments timing out quickly.
  

Problem conclusion

• A fix has been made so that the values read from server.config
  are converted to milliseconds.  The fix for this APAR is
  targeted for the following maintenance packages:
  
  | fix pack | 4.1.1-TIV-TPC-FP0007 - target to be determined
  | fix pack | 4.2.1-TIV-TPC-FP0004 - target August 2011
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future fix packs do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  

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

  TPC FOR DATA

• Fixed component ID

  5608TC300

Applicable component levels

• R41A PSY

     UP

• R41H PSY

     UP

• R41L PSY

     UP

• R41S PSY

     UP

• R41W PSY

     UP

• R42A PSY

     UP

• R42H PSY

     UP

• R42L PSY

     UP

• R42S PSY

     UP

• R42W PSY

     UP