Show TOC

Checkpoint Groups and Activation SettingsLocate this document in the navigation structure

Definition

A Checkpoint Group is a transportable repository object. Each Checkpoint Statement that can be activated is linked with exactly one checkpoint group through the ID addition. All the checkpoint statements linked with a checkpoint group can be activated or deactivated through a checkpoint group.

Alternatively, checkpoint statements can also be activated through the surrounding Compilation Unit (for example, executable program, class pool, or function group). The link with a particular checkpoint group is not of importance in this case. In both cases, the activation is generally done for a set of checkpoint statements; single activation of individual checkpoint statements is not possible.

It is possible to create appropriate Activation Settings for activating checkpoints using Transaction SAAB. These settings refer either to a checkpoint group or a compilation unit. These activation settings are stored as local system data that cannot be transported. The process for creating the respective activations settings is transparent for the user. However, to better understand the process, it is worth taking a closer look at the structure of the activation settings:

An activation setting consists of the following four components:

  • Area of Validity

    The area of validity determines the checkpoints that a particular activation applies to.

  • Validity Period

    The validity period of activation settings with active operation modes is limited.

  • Context

    The context limits the validity of the activation setting either to a particular user or a particular application server.

  • Operation Type

    The operation mode defines the system behavior for the different checkpoint types.

Use

Area of Validity

The area of validity defines the group of checkpoint statement for which an activation setting is to be effective. This definition can consist either of the specification of a checkpoint group or the specification of a compilation unit.

  • Specification of a Checkpoint Group

    The activation setting applies to all checkpoint statements that can be activated and that refer to the specified checkpoint group through the ID addition. Here it is irrelevant in which compilation unit these checkpoint statements are located. Such settings are referred to as (checkpoint) group-specific settings.

  • Specification of a Compilation Unit

    The activation setting applies to all checkpoint statements that can be activated and are within the specified compilation unit. The respective assignment of these checkpoints to a checkpoint group using the ID addition is not of importance in this case. Such settings are referred to as (checkpoint) group-specific settings. As soon as there is a program-specific activation setting, this overrides all existing group-specific settings within the specified compilation unit.

Note

Checkpoint statements without the ID addition cannot be controlled through a program-specific setting since such checkpoints are always active.

Validity Period

During activation you can define if the activation is valid for the current day, week, or until a specific date.

Context

The context limits the validity of the activation setting either to a particular user or a particular application server. Three different possibilities result from this:

  • Global Activation

    Global activation is effective for all users and all application servers.

  • User-Specific Activation

    User-specific activation is effective for the specified user for all application servers.

  • Server-Specific Activation

    Server-specific activation is effective for the specified application server for all users.

The context specification is client-dependent. If several activation settings with different contexts are found during program execution, the following precedence rules apply:

  1. User-specific activation takes precedence over server-specific activation.

  2. User or server-specific activation takes precedence over global activation.

Operation Type

The operation mode specifies the behavior of the individual types of checkpoints, that is:

  • Assertions

  • Breakpoints

  • Log points

An activation setting thus applies to all types of checkpoints; the respective behavior, however, can be specified individually.

There are only two operation modes for breakpoints and logpoints, namely inactive and active ( break or log). For assertions, on the other hand, there are several types of the active operation mode.

In a valid activation setting, one of the three operation modes is always different from inactive. A completely inactive checkpoint group is created through the non-existence of a corresponding activation setting.

Operation modes that are not inactive are time-restricted. When activating checkpoint groups in transaction SAAB, the maximum time period of the activation must be set in specific limits.