Best practices are tricky. What is best for Company X is not necessarily best for Company Y. Company Z may have 2 distinct Lines of Business they support, and what works for one may not work for the other. There are many great features and capabilities in Control-M. I won’t preach to you how exactly you should use them; I just want to make sure you know the power is there. You can use it as you see fit! With this in mind, I am starting a blog series on things you should know about when working with Control-M. Without further adieu….
Standard Naming Conventions
For almost every field in Control-M, the more you follow a standard naming convention the easier your life will be. By using standard naming conventions you make many actions in Control-M easier to perform, like:
more easily secure items you want to limit or allow access to
quickly create viewpoints or dynamic filters to affect jobs in your view
quickly prevent or allow groups of jobs to run (via quantitative resources for example)
change massive amounts of job data, even complex strings, with speed and accuracy
Here is a screen shot showing just some of the powerful functionality in Find and Update.
Job Runtime Statistical Data
ctmjsa is a command that should be run on a regular basis. The statistics this utility compiles are very useful when you want to set up jobs to alert in cases when they run too long or too short an amount or percentage of time compared to their average. The system parameter RUNINF_PURGE_LIMIT controls how many of the statistical records are kept and used for the averaging.
By default 1 day worth of job sysout and 2 days of log are kept by Control-M. Modify these 2 system parameters (SYSOUTRETN and IOALOGLM) to increase the amount of sysout and log retained by Control-M. Then, when viewing an Archived ViewPoint (discussed below) you can see not only what the job flow looked like on a prior day, but you can also access the job sysout and log from that prior day as well, all without leaving Enterprise Manager.
To see what happened to jobs on a prior day load an archived viewpoint from the Enterprise Manager GUI (select File – Open Archived ViewPoint). MaxOldDay and MaxOldTotal parameters (found and set inside the Control-M Configuration Manager) control how many of these old networks are kept. If you match your sysout/log retention values with the Archived ViewPoint retention values you can not only see what jobs ran when on those prior days, but also access their sysout and log information.