When do freshly set dynamic logpoints take effect?

[BaerbelWinkler]

Hi All!
As mentioned in an earlier question, I have started to explore and use dynamic logpoints for some troubleshooting issues. I'm using transaction SDLP via SAP GUI in a NW 7.50 EHP8 SP22 system and it's usually working quite well. There however seems to be one case, where they are not (immediately) recognized:

For a long running job, I usually "watch" it for a few minutes via SAT and then look for promising routines in the hit list where dynamic logpoints might be of interest to capture some field information and set some breakpoints. I then go to SDLP and generate dynamic logpoints based on these breakpoints.

What is weird is, that I don't get any actual logs for these newly created and active logpoints even though - as seen in SAT - the coding is accessed regularly. I make sure that the logpoint is active for the user the batch job is running with and there are no other restrictions.

Are logpoints only recognized when they already existed prior to the program getting started initially? If that's the case, it might make sense to mention this on the help pages linked above as the logpoints may then lose some of their utility for ad hoc troubleshooting of already running processes / programs.

Has anybody run into this as well?

Thanks much and cheers

Bärbel

[BaerbelWinkler]

Update: when I recreate the logpoints in a test-system and then start the program with a subset of entires, the logpoints are immediately "filled with life" as expected.

[BaerbelWinkler]

Based on my own observations when working with dynamic log points they seem to take effect when a process gets started the next time. Because of that, they for example won't start collecting information while a long-running process is already active in the system when the logpoints were first set up. But they will kick-in when the process starts the next time.