Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Seven Deadly Sins of Control-M Under-Utilisation
Transcript of Seven Deadly Sins of Control-M Under-Utilisation
No 'File Name' field in version 8.
Other Task Types: Script and Embedded Script
Failover or DR plan
Task Monitoring and Management
Little Sins of Omission
Most under-utilised control modules:
Control-M for Databases
Control-M for Advanced File Transfer
Batch Impact Manager and Forecast
File System Mirroring or Failover
Control-M/Server mirroring and failover
Run backups and copy to safe location
Installation of Control-M on Cluster
KNOW THE IMPACT OF A DR SITUATION
What is a manual migration?
There is a risk of making a mistake and affecting Production job(s).
Why is it dangerous?
Making changes directly to jobs when moving from one Control-M to another.
How can I avoid it?
Parameterisation of data – global variables, host groups, connection profiles, naming standards.
If all else fails, use preset Find and Updates.
How do you end up with too many jobs?
1. Unnecessary test jobs
Why is it important?
BMC is increasingly concerned with license compliance.
How can you keep it under control?
1. Run Extreme Peaks report in batch.
User dailies: Too many jobs ordered during new day.
Automated clean up of log files (e.g. saved proclogs, database logs, archive logs)
Pre-execution and Post-execution Command (instead of SLEEP jobs)
Naming standards - esp conditions with confusing names – jobs creating an OK condition when job fails.
Attaching sysouts to emails.
Alerting in scripts
Workload Management rules - instead of using jobs to start/stop processes by creating/deleting conditions or change values of quantitative resources.
FAILURE TO USE:
Conditions with No Date (STAT conditions) - instead of using jobs to trigger cyclic jobs that run in a loop.
Reasons to use Remote Hosts:
Excuses for not using Remote Hosts:
Less effort required to install agents, upgrade agents and apply fix packs.
Less agents means that more will be on latest and most stable version.
Less configuration requirements.
Secure – using SSH or WMI technology to authenticate.
Day 1 support on new platforms and OS releases.
Some agent utilities (e.g. filewatcher) require an agent.
Requirement for many concurrent jobs – usually over 100.
Requirement for high performance, high volume and fast throughput.
Preference for UNIX agents in root mode or Windows agents with LOGON AS USER = N.
SYSOUTS are very large.
Some hosts (e.g. Tandem Guardian) don’t support agentless technology.
Control Module needs to be installed on host.
2. Holding jobs and forgetting about them.
3. Ordering jobs that are rarely executed.
4. Jobs used to perform functions that could be handled through smarter scheduling.
2. Run SQL script to check task count and send output to administrators.
3. Run batch report to identify held jobs.
Do you dare to ask any