Procedure

Specify RAS1 trace options in the install_dir\tmaitm6\KUDENV file on Windows systems or the install_dir/config/ud.ini file on UNIX and Linux® systems. Use one of the following methods to modify trace options:

• Manually edit the configuration file to set trace logging
  1. Open the trace options file:
     • On Windows systems, open the install_dir\tmaitm6\KUDENV file.
     • On UNIX and Linux systems, open the /install_dir/config/ud.ini file.
  2. Edit the line that begins with KBB_RAS1= to set trace logging preferences.
     For example, if you want detailed trace logging, set the Maximum Tracing option (Windows, UNIX and Linux systems):

     KBB_RAS1=ERROR (UNIT:KUD ALL) (UNIT:CSS ALL) (UNIT:KRA ALL) (UNIT:IRADB2 ALL)

  3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:
     • Edit the following parameters to adjust the number of rolling log files and their size.
       • MAXFILES: the total number of files that are to be kept for all startups of a given program. Once this value is exceeded, the oldest log files are discarded. Default value is 9.
       • LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5.
     • IBM® Software Support might guide you to modify the following parameters:
       • COUNT: the number of log files to keep in the rolling cycle of one program startup. Default value is 3.
       • PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1.
     Remember: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost.
  4. Restart the DB2® agent so that your changes take effect.
• (Windows only) Alternate method to edit trace logging parameters:
  1. Open the Manage Tivoli® Enterprise Monitoring Services window.
  2. Right-click the icon of the DB2 agent whose logging you want to modify.
  3. Select Advanced > Edit Trace Parms.
  4. Edit the line that begins with KBB_RAS1= to set trace logging preferences.
     For example, if you want detailed trace logging, set the Maximum Tracing option (Windows, UNIX and Linux systems):

     KBB_RAS1=ERROR (UNIT:KUD ALL) (UNIT:CSS ALL) (UNIT:KRA ALL) (UNIT:IRADB2 ALL)

  5. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:
     • Edit the following parameters to adjust the number of rolling log files and their size.
       • MAXFILES: the total number of files that are to be kept for all startups of a given program. Once this value is exceeded, the oldest log files are discarded. Default value is 9.
       • LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5.
     • IBM Software Support might guide you to modify the following parameters:
       • COUNT: the number of log files to keep in the rolling cycle of one program startup. Default value is 3.
       • PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1.
     Remember: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost.
  6. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you diagnose communications and connectivity problems between the DB2 agent and the monitoring server.
     Remember: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
  7. Save and close the file. You see a message reporting a restart of the DB2 agent so that your changes take effect.