Hello SCN,
I have the following problem. I have a program that should start when an event is raised. For that I created a periodic job waiting for the event (start condition is after event). I thought that when I then raise the event using cl_batch_event=>raise, this job that was parked in SM37 would switch to "Active". That is sort of happening. But...
My program should always run in maximum one instance. Either one instance or parking off in SM37. Unfortunately when I call cl_batch_event=>raise, it creates a new instance of the job with status "Released" and activates the previous job into status "Active". Even if no job for that event is defined, it creates this job for me. This means the job is replicating itself over time and eating system resources, causing problems with concurrent access to the DB etc.
I understand I have no control over the kernel functionality in cl_batch_event=>raise, but is there anything I can do about this? I have coding in place that should prevent all of these problems (and I would swear it worked until recently), but cl_batch_event=>raise creating a job is for me surprising and suspicious. Is there either a way how to control this or has anyone else experienced that before?
Cheers Otto