Skip to Content
-3

Question on log-point id and its usage and functionality

Hello All,

Can any one please explain the basic functionality of the log-point with the addition ID and its significance and its usage , for example for the below log-point id , where is the qnao_sfws_sc_on defined and how can it control the program flow fron outside the program.

LOG-POINT ID qnao_sfws_sc_on.

I had gone through the basic F1 help and the documentations available in the forums and the portal.

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. Each time an entry is written to, a counter for the entry is increased. 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.

Addition 1

... ID group

Effect

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.

thanks, rg

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 30, 2017 at 04:35 PM

    The point is, I would just give a link to the documentation you cited above in order to answer your question. What are you missing? Logpoints simply work as described there.

    Look at program DEMO_CHECKPOINTS. It is described here. (I'll check why the source code is not loaded to the documentation). Play with it's checkpoint group in SAAB. No fear, you can't do anything wrong.

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 31, 2017 at 11:15 AM

    I used the log point to trace a complex process by putting a log point statement at every method entry/exit, IF, CASE, etc etc. This is relatively easy when using the replace functionality in MS Word (yes... word.... the ^p for line breaks comes in very handy). Then you can run your process without getting bogged down in breakpoints or trying to fathom out a run time analysis.

    Rich

    Add comment
    10|10000 characters needed characters exceeded