CollectingDebugData for the Scheduler Application

This topic provides information about scheduling PSL debugger data collection. You can use this feature to turn PSL debugger data collection on and off for different parts of the Scheduler application. For more information about PSL debugger data, see the PATROL Script Language Reference Manual Volume I-PSL Essentials.

To Collect PSL Debugger Data for the Scheduler Application

1. Access the SCHEDULER application menu as described in Accessing KM Commands and InfoBoxes.
2. Select Scheduling Debug from the pop-up menu. The BMC PATROL Scheduler PSL Debugger dialog box is displayed.
3. In the Scheduling Debug dialog box, select the check box next to each selection that you want to turn on. Debug data will be collected for that option.

4. For the Scheduler Daemon Debugger group box item, select the check box next to each selection that you want to turn on for run-time checks and traces. When a debugging selection is turned on, debug data is collected for that option.

    

   Check Box	Description
   Run-Time Checks
   Arithmetic operations with NULL strings	Checks to ensure that numeric variables are explicitly initialized to 0, instead of defaulting to a NULL string.
   Arithmetic operations with non-numeric operands	Checks for arithmetic operations that involve non-numeric operands An expression that attempted to numerically add "mary" + "john" would generate this warning.
   Illegal or undefined arithmetic operands	Checks for illegal or undefined arithmetic operations An operation that attempted to divide by zero would generate this warning.
   Uninitialized variables	Checks for variables that were not explicitly initialized If you attempt to use a variable before explicitly equating it to a value, this warning is generated.
   PSL Version 2.0 built-in functions	Allows you to suppress warning messages that were not suppressible in PSL Version 2.0
   PSL Version 3.0 built-in functions	Allows you to perform an error check of built-in functions that were not in BMC PATROL Version 2.0.  This option detects the following errors: Passing non-numeric arguments when a numeric value is required Passing a bad argument Passing the wrong number of arguments to a printf() function Note: BMC recommends enabling PSL Version 2.0 and PSL Version 3.0 built in functions.
   Traces
   Function call tracing	Reports which functions are called, but does not return information about the arguments. Function call tracing captures both user-defined and built-in functions.
   Function argument tracing	Reports the arguments passed to all user-defined or built-in functions Function call tracing must also be enabled if you want to use this debugger option.
   Function return value tracing	Reports the value returned by calls to all user-defined or built-in functions
   Variable assignment tracing	Reports the variable name (if available), and the value assigned to it
   PSL errno tracking	Reports any nonzero values stored in the PSL errno variable
   PSL lock tracing	Reports the interprocess actions that occur during lock() and unlock() function processing This option reports back the granting, denying, and releasing of locks.

5. For the Scheduler Facility Debugger group box item, select the check box next to each selection that you want to turn on for run-time checks and traces. When a debugging selection is turned on, debug data is collected for that option.

    

   Check Box	Description
   Run-Time Checks
   Arithmetic operations with NULL strings	Checks to ensure that numeric variables are explicitly initialized to 0, instead of defaulting to a NULL string.
   Arithmetic operations with non-numeric operands	Checks for arithmetic operations that involve non-numeric operands An expression that attempted to numerically add "mary" + "john" would generate this warning.
   Illegal or undefined arithmetic operands	Checks for illegal or undefined arithmetic operations An operation that attempted to divide by zero would generate this warning.
   Uninitialized variables	Checks for variables that were not explicitly initialized If you attempt to use a variable before explicitly equating it to a value, this warning is generated.
   PSL Version 2.0 built-in functions	Allows you to suppress warning messages that were not suppressible in PSL Version 2.0
   PSL Version 3.0 built-in functions	Allows you to perform an error check of built-in functions that were not in BMC PATROL Version 2.0  This option detects the following errors: Passing non-numeric arguments when a numeric value is required Passing a bad argument Passing the wrong number of arguments to a printf() function Note: BMC recommends enabling PSL Version 2.0 and PSL Version 3.0 built in functions.
   Traces
   Function call tracing	Reports which functions are called, but does not return information about the arguments. Function call tracing captures both user-defined and built-in functions.
   Function argument tracing	Reports the arguments passed to all user-defined or built-in functions Function call tracing must also be enabled if you want to use this debugger option.
   Function return value tracing	Reports the value returned by calls to all user-defined or built-in functions
   Variable assignment tracing	Reports the variable name (if available), and the value assigned to it
   PSL errno tracking	reports any nonzero values stored in the PSL errno variable
   PSL lock tracing	Reports the interprocess actions that occur during lock() and unlock() function processing This option reports back the granting, denying, and releasing of locks.

6. To complete the PATROL Scheduler PSL Debugger dialog box, choose one of the following options:
   • Click Accept to toggle the debugger data collection on for the items that you selected.

   • Click Cancel to close the dialog box without saving your changes.

     Note

     • The left side of the dialog box controls debug options for the scheduler daemon. The right side of the dialog box controls debug options for the graphical user interface (GUI).
     • Debug information is only sent to the BMC PATROL Agent Console window when the area being debugged is active. The PATROL KM for UNIX does not generate debug data when the scheduler daemon is sleeping, or the GUI is not being used.
     • In the left side BMC PATROL begins collecting debug data for the options that you selected. Debug information is displayed in the System Output Window.