Control-M will primarily be used for coding, writing code, debugging errors, and building projects. It is part of my part-time work and serves for learning, explaining concepts, and similar purposes. I also use it for design, as I am a Solution Architect.
For a coding example, if I want to create a calculator that adds, subtracts, multiplies, and divides two numbers, I would use Control-M for that. There are many other ways I use Control-M beyond my main use case.
For cloud environments, the integration for Control-M will have multiple layers. Scheduled jobs and all things will be monitored.
The integration layers will be numerous, possibly through APIs or agents. That will be integrated with AWS, Azure, and Google Cloud. The exact integration depends on the cloud service.
In the future, we plan to use Control-M to support AI or ML workloads. We are exploring this possibility.
We are not using Control-M with Kubernetes.
The user or administrator will be responsible for taking care of compliance requirements with Control-M, where the activity is recorded. An audit record will document all the jobs.
The best features Control-M offers include workflow automation, job scheduling, monitoring and alerts, and integration.
Job scheduling and monitoring help automate repetitive tasks, run tasks at specific times, or handle some failures automatically.
Control-M has impacted my organization positively in that we are able to save time. It helps reduce human errors and improve productivity. Some of the tasks run on time, allowing us to manage or detect failures and manage all our complex workflows.
Control-M may need to improve its GUI. It should be more user-specific. Right now it is user-friendly, but I want it to be more precise for the users.
I have been using Control-M for about two years.
Control-M's scalability is good.
The customer support for Control-M is good.
We are not using any other solutions as of now. We are planning to use Control-M.
We have not deployed Control-M in our organization. I am using it as a customer.
I have seen some return on investment with Control-M as there are reduced missed deadline costs and recovery costs. That is one of the key ROIs I can mention.
In terms of pricing, there are two pricing tiers for Control-M: a starter pack for the SAS layer and enterprise custom pricing. My experience is that it is a bit overpriced.
Before choosing Control-M, we did not evaluate other options. We are trying to explore it. There are other competitors. I will be exploring in the future for IBM or other automation solutions.
On a scale of one to ten, I would rate Control-M a seven.
I chose a seven out of ten for Control-M because it does things that reduce my time and improve my productivity.
Regarding Control-M's AI capabilities, it has access control, originals, and many of the scheduling standards. It helps restrict who can run the job. Monitoring and alerts are present, where it identifies failures. It acts as a watcher.
Governance should be improved for it to be more useful in the field of AI. I am referring to predictive analytics, anomaly detection, monitoring, or root cause analysis. Those are the kinds of things I would add to it.
I would advise others looking into using Control-M to explore it.
LOL - "My relationship with BMC is more transactional. I am primarily paying them for the service rather than experiencing active involvement from their team."