LOG-POINT ID group
[SUBKEY sub]
[FIELDS dobj1 dobj2 ...].
1. ... ID group
2. ... SUBKEY sub
3. ... FIELDS dobj1 dobj2 ...
This statement defines a logpoint whose activation is controlled via the addition ID.
When the program reaches an active logpoint, an entry is created in the log that is also used by
the statement ASSERT and
the program execution proceeds with the statement after LOG-POINT.
During this process, an already existing entry of the same LOG-POINT
statement is overwritten by default. The log can be evaluated using transaction SAAB.
No log entry is written for an inactive logpoint and the program execution proceeds with the statement after LOG-POINT.
... ID group
The addition ID controls the activation of the logpoint from outside the program via a
checkpoint group group or an
activation variant. For the specification
of the checkpoint group, the same rules apply as to the
ASSERT statement.The possible operations modes for logpoints are active and logging.
... SUBKEY sub
When you specify SUBKEY, the content of
sub is stored as sub-key in the log. Already existing log entries of the same
LOG-POINT statement are only overwritten if the sub-keys have the same content. For
sub, you have to specify a character type data object of which the first 200 characters are evaluated. Without specifying SUBKEY, the sub-key is initial.
... FIELDS dobj1 dobj2 ...
After the addition FIELDS, you can specify a list
dobj1 dobj2 ... of any data object whose content is transferred to the log.