IV06661: CONFIGPARSER COULD NOT FIND CONFIG FILE BASED ON HOSTNAME

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)

APAR status

• Closed as program error.

Error description

• Configuration of an Agent on a machine whose System Name does
  not match the HOSTNAME (network name) results in the failure to
  read the configuration file created during initial Agent
  installation.
  
  In the Agent's RAS1 log file with default ERROR level tracing:
  kdycfgp.cpp,144,"ConfigParser::parseConfig")
    could not find config file:
    <ITM_install_dir>/config/<machinename>_<pc>.cfg
  configfile.cpp,146,"ConfigFile::parseConfig")
    Error reading agent configuration file: <pc>
  
  configdata.cpp,701,"getConfigurationProperty")
    Configuration property K<pc>_XXXX not found
  
   RECREATE INSTRUCTIONS:
   1. Install Agent Builder Agent <pc> on AIX
   2. Start Agent
   3. Stop Agent
   4. Modify CITRA_HOSTNAME and CITRA_SYSTEMNAME to differ from
  System Name
   5. Configure the Agent (itmcmd config -A <pc>)
   6. Start Agent <pc>.
   7. Observe error in agent's RAS1 trace log:
  kdycfgp.cpp,144,"ConfigParser::parseConfig")
    could not find config file:
    <ITM_install_dir>/config/<machinename>_<pc>.cfg
  

Local fix

• This APAR requires prior changes made with APAR IZ88159
  to be applied to the systems involved along with this APARs
  code changes (already addressed in next release as CMVC
  defect 156687).
  
  Possible workaround is to rename existing Agent configuration
  file in the <ITM_install_dir>/config directory to the name of
  the file that is being looked for by kdycfgp.cpp during
  Agent startup.
  

Problem summary

• Configuration of an agent whose system name does not match the
  HOSTNAME (network name) results in the failure to read the
  configuration file created during initial agent installation.
  
  
  The OS Agent's configuration is contained within a file whose
  name is constructed using the machine's hostname. When the OS
  Agent starts or when the OS Agent's configuration is updated,
  this file is read to obtain the current configuration data. If
  the name of the machine is changed after the OS Agent is
  installed without changing the OS Agent's configuration file
  name to match, the file cannot be located when an attempt is
  made to read the file.
  

Problem conclusion

• Specifically use the COMPUTERNAME environment variable on
  Windows, if set, rather than rely on the text returned from the
  hostname Operating System API. If the COMPUTERNAME value is not
  set, then rely on the hostname as has been done prior to this
  change.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.2-TIV-ITM-FP0007
     | release  | 6.2.3-TIV-ITM
  

Temporary fix

• Rename the OS Agent configuration file to the current name of
  the machine.
  

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

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP