The official ending of the Stone Age for an organization is when we no longer can find any batch processing that is still running outside of Control-M over the entire IT environment. This is harder to achieve than it sounds. Even with matured Control-M sites, we could occasionally see that there is batch processing done in CRON, Windows scheduled tasks, or other schedulers. Our objective is to find the simplest way with the least amount of risk involved in bringing those tasks into Control-M.
CRON jobs are the easiest-to-identify batch processing to be migrated into Control-M. Once they are migrated, we can make instant improvements simply by replacing time match scheduling with condition-based scheduling to shorten the total processing time, as well as letting each job automatically generate a status notification for quicker failure response.
Manually re-defining CRON jobs in Control-M has become history...