As passionate Control-M administrators, we just cannot leave the Control-M running in production with all the default settings; we will try our best to figure out the configurations and tunings that can be done to make it close to perfect in every aspect. People may argue that it is something good to have but not 100 percent necessary in reality. Well, it may not be necessary for a site that only runs the same 200 jobs everyday, but it definitely makes noticeable difference if it is a reasonable sized environment with a large amount of users and running complex batch flows.
Talks around Control-M best practices and fine tuning can go pages after pages. In this section, we will be focusing on two major topics — housekeeping and NDP turning, plus highlighting some worth-to-consider features.