Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on November 3, 2025. We recommend that you use PATROL for Linux, PATROL for AIX, or PATROL for Solaris to monitor operating systems.

PATROL Scheduler PSL Debugger dialog box


You can use this dialog box to toggle PSL debugger data collection on and off for different parts of the Scheduler application. For more information on PSL debugger data, see the PATROL Script Language Reference Manual Volume I—PSL Essentials.

Procedures related to this topic

Collecting Debug Data for the Scheduler Application

Items on this dialog box

Item

Description

Scheduler Daemon Debugger group box

Select the check box next to each selection that you want to turn on. When a debugging selection is turned on, debug data is collected for that option.

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 operations—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 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 Software 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 functionsFunction 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 tracking—reports the interprocess actions that occur during lock() and unlock() function processingThis option reports back the granting, denying, and releasing of locks.

Scheduler Facility Debugger group box

Select the check box next to each selection that you want to turn on. When a debugging selection is turned on, debug data is collected for that option.

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 operations—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 initializedIf 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 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 Software 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 tracking—reports the interprocess actions that occur during lock() and unlock() function processing. This option reports back the granting, denying, and releasing of locks.

Accept

toggles debugger data collection on for the options that you selected

Cancel

closes the dialog box without saving your changes

Related topics

Scheduler-SCHEDULER

SCHEDULER-application-menu

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*