One of the benefits of recurring scheduled requests is they are “set and forget” they just happily run and resubmit without you having to do a thing.
The biggest issue I’ve found, and this applies to almost all sites, is the “forget” component. I regularly find scheduled requests that have been running for years that are no longer required, and also duplicate scheduled requests which have come about because someone doesn’t know the original request exists. Both these issues are a waste of processing resources.
Another issue with scheduled requests is that I often find resource intensive requests originally set to run overnight now creeping into the working day because the request is resubmitting from the END of the prior run.
You should periodically review your scheduled requests to help avoid these issues.
Want to know more?
Download the simple OEBS scheduled requests report ordered by program - TOAD Reports format report.
Report ID - PRXCMS-002
Using this report you should be able to identify both your duplicates and those requests with a resubmit of END. By multiplying the “Re-submit” value by the “Resub Count” you can get some idea how long the request has been resubmitting.
Refer to PAM tutorial 19 “When Scheduled Requests Go Wrong”