I have worked on systems where new Run Controls, whose IDs contain either a date or sequence number, are generated for each process. The result is that the Run Control tables, especially child tables, grow quickly and if not regularly managed will become very large. On one system, I found 18 million rows on one table!
I have written a simple Application Engine process, GFC_RC_ARCH, that purges old Run Controls from these tables. It can be downloaded from my website.
Run Control records are easily identified. They are characterised by:
- the first column of these tables is always OPRID, and the second is either RUNCNTLID or RUN_CNTL_ID,
- these two columns are also the first two columns of the unique key,
- the Run Control tables appear on pages of components that are declared as the process security component for that process.
I have chosen to make these two Application Engine processes mutually exclusive, so the Process Scheduler will not run both at the same time, but that configuration cannot be delivered in an Application Designer project.