Setting the debug level by scenario

This procedure describes how to set debug levels by a particular scenario. It enables you to collect diagnostic data particular to that problem by processing the relevant Control-M components where the problem resides and communicate that information to BMC customer support.

To set a debug level by scenario:

1. From the CCM, select Tools>Debug>Set Debug Level By Scenario.

   The Debug Scenario Wizard appears.

2. From the Scenario drop-down list, select that scenario that represents the problem you have.
3. Select the Control-M component/s where the problem resides (The list is populated dynamically according to the scenario you have selected in the previous step) and then click Next and then click OK.

   A confirmation message appears. The debug level process starts.

4. Recreate the problem on the remote host where the problem occurred, after the debug level processing is completed successfully.
5. In the wizard, select the Scenario recreated checkbox to confirm that you have recreated the problem on the machine where the problem occurred.
6. Select the Reset Debug Level checkbox.

   If you select this checkbox, all debug levels are reset to 0. If you choose not to reset debug levels to 0, you can reset the debug levels manually to the levels you want. For more information, see Debug levels.

7. Click Next and then click OK.
8. Select one or both of the following:
   • Collect usage measurements reports
   • Collect product logs and configuration
9. In the Last days field, define the number of days in the past to include data in the report.
10. From the Save Method drop-down list, select one of the following and then click Next:
    • Common location: Enables you to save the collected output files of all relevant components to either a default location at the component directory or a shared network location. Take note that if you select this option, all relevant Control-M components must have one platform, either Windows or UNIX.
    • Custom location:Enables you to save the collected files and save them per component to either a default location at the component directory or a shared network location.

      NOTE: If you are working with more than one platform, the files are automatically saved to the default location at the component directory. Copy the files to a shared network location, and specify the shared network location path.

    The diagnostic data is being collected.

11. Collect the generated files from the output directories provided in the dialog box, and upload them to the BMC FTP site 000172498 and then click Finish.