We adressed this kind of issue in one of the major telephone company in France. Customer wanted to keep all jobs under control until a consistent set of job (here the management unit was the controlm APPLICATION name).
All jobs were defined with a MAXWAIT = 99n, which means that automatic cleanup of the AJF is not automaticamlly carried out and that the modification is to be done manually.
Of course, « manually » was not (and still is not) my concern. To address the issue, we created a standard script which updated the MAWXWAIT field on the AJF using a standar SQL request, like « updatre CMR_AJF set MAXWAIT=1 where APPLIC=’appli name’ and ODATE=’yyyymmdd’.
As a result, the jobs will be removed from AJF at the next newday procedure.
This update job was the very last one on the global application workflow.
Note that the update is not propagated on the EM GUI unless you hold/free the upddated jobs. However, the update is reflected on the controlm database ; you can check it using ctmpsmor SQL, and the AJF cleanup is based on the contents of the server database, not the EM one.